Introduction to the Alias Entity

In order to maintain and align data related to the registration of PIX keys, as required by the Central Bank of Brazil, the Indirect Participant must register an Alias in QI Tech. Every Alias is necessarily linked to an account that the Indirect Participant holds at QI Tech.

Information

Everything described in this introduction section is also detailed in the subsequent sections on how the Indirect Participant should handle it via API.

What does the Alias entity represent?

The Alias entity is a 'mask' of the account data that the Indirect Participant's customer has registered with the Indirect Participant. It is emphasized that QI Tech will only perform formatting checks on the data sent by the Indirect Participant to us. For example, validation of CPF, CNPJ, maximum character length of a trade name, etc. The data that QI Tech asks the Indirect Participant to send regarding their customer's account is only that which is necessary for the scope of PIX functionalities.

Alias in practice

In practice, the Alias entity represents the customer of the Indirect Participant. An example of the need to create an Alias would be:

The Indirect Participant has an account with account_key a520b977-d6b2-4f27-bef5-29760ebfd6a7 registered at QI Tech,

The Indirect Participant wishes to link their own customer to this account registered at QI Tech,

The Indirect Participant sends the customer's data (account number, branch, name, trade name, etc.) to link to this account registered at QI Tech,

QI Tech links the Indirect Participant's customer to the account registered at QI Tech.

The Indirect Participant receives a unique key identifying the registered Alias.

Thus, the Indirect Participant can request the creation of a PIX key, and QI Tech will be able to effectively communicate with the Central Bank of Brazil with the necessary data for registration.

Representation of Alias usage with a 1:N relationship:

Representation of Alias usage with a 1:1 relationship: