Introduction to Alias Entity

In order to maintain and align data regarding PIX key registration, as required by the Central Bank of Brazil, the Indirect Participant must register an Alias with QI Tech.

Every Alias is necessarily linked to an account that the Indirect Participant has with QI Tech.

Information

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

What does the Alias entity represent?

The Alias entity is a 'mask' of the account data that the Indirect Participant's client has registered with the Indirect Participant itself. It should be noted that QI Tech will only perform formatting validations on the data sent by the Indirect Participant to us.

For example: CPF validation, CNPJ validation, maximum character length for a trade name, etc.

The data that QI Tech requests the Indirect Participant to send, regarding their client's account, is only what is necessary for PIX functionality purposes.

Alias in practice

In practice, the Alias entity represents the Indirect Participant's client.

An example regarding the need to create an Alias would be:

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

Indirect Participant wants to link their own client to this account registered with QI Tech,

Indirect Participant sends the client's data (account number, branch, name, trade name, etc) to link to this account registered with QI Tech,

QITech links the Indirect Participant's client to the Indirect Participant's registered account.

Indirect Participant receives a unique identification key for the registered Alias.

This way, 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 1:N relationship:

Representation of Alias usage with 1:1 relationship: