Normative Instruction BCB No. 6 — Amends Circular Letter No. 4,056 of May 25, 2020, which establishes the procedures necessary for PIX adherence since its launch

BCB NORMATIVE INSTRUCTION NO. 6, OF AUGUST 20, 2020

Amends
Circular Letter No. 4,056, of May 25, 2020, which establishes the procedures necessary for adherence to PIX, since its launch.

The Head of the Department of Competition and Financial Market Structure (Decem), in use of the attributions conferred upon him by art. 97-A, item V, of the Internal Regulations of the Central Bank of Brazil, annexed to Ordinance No. 84,287, of February 27, 2015, and taking into account the provisions of § 3º of art. 25 of Resolution BCB No. 1, of August 12, 2020,

R E S O L V E :

Art. 1º The normative devices conferring competence to the signatory of Circular Letter No. 4,056, of May 25, 2020, are amended, which shall henceforth read as follows:

“The Head of the Department of Competition and Financial Market Structure (Decem), in use of the attributions conferred upon him by art. 97-A, item V, of the Internal Regulations of the Central Bank of Brazil, annexed to Ordinance No. 84,287, of February 27, 2015, and taking into account the provisions of § 3º of art. 25 of Resolution BCB No. 1, of August 12, 2020,” (NR)

Art. 2º Circular Letter No. 4,056, of May 25, 2020, shall henceforth read as follows:

“Art. 12. ..........................................................................................................

.......................................................................................................................

§ 1º ..................................................................................................................

.......................................................................................................................

VII - infringement notification functionality test.

.......................................................................................................................

§ 4º At least one message from the tests referred to in § 1º must be duly signed.

§ 5º The tests referred to in item V of § 1º must be carried out by means of simulation of operations with at least one institution that uses the direct access service to DICT provided by the institution with direct access.” (NR)

“Art. 22. In addition to compliance with the provisions of this Circular Letter, successful completion of the PIX adherence process implies adherence to the rules, conditions, and procedures established in the PIX Regulation.” (NR)

Art. 3º Annex I of Circular Letter No. 4,056, of May 25, 2020, shall henceforth read as follows:

“Annex I – Requirements and deadlines for compliance with formal tests for access to DICT

Object of tests	To comply, the institution must:	Period
1. Registration, exclusion, and inquiry functionalities for addressing keys	I – register at least one addressing key of each type (mobile phone number, e-mail, CPF, CNPJ, and Virtual Payment Address – EVP); II – exclude at least one addressing key of each type (mobile phone number, e-mail, CPF, CNPJ, and Virtual Payment Address – EVP); and III – inquire about at least one addressing key of each type (mobile phone number, e-mail, CPF, CNPJ, and Virtual Payment Address – EVP).	June 1, 2020 to July 15, 2020 9h to 18h business days
2. Portability and claim of ownership functionalities for addressing keys	I – initiate a portability or claim of ownership process with mobile phone number, e-mail, CPF, and CNPJ; II – cancel at least one portability or claim of ownership process that is status “Open”; and III – confirm at least one portability or claim of ownership process that is status “Open”.	July 1, 2020 to August 15, 2020 9h to 18h business days
3. Protection mechanisms against scanning of DICT and internal database of participants	I – send declaration, to the email dict@bcb.gov.br, stating that performing two successive inquiries of the same user is generating the same “PI-PayerId” result for both inquiries; and II – send declaration, to the email dict@bcb.gov.br, stating that the institution has adequate protection mechanisms against scanning of its internal database.	August 1, 2020 to September 30, 2020
4. Synchronization verification functionality	I – register at least one thousand addressing keys of a specific type (mobile phone number, e-mail, CPF, CNPJ, or Virtual Payment Address – EVP) and request synchronization verification of this type of addressing key; and II – simulate lack of synchronization between DICT and internal database and identify divergent addressing keys through file of content identifiers (CIDs) registered in DICT.	July 1, 2020 to August 31, 2020 9h to 18h business days (exception: CIDs – 16h to 18h business days)
5. Simulation of requests sent by participants accessing DICT indirectly (all functionalities)	Execute, on behalf of another institution, the tests referred to in items 1, 2, and 4 (object of tests).	July 1, 2020 to August 31, 2020 9h to 18h business days
6. Capacity test	I – Inquire about one thousand different keys within an interval of 60 seconds and receive successful response from DICT, if the institution maintains up to one million transactional accounts; II – inquire about two thousand different keys within an interval of 60 seconds and receive successful response from DICT, if the institution maintains between one million and ten million transactional accounts; or III – inquire about four thousand different keys within an interval of 60 seconds and receive successful response from DICT, if the institution maintains more than ten million transactional accounts. The inquiries must last ten minutes and must be distributed homogeneously over time, with the total number of operations being equal to: I – ten thousand, if the institution maintains up to one million transactional accounts; II – twenty thousand, if the institution maintains between one million and ten million transactional accounts; or III – forty thousand, if the institution maintains more than ten million transactional accounts.	August 1, 2020 to September 30, 2020 9h to 18h business days
7. Infringement notification functionality	I – open an infringement notification process; II – receive an infringement notification; III – cancel an open infringement notification; and IV – analyze an infringement notification process.	September 1, 2020 to September 30, 2020 9h to 18h business days
Final adjustments		Until October 16, 2020 9h to 18h business days	”(NR)

Art. 4º Annex II of Circular Letter No. 4,056, of May 25, 2020, shall henceforth read as follows:

“Annex II – Requirements and deadlines for the process of verifying adherence of solutions to end users

Stages	To comply, the institution must:	Period
1. Submission of mobile application draft	Submit mobile application draft indicating the intended form of making PIX available, presenting, at minimum: I – the dynamics of activating the environment dedicated to PIX; II – the location of PIX functionalities in the general application environment; and III – the general presentation of application options involving functionalities related to PIX (e.g., payments, transfers, etc.), including menus, shortcuts, and quick access buttons, if they exist.	June 1, 2020 to July 15, 2020
2. Submission of mobile application project	Submit mobile application project, which shall contain, at least, the following indications: I – user authentication method; II – method of making the following procedures available for initiating a PIX: a) manual insertion of recipient user data by the payer user; b) insertion of PIX key; and c) QR Code reading; III – method of making PIX initiation available through insertion of the five types of PIX keys: a) mobile phone number; b) e-mail address; c) CPF registration number; d) CNPJ registration number; and e) random key; IV – method of making recipient user information available after inquiry to DICT of a PIX initiated through insertion of PIX key; V – method of making error messages available; VI – method of notifying the payer user after successful completion of a transaction; VII – method of notifying the recipient user after successful completion of a transaction; VIII – method of presenting a PIX receipt; IX – method of making PIX initiation available through manual insertion of recipient user data; X – method of presenting PIX in transaction statement; XI – method of making return available; XII – method of making PIX key management option available; XIII – method of making information regarding registered PIX keys available; XIV – method of making PIX key registry available; XV – method of making PIX key deletion available; XVI – method of making PIX key portability available; XVII – method of communicating with the user after receiving a PIX key portability request; XVIII – method of notifying the user of successful and unsuccessful completion of PIX key registration, exclusion, portability, and claim of ownership operations; XIX – method of making recipient user information available after reading a static QR Code; XX – method of making recipient user information available after reading a dynamic QR Code; XXI – method of making option to generate QR Code available.	August 1, 2020 to August 31, 2020
3. Adjustments to the project and submission of final version of mobile application project	Depending on the analysis of each project.	August 1, 2020 to October 16, 2020	”(NR)

Art. 5º This Normative Instruction enters into force on the date of its publication.

Angelo José Mont Alverne Duarte