Instruction Normative BCB No. 774 — Publishes Version 7.4 of the "Minimum Requirements for User Experience" Document, Which Comprises the Pix Regulation

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, attached to Resolution BCB No. 340, of September 21, 2023, and considering the provisions of Article 2, caput, item IV, of the Regulation attached to Resolution BCB No. 1, of August 12, 2020,

RESOLVES:

Art. 1 This Instruction Normative publishes version 7.4 of the document “Minimum Requirements for User Experience”, which comprises the Pix Regulation, as per Article 2 of the Regulation attached to Resolution BCB No. 1, of August 12, 2020.

Sole Paragraph. The document “Minimum Requirements for User Experience” is available at the electronic address of the Central Bank of Brazil on the internet, on the page dedicated to the manuals that compose the Pix Regulation: https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/IV_RequisitosMinimosparaExperienciadoUsuario.pdf

Art. 2 Instruction Normative BCB No. 689, of December 11, 2025, is hereby revoked.

Art. 3 This Instruction Normative enters into force on March 1, 2027.

Ricardo Teixeira Leite Mourão

ANNEX TO INSTRUCTION NORMATIVE BCB No. 774 OF SEPTEMBER 3, 2026

Minimum Requirements for User Experience Version 7.4

Revision History

Date	Version	Description of Changes
09/2026	7.4	• Chapter 02:

• Page 07 – item 10 (new): inclusion of mandatory message to inform the user when a Pix transaction cannot be performed due to a founded suspicion of transactional fraud.

• Page 10 – item 15: exclusion of the item, with migration of the requirements to the chapters dealing with payment by static QR Code (Ch. 06) and by dynamic QR Code, with alterations.

• Adjustments to item numbering due to the inclusion and exclusion of items in the chapter.

• Chapter 03:

• Page 13 – item 06: inclusion of the term “founded suspicion of” in the body of the requirement and exclusion of the term “founded” in error message examples.

• Page 14: repositioning of screens related to items 07 and 08 on the page.

• Page 14: renumbering of item 11 to item 10 and repositioning of the corresponding illustrative screen.

• Page 15 – item 11 (new): inclusion of requirements for favorite contacts, with storage of the Pix key used in initiation and mandatory alert to the paying user in case of alteration of the receiving user’s identification. Inclusion of an exemplifying screen.

• Page 16 – item 14: inclusion of mandatory display of the Legal Entity’s Trade Name of the receiving user, when existing, and prohibition of inclusion of advertisements, offers, links, and content unrelated to the transaction on payment receipts.

• Adjustments to item numbering due to the inclusion of a new item in the chapter.

• Chapter 04:

• Page 21 – item 08: inclusion of mandatory display of the Legal Entity’s Trade Name of the receiving user, when existing; and prohibition of inclusion of advertisements, offers, links, and content unrelated to the transaction on payment receipts.

• Chapter 06:

• Page 27 – item 01: inclusion of prohibition of displaying the Pix key among the data returned from DICT in static QR Code reads, in substitution for the requirement excluded from Ch. 02 (item 15), with exclusion of the passage “when the TxId is filled in”.

• Page 29 – item 08: inclusion of the term “founded suspicion of” in the body of the requirement and exclusion of the term “founded” in error message examples.

• Page 31 – item 13: inclusion of mandatory display of the Legal Entity’s Trade Name of the receiving user, when existing; exclusion of the passage “when the TxId is filled in” from the prohibition of displaying the Pix key and account data; and prohibition of inclusion of advertisements, offers, links, and content unrelated to the transaction on payment receipts.

• Page 31 – item 14: inclusion of prohibition of saving account data linked to payments by static QR Code. Exclusion of the passage “when the TxId is filled in” from the prohibition of displaying the Pix key and account data.

• Chapter 07:

• Pages 33 and 34 – items 01 and 03: wording adjustments to clarify that, in initiations by dynamic QR Code, the field “informacoesEntreUsuarios” of pacs.008 must be used to register the paying user’s response to the field “solicitacaoPagador”, when this is informed by the receiving user. Inclusion of prohibition of displaying the Pix key among the data returned from DICT in dynamic QR Code reads, in substitution for the requirement excluded from Ch. 02 (item 15).

• Page 36 – item 10: inclusion of the term “founded suspicion of” in the body of the requirement and exclusion of the term “founded” in error message examples.

• Page 38 – item 14: inclusion of mandatory display of the Legal Entity’s Trade Name of the receiving user, when existing; and prohibition of inclusion of advertisements, offers, links, and content unrelated to the transaction on payment receipts.

• Page 38 – item 15: inclusion of prohibition of saving account data linked to payments by dynamic QR Code.

• Chapter 08:

• Pages 40 and 41 general review of screens to standardize the identification of payments and receipts, using the signs “+” and “-” and the terms “Payment” and “Receipt”.

• Page 40 – item 05: adjustments in the identification of MED returns in statements, with substitution of the reference to the protocol by the dispute identifier and inclusion of requirements for presenting the return in the debited user’s statement. Inclusion of an illustrative example of the item.

• Chapter 10:

• Page 50 – item 08: revision of the requirement regarding the claim of ownership of Pix keys, restricting its application to keys of the cellular phone number type and including specific guidelines for attempts to register email keys already registered by another user.

• Page 52 – item 12: wording adjustments to make the requirement clearer. Inclusion of guidance that failure messages inform the association of the user or account to the marking of suspicion of transactional fraud as the reason for rejection, when the infraction notification has been created or accepted by the PSP itself.

• Chapter 15:

• Pages 86, 90, 94, 97, 98 and 100 – items 05, 06, 07, 17, 27, 34, 36, 41: standardization of the display of the “Payment Object” field in notifications, authorization journeys, queries, history, and receipts of Pix Automatic, observing the provisions of item 09.

• Page 86 – item 06: exclusion of recommendation to use a link in the notification to direct the user to the screen with authorization information.

• Page 87 – item 09 (new): inclusion of requirement for clear and prominent presentation of the “Payment Object” field, to facilitate identification of the purpose of the payment associated with Pix Automatic.

• Pages 86, 88 and 89 – items 08, 13 and 16: alteration of item 16 to item 17 in the reference to the continuity of the authorization journey;

• Page 92 – item 20: inclusion and standardization of the display of the “Payment Object” field, observing the provisions of item 09. Inclusion of requirement to fill the field informacoesEntreUsuarios of pacs.008 with the paying user’s response to the field solicitacaoPagador, when this is informed by the receiving user. Exclusion of the phrase prohibiting the availability of the “Description” field and other wording adjustments.

• Pages 93 to 95, 97, 98, 100, 101 and 104 – items 21 to 28, 34, 36, 41, 44, 58: adjustments in the exemplifying screens to include and standardize the display of the “Payment Object” field in the functionalities of Pix Automatic, observing the provisions of item 09.

• Page 100 – item 41: inclusion of mandatory display of the Legal Entity’s Trade Name of the receiving user, when existing; and prohibition of inclusion of advertisements, offers, links, and content unrelated to the transaction on payment receipts. Inclusion of reference to the provision in item 09 in the topic regarding the “payment objective”.

• Page 100 – item 42: adjustment in the exemplifying screen to remove the nomenclature “Pix Automatic” from immediate payment receipts linked to authorization journeys.

• Page 104 – item 55: adjustments to the requirements for handling pending authorizations due to lack of response from the receiving PSP, with inclusion of failure notification in case of cancellation after the regulatory period has elapsed.

• Page 104 – item 58 (new): inclusion of the mandatory display of the “Payment Object” field in notifications, when filled in.

• Adjustments to item numbering due to the inclusion of a new item in the chapter.

• Chapter 16:

• Pages 105 to 119 – items 01 to 36: general reformulation of the Self-Service MED chapter, with reorganization of the dispute journey, inclusion of a triage stage to identify eligible and non-eligible situations for MED, revision of guidelines provided to the user, improvement of fraud suspicion classification and contextualization, inclusion of eligibility analysis before opening value recovery, adaptation of the Pix Automatic dispute journey, improvements in querying and canceling disputes, inclusion of receipts related to returns via MED, new notifications for canceling disputes with resource return, and adjustments to recommendations for monitoring dispute progress.

• Chapter 17:

• Page 123 – item 09: wording adjustments to clarify that the prohibition of saving the Pix key applies to payments by static and dynamic QR Code, with exclusion of the condition “when the TxId is filled in”.

• Page 123 – item 10: wording adjustment to clarify that the prohibition of saving transactional account data applies to payments by static and dynamic QR Code, with exclusion of the condition “when the TxId is filled in”.

• Page 123 – item 11 (new): inclusion of requirements for favorite contacts, with storage of the Pix key used in initiation and mandatory alert to the paying user in case of alteration of the receiving user’s identification.

• Adjustments to item numbering due to the inclusion of a new item in the chapter.

• Chapter 21 – Annex I:

• Pages 136 to 142 – adjustments to page and item numbering cited and update of texts to incorporate the changes introduced in the manual.

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 compose or 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 compose or detail and complement it are not subject to the prior production of a regulatory impact analysis (AIR).

In this way, this Instruction Normative is exempted from the prior production of AIR.

Ricardo Teixeira Leite Mourão