Instruction Normative BCB No. 769 of August 19, 2026

The Head of the Department of Competition and Financial Market Structure (Decem), using the powers conferred by Articles 23, caput, item I, letter “a”, and 94, caput, item IX, of the Internal Regulations of the Central Bank of Brazil, annexed to Resolution BCB No. 340 of September 21, 2023, and considering the provisions of Article 2, caput, item II, of the Regulation annexed to Resolution BCB No. 1 of August 12, 2020,

RESOLVES:

Art. 1 This Instruction Normative publishes version 2.10.0 of the Pix Initiation Standards Manual, which constitutes part of the Pix Regulation, as per Article 2 of the Regulation annexed to Resolution BCB No. 1 of August 12, 2020.

Sole Paragraph. The Pix Initiation Standards Manual is available at the electronic address of the Central Bank of Brazil on the internet, on the page dedicated to the manuals that make up the Pix Regulation: https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf.

Art. 2 Instruction Normative BCB No. 658 of September 5, 2025, is hereby revoked.

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

Ricardo Teixeira Leite Mourão

---

ANNEX TO INSTRUCTION NORMATIVE BCB No. 769 OF AUGUST 19, 2026

Pix Initiation Standards Manual Version 2.10.0

Revision History

Date	Version	Description of Changes
11/8/2020	1.0	Initial version
23/9/2020	1.1	Adjustments to definitions in the payload fields, especially the semantics of the txid field. Annexes I and II included, dealing with Pix API Business Concepts and their technical specifications.
13/10/2020	2.0	Section 1.5.2: explanations added regarding permitted characters in the txid field. Section 1.6.1: text included to clarify that the dynamic QR Code can be generated via an application. Section 1.6.6: text excluded to clarify that the dynamic QR Code does not necessarily need to be generated via the Pix API. Section 1.6.8: adjustment in the explanation of the “calendario.vencimento” field and exclusion of the “calendario.recebivelAposVencimento” field. Section 1.6.17: footnote included in field 62 “Additional Data Field”. Section 1.6.18: text included to clarify that the dynamic QR Code can be generated via an application. Section 1.7 included, dealing with the “Pix Copia e Cola” functionality. Annex I, Section 6.3.3: correction of the function associated with the alteration of the charge via Pix API.
6/11/2020	2.1	Section 1.6: update of the Payload JSON fields, with the inclusion of fields related to the charge for payments with maturity functionality (interest, penalty, discount, and related); reorganization of sub-sections to reflect the differences in fields between charges for immediate payments and payments with maturity. Annex I: Use cases related to “Location Reuse” added, scenarios including charge for payments with maturity and generation of charges in batches. Annex III included dealing with creation, update, and calculation of charges for payments with maturity.
9/12/2020	2.2	Section 1.6.6.2: insertion in the table displaying the JSON payload structure for charges with maturity of the information calendario.validadeAposVencimento. Annex II – Section 3.1: insertion of a recommendation regarding the use of certificates in webhooks.
12/2/2021	2.2.1	Section 1.6.6.1: explanation added for the field increment rule. Section 1.6.6.2: clarifications added regarding the operation of the field calendario.validadeAposVencimento. Section 2.1: changed from mandatory to optional the filling of the logradouro, cidade, UF, and CEP fields of the “debtor” field in the creation of a charge with maturity. Section 1.6.1: Excluded the passage that erroneously referred to a possible “0” value in the EMV value field.
22/3/2021	2.3.0	Section 1.4: footnotes removed and explanations added to clarify that the Pix key formatting rule follows the determinations contained in the DICT Operational Manual. Section 1.6.3: fragment indicating the location version removed. Section 1.6.6: editorial adjustment to clarify that the municipality code to be informed by the payer’s PSP must correspond to the user payer’s address registration information. Section 1.6.6.1: modalidadeAlteracao field added to the “valor” object for Pix Cobrança for immediate payments. Section 1.6.6.2: clarifications inserted regarding the behavior of the maturity date and validity after maturity in case of weekend and holiday for the user payer. Section 1.6.7: revised example: value (EMV, optional) removed; Ref.Label (txid) modified (emphasizes that the charge payload applies); ‘v2’ fragment (made optional) removed from the location (charge URL). Annex III: clarifications inserted regarding the behavior of the maturity date in case of weekend and holiday for the user payer and about the consequent impacts on fields that reference this date (validadeAposVencimento; discount; interest and penalty).
22/7/2021	2.4.0	Section 1: Generalization of 'celular' to 'mobile device'; Section 2.4.2: Reinforcing the key's mandatory nature; Section 1.6.2. Footnote promoted to highlight QR Code reuse; Section 1.6.3. Correction of fdqnPspRecebdor to fqdnPspRecebedor; Section 2.7.1. Structuring points of attention; Section 2.7.1.1: in the description of the value field, text changed to reflect that the field follows the regex specified in the Pix API: \d{1,10}.\d{2}; Section 2.7.1.2: in the description of the value field, text changed to reflect that the field follows the regex specified in the Pix API: `\d{1,10
26/8/2021	2.5.0	Section 1: Clarifications in the text. Section 1.2 and 1.5: Inclusion of the new FSS field related to Pix Saque in the Static QR Code. Section 1.5.1: Inclusion of a situation where the fss field is used. Section 1.6: Inclusion of fields related to Pix Saque and Pix Troco in the Dynamic QR Code. Section 1.6.6.2: Adaptation of the description and mandatory nature of the calendario.validadeAposVencimento field to the Pix API specification. Section 1.8: Change in the table with mandatory information about initiation through the payment transaction initiation service. Section 2: Inclusion of fields in payment messages related to Pix Saque and Pix Troco. Annex I: Section 1: Inclusion of functionalities related to Pix Saque and Pix Troco among those covered by the Pix API. Annex I: Section 4: Inclusion of the definition of FSS. Annex I: Section 5.4.2: Inclusion of mandatory functionalities per product offered. Annex III: Section 2.1: Adaptation of the mandatory nature of the calendario.validadeAposVencimento field to the Pix API specification. Annex 4: Inclusion of the implementation schedule for mandatory functionalities.
17/9/2021	2.6.0	Section 2: Adaptation of the information contained in the payment message fields and inclusion of guidelines regarding a Pix Saque via static QR Code.
29/10/2021	2.6.1	Section 1.6.1: Change of text of footnote 35 regarding the municipality code. Section 1.6.6.1: Correction of AGTET to AGTEC. Section 1.6.6.1: Adaptation regarding the content of the valor.retirada.troco.modalidadeAgente field for Pix Troco. Section 1.6.6.2: Reinforcement of the mandatory nature of the calendario.validadeAposVencimento field in the return. Section 1.8: Inclusion of fields for the payment transaction initiation service. Section 2.3: Inclusion of field of the payment transaction initiation service for pacs.008.
09/12/2021	2.6.2	Section 1: Adaptation of terminologies related to Pix Saque and Pix Troco. Section 1.5.4, 1.6.6.1 and 2.2: Inclusion of correspondent banks as withdrawal agents (modalidade AGTOT).
30/8/2022	2.6.3	Section 1.5: Change in the denomination of the pss field to fss in the static QR Code, with equivalent semantics. Sections 1 and 2: Adaptation of terminologies related to Pix Saque and Pix Troco, regarding the Withdrawal Service Facilitator. Section 1.8: Change in the table with mandatory information about initiation through the payment transaction initiation service, with adaptation of the mandatory date for code generation by the initiator and inclusion of information about the codMun of the user payer. Annex III. Section 2.1: Clarifications inserted regarding the valor and discount value fields, in the composition of the charge value. Annex III. Section 2.3.2: Adjustment in the calculation of the discount value, in the charge with maturity, which can be applied for dates less than or equal to the maturity date, as per the Pix API specification.
31/10/2024	2.7.0	Reorganization of the document:

Creation of section “1. Introduction” Previous section “1. Pix Initiation by QR Code” was divided into two sections: “2. Initiation by QR Code” and “3. Other forms of initiation” Previous section “2. Mapping to ISO 20022 Messages” was transferred to “ANNEX V - Mapping to ISO 20022 Messages” “ANNEX IV – Deadlines for implementation of functionalities” was changed to “ANNEX VI – Deadlines for implementation of functionalities”

Inclusion of the Pix Automático product:

Creation of section “2.8 Initiation via Composed QR Code” Creation of section “3.3 Pix Automático” Inclusion of content related to Pix Automático and Composed QR Code in “ANNEX I – Pix API: Business Concepts” Creation of “ANNEX IV – Pix Automático” Inclusion of the messages used in Pix Automático in “ANNEX V - Mapping to ISO 20022 Messages” | | 29/11/2024 | 2.8.0 | Annex IV, Section 2.2.1: Inclusion of clarification regarding the identifiers of the recurring charges. Inclusion of ANNEX VI on the Standardized File of Pix Automático. Reorganization in the document: The “ANNEX VI – Deadlines for implementation of functionalities” was changed to “ANNEX VII – Deadlines for implementation of functionalities”. | | 14/03/2025 | 2.8.1 | Annex IV, Section 2.1.2: Adjustment in the wording and inclusion of the reference to the agreement in the recebedor attribute of the recurrence. Annex IV, Section 2.3.9: Inclusion of the reference to the ajusteDiaUtil attribute in the recurring charge. Annex IV, Section 3.3.5: Inclusion of the table of rejection codes for attempts to schedule recurring charges that cause the rejection of the related recurring charge. Annex IV, Section 4.3.1: Adjustment in the rule for defining the start date of the charge cycles, when the expected charge date does not exist. | | 05/06/2025 | 2.8.2 | Section 2.8.4.2: Adjustment in the Mult. column of the table to highlight the optionality of the vinculo.objeto field of the recurrence parameters. Inclusion of section 3.4 on the initiation method “Pix by proximity” | | 05/09/25 | 2.9.0 | Section 2.5.1: inclusion of example of alphanumeric CNPJ key. Annex IV, Section 2.1 and Section 2.2: adaptation of the rules for forming idRec and idSolicRec to alphanumeric CNPJ. | | 19/08/26 | 2.10.0 | Section 3.2: Inclusion of the AUTO initiation method in the table with mandatory information about initiation through the payment transaction initiation service and adjustment in the information about the codMun of the user payer in the dynamic QR Code with maturity. Annex III, Section 3: Textual adjustments regarding the valor.juros.valorPerc field. Annex IV, Section 2.1.6: Adjustment to include new information on the closure of a recurrence. Annex IV, Section 2.2.5: Inclusion of the section with information on the closure of a recurring charge request. |

NOTE

Decree No. 10.411, of June 30, 2020, provides for the mandatory conduct of a regulatory impact analysis (AIR) for the issuance of normative acts of general interest produced by the organs and entities of the direct and indirect federal public administration.

However, as defined in paragraph 8 of Vote 280/2021–BCB, of November 10, 2021, the Pix Regulation, including the other documents that integrate, detail, and complement it, do not characterize themselves as a regulatory act of coercive force, possessing, in truth, an eminently contractual nature. Thus, modifications promoted in said regulation and in the other documents that integrate, detail, and complement it are not subject to the prior production of an AIR.

Ricardo Teixeira Leite Mourão