Skip to main content

Introduction to Portability Requests

PIX key claims and portability are special mechanisms provided by the central bank for potential changes in PIX key ownership.

  • Claims are used in cases where there is a change in ownership of a key (phone or email), and the new owner wishes to create a link for their account, but the previous owner (former holder of the phone or email) already has a record in the DICT with this key.

  • Portabilities are used when the key owner wishes to change its linkage to another account, which is domiciled in a different participant from the current one. For each type of ownership change resource, there are only a few types of keys enabled, which are:

CompatibleClaimPortability
cpf✓
cnpj✓
phone_number✓✓
email✓✓
random_key

In the scope of indirect PIX, the ownership change mechanisms will work with the same premises, with special routes provided in the QI Tech infrastructure so that accounts enabled to use indirect PIX can make requests and receive responses from the flows presented above.

1. Claimant Flow​

info

The flowcharts below represent the behaviors pertinent to the claim flow of PIX key

1.1. QI Tech Indirect Participant requests opening a portability request​
flowchart LR
    PARTICIPANT(Indirect Participant\n QiTech);
    WAITING_RESOLUTION{{Portability \n'waiting_resolution'}};
    
    PARTICIPANT -. portability\n request.-> WAITING_RESOLUTION
1.2. Donor Bank confirms receipt of portability request​
flowchart RL
    OTHER_BANK(Donor Bank);
    QI_PARTICIPANT(Indirect Participant\n QiTech);
    CONFIRMED{{Portability \n 'confirmed'}};
    
    OTHER_BANK-. Confirm portability\n request.->CONFIRMED -- Webhook Update --> QI_PARTICIPANT;
flowchart LR
    BACEN(Banco Central \n do Brasil);
    QI_PARTICIPANT(Indirect Participant\n QiTech);
    COMPLETED{{Portability \n 'completed'}};
    
    QI_PARTICIPANT-. Completes portability\n request.->COMPLETED -- Pix key link \n creation--> BACEN;
Important

Portability Requests with confirmed status can only be canceled if they are of type "fraud"

flowchart LR
    BACEN(Banco Central \n do Brasil);
    QI_PARTICIPANT(Indirect Participant\n QiTech);
    PORTABILITY{{Portability \n 'waiting_resolution' ou 'confirmed'}};
    
    QI_PARTICIPANT-. Cancel portability \n request.->PORTABILITY -- Pix key link creation --> BACEN;

2. Donor Flow​

info

The flowcharts below represent the behaviors pertinent to the donation flow of PIX key

2.1. Claimant Bank opens a portability request​

flowchart RL
    OTHER_BANK(Claimant Bank);
    QI_PARTICIPANT(Indirect Participant\n QiTech);
    CONFIRMED{{Portability \n 'waiting_resolution'}};
    
    OTHER_BANK-. Confirm portability \n request.->CONFIRMED -- Portability Request Receipt \n Webhook --> QI_PARTICIPANT;

2.2. QI Tech Indirect Participant confirms receipt of portability request​

flowchart LR
    PARTICIPANT(Indirect Participant\n QiTech);
    CONFIRMED{{Portability \n'confirmed'}};
    
    PARTICIPANT -. Confirms receipt \n and removes link .-> CONFIRMED

2.3. Claimant Bank completes a portability request​

flowchart RL
    OTHER_BANK(Claimant Bank);
    QI_PARTICIPANT(Indirect Participant\n QiTech);
    CONFIRMED{{Portability \n 'completed'}};
    
    OTHER_BANK-. Completes portability\n request.->CONFIRMED -- Webhook Update --> QI_PARTICIPANT;

2.4. Claimant Bank cancels a portability request​

Important

Portability Requests with confirmed status can only be canceled if they are of type "fraud"

flowchart RL
    OTHER_BANK(Claimant Bank);
    QI_PARTICIPANT(Indirect Participant\n QiTech);
    PORTABILITY{{Portability \n 'waiting_resolution' ou 'confirmed'}};
    
    OTHER_BANK-. Cancels portability\n request.->PORTABILITY -- Webhook Update --> QI_PARTICIPANT;