Instruction Normative BCB No. 689 — Publishes Version 7.3 of the "Minimum Requirements for User Experience" Document, which Comprises the Pix Regulation — BCB — BR

for user experience version 7.3
MINIMUM REQUIREMENTS
Access version 7.4 here, effective from 01/03/2027.

December 2025
Version: 7.3
All rights reserved. Partial or total reproduction of this work is permitted, provided the source is cited and that it is not for sale or any commercial purpose. Sale prohibited. Free distribution. The responsibility for the copyright of the texts and images of this work lies with the technical area. Elaboration, distribution and information Central Bank of Brazil Sul Banking Sector (SBS) Block 3 Block B - HQ Building Brasília – DF, ZIP Code: 70074-900 Website: https://www.bcb.gov.br for user experience MINIMUM REQUIREMENTS

9:30
01
Introduction
04
02
General Obligations and
Recommendations
05 - 10
03
Pix with Pix key
11 - 17
04
Pix with manual insertion of account data
18 - 21
10
46 - 52
My Keys
09
41 - 45
Return
11
53 - 62
My Pix Limits
16
104 - 114
Self-service MED
12
Scheduled Pix
63 - 69
13
Pix Copy and Paste
70 - 73
14
Pix Withdrawal and Pix Change
74 - 81
19
Pix in Internet Banking
122 - 127
18
Integration with Contact
List
120 - 121
17
Payment transaction initiation services in Pix 115 - 119 20 Accessibility in Pix 128 - 129
Annex I
130 - 137
21
Revision history
138 - 163
22
05
Generation of static
QR Code
22 - 25
06
Payment through static QR Code
26 - 31
07
32 - 38
Immediate payment or with due date through dynamic QR Code 08 39 - 40 Statement 82 - 103 15 Automatic Pix INDEX

4
This document was prepared with the objective of establishing minimum criteria for the adequate experience of users (payer and payee) in Pix transactions. The obligations contained herein are intended for applications designed for natural persons, given that this audience is more sensitive to user experience standardization. Considering that smartphones tend to be the main access channel for users to Pix, the minimum requirements for user experience are directed towards this device, with the exception of the experiences detailed in the chapter regarding the payment transaction initiation service, whose mandatory requirements are valid for all user payer service channels, and in the last chapter of this document, which deals with the availability of Pix on participants' websites on the internet. Participants acting as payment transaction initiation service providers (PSIs) must observe the provisions in the chapter dealing specifically with this service (chapter 17), being exempt from complying with the general obligations and recommendations contained in chapter 2. We also emphasize that participants must guarantee non-discriminatory treatment to users, including with respect to accessibility principles, in accordance with current legislation. The set of obligations and recommendations for each use case is accompanied by illustrative screens. These screens are merely exemplary, seeking to materialize and facilitate the understanding of the established commands. Thus, the content of these screens does not bind the development of applications to any parameter, and only the guidelines of the regulation, the obligations of this document as well as the Pix Brand Usage Manual regarding brand applications should be followed. We emphasize that this document is an integral part of the Pix regulation; therefore, the obligations contained therein must be followed by participants. Features not foreseen in this document will be accepted, provided they meet the user experience guidelines contained in the current regulation. 01 Introduction

General Obligations and Recommendations
This item addresses the general obligations and recommendations for all use cases. Recommendations and OBLIGATIONS Version: 7.3 December 2025 02

6
Version 7.3 General Obligations and Recommendations RECIPIENT: Payer user's PSP and Payee user's PSP 9:30 Pix Receive Pix Pix with QR Code Pix Copy and Paste Pix with Key / Manual My Pix Limits Pix Automatic Statement / Return My keys R$30.00 Amount João da Silva R$10.00 Amount Payment via Key Roberto da Silva LAST TRANSACTIONS Cell phone CPF Key Random E-mail Balance: R$ 1,000.00 Nadir da Silva 9:30 Other Pix services Open your account LOGIN NADIR PSP XYZ 9:30 Statements Investments Pix Transfer PSP XYZ Hello, Nadir! Branch: 1234 Account: 9999-9 R$ 1,000.00 Available balance 05 01 User has access to the specific Pix environment after pressing the specific buttons/ icons. Example of Pix environment 05 All of the following payment initiation forms must be offered to the user:

Pix key insertion;
QR Code reading;
Insertion of PSP, branch, transactional account and CPF/CNPJ of the payee user;
Insertion of Pix Copy and Paste.
04
It is mandatory that, upon first access to the dedicated Pix environment, the user is informed about the new payment method, addressing, at a minimum, the main characteristics:
Speed (transaction carried out in a few seconds);
Availability (any day and any time);
Convenience (simple and practical experience);
Cost (if natural person – free of charge, if user subject to fees, inform the cost);
Initiation forms (key, QR code).
03
If the participant makes the Pix environment available on the login screen, it must adopt one of the following actions:
Make access to the dedicated Pix environment available on the screen immediately
after login;
Insert the Pix option in all menus and submenus of the application related to
payments or transfers, with no less prominence than other payment methods. 02 If the participant's application has payment and/or receipt functionalities on the login screen, it must necessarily make access available to the Pix environment on this screen. 01 The Pix environment must be accessible at any time in the main application of each participant. Whenever applicable, its access must be on the login screen or on the screen immediately after login, with no less prominence than any other payment or transfer functionality. Mandatory

7
Version 7.3 General Obligations and Recommendations RECIPIENT: Payer user's PSP 9:30 Recipient / Amount Balance: R$ 1,000.00 Continue Type branch and account Cell phone CPF Key random E-mail Select key type +55 (00) 0 0000 0000 ? If you do not have a key for addressing the recipient, use the "Type branch and account" button to perform a Manual Pix. Description (optional) 0 of 140 characters Small description of the transaction R$ 0.00 Amount 9:30 Pix Pix with Key / Manual Pix Copy and Paste Pix with QR Code Receive Pix My Pix Limits Pix Automatic Statement / Return My keys R$10.00 Amount Payment via Key Roberto da Silva R$30.00 Amount João da Silva LAST TRANSACTIONS Cell phone CPF Key Random E-mail Balance: R$ 1,000.00 Nadir da Silva 07 To access manual payment initiation (branch/ account), it is suggested to insert this option within the menu “Pix with Key / Manual”, as the greater incentive is for the use of keys. The user selects the key type and performs the search. The app will check in the DICT and return success (result) or an error. 09 The payer user must be notified by their PSP, in case the transaction is suspected of fraud, whenever the PSP needs to use additional time to analyze the transaction. During the period in which the payment order is being analyzed, the Pix participant must make available, for the payer user, the option to cancel the transaction. Mandatory message: It must highlight that the transaction requires additional analysis time to be authorized and give the option to cancel the transaction. Examples:

We need an additional 30 minutes to analyze your transaction. Do you want to cancel the
Pix?
Your transaction needs approximately 60 minutes to be authorized. Do you want to
cancel the transaction?
08
Pix security validations should not generate more actions for users than those that the participating institution requires for other forms of payment. 07 The nomenclatures "Pix", "Key" or "Pix Key", "My keys", “Portability”, “Claim”, “Random key”, “Pix Copy and Paste”, “My Limits”, “Pix Withdrawal”, “Pix Change”, “Scheduled Pix” and “Automatic Pix” are mandatory. 06 All success, error and user orientation messages specified in this document in mandatory items must present the minimum content indicated, each PSP may complement and adjust the wording in a way compatible with the language used in its platform. Other messages aimed at orienting the user may be added, at the participant's discretion. Mandatory

8
Version 7.3 General Obligations and Recommendations RECIPIENT: Payer user's PSP 9:30 Pix Pix with Key / Manual Pix Copy and Paste Pix with QR Code Receive Pix R$10.00 Amount Payment via Key Roberto da Silva R$30.00 Amount João da Silva LAST TRANSACTIONS Cell phone CPF Key Random E-mail Balance: R$ 1,000.00 Nadir da Silva Complain here My Pix Limits Pix Automatic Statement / Return For other types of complaints, contact our Customer Service Center If your complaint is not resolved, you can register a complaint on the Central Bank of Brazil website. Customer Service Center MED To contest Pix in cases of fraud or unjustified charge in Automatic Pix, click on MED OR 9:30 Pix Pix with Key / Manual Pix Copy and Paste Pix with QR Code Receive Pix Pix Locations Withdrawal / Change Complain here Contest Pix MED Pix Installment 2x R$10.00 Amount Payment via Key Roberto da Silva R$30.00 Amount João da Silva LAST TRANSACTIONS Cell phone CPF Key Random E-mail Balance: R$ 1,000.00 Nadir da Silva 10 11 10 11 An informative message must be made available in the Pix environment, next to the shortcut to the participant's service channel, for the user to register a complaint on the Central Bank's website if the occurrence is not resolved by the PSP. 10 A shortcut must be made available on the Pix environment home screen that the user can easily access and identify as the path to the service channel provided by the PSP for handling complaints involving Pix, including those related to the Special Return Mechanism and frauds. Upon clicking this shortcut, the user must be immediately directed to said channel, without having to go through intermediate steps. Mandatory

9
Version 7.3 General Obligations and Recommendations RECIPIENT: Payee user's PSP 9:30 Camera E-mail PSP XYZ 20 Calendar Pix received from Fernanda Costa, CPF: *** .777.888 -** Amount: R$10.00 PSP XYZ - 15:00 12 13 In QR Code Pix transactions, the payee user must receive notification as soon as the transaction is completed. The method of sending the notification is at the free choice of the PSP. The notification must contain, at a minimum, the following information:

Payer's name (available in the settlement message), masked CPF (e.g.
*.777.888-)/CNPJ, transaction amount, message from the “Identifier” field (TxId), whenever it is filled in, and the amount of the fee charged, if there is a charge in accordance with current regulation;
The “Identifier” field refers to the “TxId” of the pacs.008;
If the notification is via push, part of the information, at the PSP's choice, may be
detailed when the user clicks on the notification;
In Pix Cobrança transactions for payment with a due date where there is
scheduling, the payee user must receive notification of the transaction settlement, the method of sending the notification being at the free choice of the PSP. The notification must contain the same information specified for QR Code Pix transactions and, preferably, be sent during daytime hours. 12 In Pix transactions with key or manual data insertion, the payee user must receive notification as soon as the transaction is completed. The method of sending the notification is at the free choice of the PSP. The notification must contain, at a minimum, the following information:
Payer's name (available in the settlement message), masked CPF (e.g.
*.777.888-)/CNPJ, transaction amount, message from the “Description” field, whenever it is filled in, and the amount of the fee charged, if there is a charge in accordance with current regulation;
The “Description” field refers to “informacoesEntreUsuarios” in the pacs.008;
The “Description” field must not contain HTML tags. The payer user's application must
display the characters of this field literally and, therefore, must not render links or any dynamic content.
If the notification is via push, part of the information, at the PSP's choice, may be
detailed when the user clicks on the notification;
In Scheduled Pix transactions, the payee user must receive notification of the
transaction settlement, the method of sending the notification being at the free choice of the PSP. The notification must contain the same information specified for transactions Pix with key or manual data insertion and, preferably, be sent during daytime hours. Mandatory

10
Version 7.3 General Obligations and Recommendations RECIPIENT: Payer user's PSP 9:30 Pix Statement / Receipt Balance: R$ 1,000.00 Share Save to cell phone PSP: PSP ABCD PSI: PSI EFGH CPF/CNPJ: *** .777.888 -** Transaction ID: 885544774112269 Amount received: R$ 10.00 Description: Barbecue Date/Time: 01/21/2020 at 21:34:05 Fernanda Costa Payment - Pix via Key ENTRY 9:30 Pix Statement / All Balance: R$ 1,000.00 Receipts with or without return Pix via QR Code Pix via Key or Manual All Search Receipt - Pix via QR Code Date/Time: 05/01/2021 at 17:16:45 Roberto da Silva Amount received: R$ 5.00 (updated) Return Amount: R$ 40.00 Date/Time: 05/10/2021 at 10:31:42 Energia S/A Automatic Pix Amount received: R$ 10.00 Date/Time: 01/21/2020 at 21:34:05 Fernanda Costa Pix Receipt via Key Amount debited: R$ 100.00 Date/Time: 05/15/2021 at 21:34:05 João da Silva Pix via Key LAST ENTRIES 9:30 Receipt Balance: R$ 1,000.00 Share Save to cell phone Statement / Return Name: Nadir da Silva CPF: *** .222.333 -** DEBTOR INFORMATION Name: Store ABC CNPJ: 15.436.940/0001-03 PAYEE INFORMATION PIX CONFIRMED Amount: R$19.90 Date/time: 01/10/2024 - 9:30:56 ID/Transaction: 975342678309753 14 16 15 The participant cannot display the Pix key among the data returned from the DICT, nor save or make available the option to save, when the txId is filled in. 16 Payment receipts for Pix transactions must contain the “check” type icon prominently at the top of the document, in order to expressly differentiate it from the scheduling receipt. 17 The mandatory information and icons (“check” or “calendar clock”) present on the screens concluding Pix payment and transaction scheduling journeys must be made available also in the respective receipts generated for sharing purposes (pdf file or image). 14 The PSP must identify other Pix participants (including the PSI possibly involved), on the transaction receipt, by its shortened name, according to the list of participants made available on the SPI page on the Central Bank of Brazil website on the internet. In the case of PSIs, the list is on the Pix page on the same site. Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
03
This is Pix between users through the use of a Pix key.
Pix with Pix Key

12
Version 7.3 Pix with Pix Key
RECIPIENT: Payer user's PSP
9:30
Recipient / Amount
Balance: R$ 1,000.00
Continue Type branch and account
Cell phone CPF Key random E-mail
Select key type ?
If you do not have a key for addressing the recipient, use the "Type branch and account" button to perform a Manual Pix. Description (optional) Small description of the transaction 0 of 140 characters R$ 0.00 Amount +55 (61) 9 João da Silva 61 99222-2222 61 98666-6666 Henrique Oliveira Guilherme Souza 61 99555-5555 Fernanda Costa 61 98888-5555 9:30 Recipient / Amount Balance: R$ 1,000.00 Continue Type branch and account Cell phone CPF Key random E-mail Select key type +55 (00) 0 0000 0000 ? If you do not have a key for addressing the recipient, use the "Type branch and account" button to perform a Manual Pix. Description (optional) Small description of the transaction 0 of 140 characters R$ 0.00 Amount 02 03 02 01 The user selects the key type and performs the search. The app checks in the DICT and returns success (result) or an error. The “Description” field, optionally filled in by the user, must be presented for filling in.

In the formation of the pacs.008, the text of the “Description” field must be inserted in the field
“informacoesEntreUsuarios”.
The “Description” field must not contain HTML tags. The payer user's application must
display the characters of this field literally and, therefore, must not render links or any dynamic content. 03 When the user wishes to pay by key, no additional information about the payee user should be requested beyond the key chosen itself (CPF/CNPJ or cell phone number with DDI code, adopting +55 as the standard code, or e-mail). Likewise, the filling in of more than one key to identify the payee user should not be requested. 02 For payments with manual key insertion, at a minimum, the following key types must be accepted:
CPF/CNPJ, cell phone number, e-mail.
01
Mandatory

13
Version 7.3 Pix with Pix Key
RECIPIENT: Payer user's PSP
9:30
Recipient / Amount
Balance: R$ 1,000.00
Continue Type branch and account
Cell phone CPF Key random E-mail
Select key type
+55 (00) 0 0000 0000
?
If you do not have a key for addressing the recipient, use the "Type branch and account" button to perform a Manual Pix. Description (optional) Small description of the transaction 0 of 140 characters R$ 0.00 Amount +55 (61) 99999 9998 Understood Transaction not completed. Key unavailable. 9:30 Recipient / Amount Balance: R$ 1,000.00 Continue Type branch and account Cell phone CPF Key random E-mail Select key type +55 (00) 0 0000 0000 ? If you do not have a key for addressing the recipient, use the "Type branch and account" button to perform a Manual Pix. Description (optional) Small description of the transaction 0 of 140 characters R$ 0.00 Amount +55 (61) 9999999999999999 Understood Transaction not completed. Invalid key format (CPF/CNPJ, e-mail, cell phone or random key). 05 04 04 The app will not search in the DICT in this case. The app must identify the error and present it to the user. Limiting the number of characters (CPF/CNPJ) and applying a mask are solutions that help avoid these errors. The user selects the key type and performs the search. The app will check in the DICT and return success (result) or an error. When a key is sent to the DICT and the return is of an account or user with a restriction for receiving Pix transactions due to involvement in fraud, the payer user must be informed about this and about the impossibility of completing the transaction for this reason. Mandatory message: It must highlight that the destination account or payee user was involved in a transaction with a well-founded suspicion of fraud and that it is not possible to complete the transaction. Examples:

Account or payee involved in a transaction with a well-founded suspicion of fraud. It is not
possible to perform the Pix.
It is not possible to consult this Pix key. Payee involved in a transaction with
a well-founded suspicion of fraud.
06
When a key is sent to the DICT and the return is of a key not found or blocked, the payer user must be informed about the non-existence or unavailability of this key. Mandatory message: It must highlight that the transaction was not carried out and that the key is non-existent or unavailable. Examples:
Transaction not completed. Key unavailable.
Key not located. Try again.
An error occurred. It was not possible to find this key.
Error. Check if you entered the correct key.
Pix not completed. Check if the key is correct.
05
When the payer user enters a Pix key in a format incompatible with those accepted by Pix, the key should not be forwarded to the DICT and the user must be notified about the format error. Mandatory message: It must highlight that the transaction was not carried out and that there is a problem with the key format. Examples:
Transaction not completed. Invalid key format;
There was a problem with the key format. Try again;
An error occurred. Check the format of this key;
Your Pix was not completed. Check the format of the key entered.
04
Mandatory

Mandatory
The selection of the key must return the payee user's data for verification: full name, masked CPF (e.g. *.777.888-)/CNPJ, Pix key, as well as amount and option to cancel the transaction before confirming the payment. The branch number and the payee's account number must not be returned to the payer user. The return of the payee PSP's name information is optional and is at the participant's discretion.

Full name;

Masked CPF (e.g. *.777.888-)/CNPJ;

Pix Key;

Amount field;

Cancel option. This option is not necessarily a Cancel button. It is merely the cancellation functionality available before the conclusion of the transaction. Its implementation aims to reduce the number of returns of erroneous transactions;

In the case of CNPJ, the name provided must be the Company's Trade Name, if it exists. If it does not exist, the name provided must be the Company's Name/Legal Name;

There must be no masking of the Pix key in the return of the DICT query, in order to allow the verification of the key data by the payer user before confirming the payment. 07 If there is a communication failure with the DICT, the payer user must be informed about this situation.

Mandatory message: It must highlight that the transaction was not carried out and that there was a technical or communication problem. Examples:

Transaction not completed. Communication failure. Try again;

Your Pix was not finalized. We had a technical problem. Try again;

Sorry, we had a communication problem. Try again.
08
If any type of credit is used to make the payment, the payer user must be informed of this before confirming the payment.

Mandatory message: It must highlight the amount and the credit line that will be used.

Examples:

Attention: to complete the transaction, R$ XX.XX will be used from the/o [Name_of_credit_line]. To finalize this Pix, R$ [amount] will be withdrawn from the credit line [name of credit line]. 09 The user selects the key type and performs the search. The app will check in the DICT and return success (result) or an error. 9:30 Recipient / Amount Balance: R$ 1,000.00 Select key type ? Key

random Cell phone CPF E-mail
+55 (61) 99999 9999
Recipient information
Name: Fernanda Costa
CPF/CNPJ: *.777.888 - *
Amount
R$ 10.00
Description (optional)
Small description of the transaction
0 of 140 characters
If you do not have a key for addressing the recipient, use the "Type branch and account" button to perform a Manual Pix. Type branch

and account Continue
08
07
07
9:30
Recipient / Amount
Balance: R$ 1,000.00
Select key type ?
Key

Version 7.3 Pix with Pix Key

DESTINATION: Payer's PSP

9:30
Transfer Confirmation
Balance: R$ 1,000.00
Cancel Schedule Finalize

RECIPIENT INFORMATION
Name: Fernanda Costa
Key: 61 99999 9999
CPF/CNPJ: *.777.888 -
Description: Barbecue
Final Value
R$ 10.00

07 Cancel Schedule Finalize

9:30
Transfer Confirmation
Balance: R$ 0.00
Cancel Schedule Finalize

Key: 61 99999 9999
Name: Fernanda Costa
RECIPIENT INFORMATION
CPF/CNPJ: *.777.888 -
Description: Barbecue
R$ 10.00
Final Value

Understood

Transaction not completed.
Insufficient balance.

9:30
Transfer Confirmation
Balance: R$ 1,000.00
Cancel Schedule Finalize

Key: 61 99999 9999
Name: Fernanda Costa
RECIPIENT INFORMATION
CPF/CNPJ: *.777.888 -
Description: Barbecue
R$ 10.00
Final Value

Understood

Transaction not completed.
Processing error.

9:30
Transfer Confirmation
Balance: R$ 1,000.00
Cancel Schedule Finalize

R$ 10.00
Final Value
Description: Barbecue
CPF/CNPJ: *.777.888 -
Key: 61 99999 9999
Name: Fernanda Costa
RECIPIENT INFORMATION

Understood

Transaction not completed. Recipient account unavailable.

The alert regarding the lack of balance will occur when attempting to finalize the operation.

Before the option to confirm payment, the balance of the transaction account may be made available to the user.

Error messages in settlement must be specific and clear to the user, in order to highlight the actual reason for the non-processing of the transaction.

Mandatory messages: They must indicate that the transaction was not carried out and specify the problem that occurred in cases of insufficient balance, unavailable recipient account, non-existent recipient account, processing error or technical failure, or time exceeded.

In the event of settlement errors associated with processing, participant unavailability or time limit exceeded, it must be clear to the user that the error stems from the PSP itself.

Examples:

Try another value, insufficient balance.
Pix not performed, the balance you have was not enough.
You have no balance to finalize this Pix;
Transaction not completed. Recipient account unavailable.
Pix not completed. The account of the person you want to transfer to is not available.
Error. Recipient account unavailable;
Transaction not completed. Recipient account non-existent.
Pix not completed. The account of the person you want to transfer to does not exist.
Error. Recipient account non-existent;
Transaction not completed. Processing error. We had a failure processing your Pix. Try again.
Sorry, we had a technical failure. Try again.

Recommended
Mandatory

Version 7.3 Pix with Pix Key

DESTINATION: Payer's PSP and Payee's PSP

9:30
Receipt
Balance: R$ 990.00
Share Save on mobile
Statement /
Refund

Name: Nadir da Silva
CPF/CNPJ: *** .993.555 -**
PAYER INFORMATION
PSP: PSP XYZ
Name: Fernanda Costa
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
RECIPIENT INFORMATION
Transaction ID: 975342678309753
Date/time: 21/01/2020 - 21:34:05
Final Value: R$10.00
Description: Barbecue
PIX CONFIRMED

9:30
Statements Investments
Pix Transfer
2,010.00
Available
Balance
R$
Acct: 8888-8
Branch: 4321
Hello, Fernanda!
PSP ABCD

Make payment receipt available to payer and payee users during the period established in current regulation, containing, at minimum:

Name, CPF (masked or not)/CNPJ and name of the payer's PSP;
Name, CPF (masked or not)/CNPJ and name of the payee's PSP;
"Description" field (whenever filled);
Value and Transaction ID;
Date and time/minute/second (Brasília time) of settlement.

When the transaction involves an SFI, the name of the SFI must appear on the receipt. The message and minimum fields that must be presented to the user are represented on the screen to the side.

The Transaction ID refers to the "EndtoEndID" present in pacs.008;
The "Description" field refers to "informacoesEntreUsuarios" in pacs.008;
The "Description" field must not contain HTML tags. The payer's user application must display the characters of this field literally and, therefore, must not render links or any dynamic content.

The payer user must receive a notification as soon as the transaction is completed, including for scheduled transactions. The method of sending the notification is at the free choice of the PSP. The notification must contain, at minimum, the following information:

Payee name and transaction value.

Mandatory

Version 7.3 Pix with Pix Key

DESTINATION: Payer's PSP and Payee's PSP

For random keys, it is recommended:

Inform, to the user, the 32 characters that make up their random key;
Inform, to the user, that the random key was created primarily to be used in the QR Code;
Do not allow the assignment of "nicknames" for the random key. This practice may confuse users, who may conclude that the "nickname" is the random key itself and try to receive Pix through this "nickname";
Allow the random key to be copied, in the "My keys" environment, in order to facilitate its sharing;
Allow the random key to be pasted in the space provided for typing the key.

Recommended

December 2025
Version: 7.3
Recommendations and OBLIGATIONS

This is Pix between users through the manual insertion by the payer user of the transaction account data of the payee user. Pix with manual insertion of transaction account data

Version 7.3 Pix with manual insertion of transaction account data

DESTINATION: Payer's PSP

9:30
Recipient / Value
Balance: R$ 1,000.00
Cancel Schedule Finalize
Yes No
Add as favorite?
Small description of the transaction
0 of 140 characters
Description (optional)
R$ 10.00
Final Value
PSP: PSP ABCD
Name: Fernanda Costa
CPF/CNPJ: *.777.888 -
Account: 88888-8
Branch: 9999
RECIPIENT INFORMATION

9:30
Recipient / Value
Balance: R$ 1,000.00
Continue Select a favorite
R$ 0.00
Value
CPF/CNPJ
Yes No
Same ownership?
Checking Savings Payment account
What type of account?
With check digit
Branch Account
Select the PSP

In this case, it is the same procedure as performing a TED/DOC.

If any type of credit is used to make the payment, the payer user must be informed of this before confirming the payment. Mandatory message: It must indicate the value and the credit line that will be used. Examples:

Attention: to complete the transaction, R$ XX.XX from the [Credit_Line_Name] will be used/To finalize this Pix, R$ [value] will be withdrawn from the credit line [name of the credit line].

It is mandatory to have a field for entering the value and another for typing the "Description" field, as well as an option to cancel the transaction before confirming the payment.

Cancel Option. This option is not necessarily a "Cancel" button. It is simply the cancellation functionality available before the completion of the transaction. Its implementation aims to reduce the number of returns of erroneous transactions.
In the formation of pacs.008, the text of the "Description" field must be inserted into the "informacoesEntreUsuarios" field.
The "Description" field must not contain HTML tags. The payer's user application must display the characters of this field literally and, therefore, must not render links or any dynamic content.

Return the payee's name, based on the data typed by the payer, before confirming the transaction.

Name, fields related to the transaction account, CPF/CNPJ.

The fields related to the transaction account, CPF/CNPJ and "Description" field (optional filling by the user) must be presented for filling.

Fields related to the transaction account, CPF/CNPJ, "Description" field.

The number associated with each PSP, only for the purpose of searching for PSPs by their users, can be either the PSP code number or its ISPB, at the discretion of each participant. Special liquidating participants cannot appear in the list of participating institutions.

Mandatory

Version 7.3 Pix with manual insertion of transaction account data

DESTINATION: Payer's PSP

9:30
Recipient / Value
Balance: R$ 0.00
Cancel Schedule Finalize
Yes No
Add as favorite?
0 of 140 characters
Description (optional)
Small description of the transaction
R$ 10.00
Final Value
CPF/CNPJ: *.777.888 -
Account: 88888-8
Branch: 9999
PSP: PSP ABCD
Name: Fernanda Costa
RECIPIENT INFORMATION

Understood
Transaction not completed.
Insufficient balance.

9:30
Recipient / Value
Balance: R$ 1,000.00
Yes No
Add as favorite?
0 of 140 characters
Description (optional)
Small description of the transaction
R$ 10.00
Final Value
CPF/CNPJ: *.777.888 -
Account: 88888-8
Branch: 9999
PSP: PSP ABCD
Name: Fernanda Costa
RECIPIENT INFORMATION

Understood
Transaction not completed.
Recipient account unavailable.

9:30
Recipient / Value
Balance: R$ 1,000.00
Cancel Schedule Finalize
Yes No
Add as favorite?
0 of 140 characters
Description (optional)
Small description of the transaction
R$ 10.00
Final Value
CPF/CNPJ: *.777.888 -
Account: 88888-8
Branch: 9999
PSP: PSP ABCD
Name: Fernanda Costa
RECIPIENT INFORMATION

Understood
Transaction not completed. Processing time exceeded.
Try again.

The alert regarding the lack of balance will occur when attempting to finalize the operation.

Before the option to confirm payment, the balance of the transaction account may be made available to the user. 06

Error messages in settlement must be specific and clear to the user, in order to highlight the actual reason for the non-processing of the transaction. Mandatory messages: They must indicate that the transaction was not carried out and specify the problem that occurred in cases of insufficient balance, unavailable recipient account, non-existent recipient account, processing error or technical failure, or time exceeded. In the event of settlement errors associated with processing, participant unavailability or time limit exceeded, it must be clear to the user that the error stems from the PSP itself. Examples:

Try another value, insufficient balance.
Pix not performed, the balance you have was not enough.
You have no balance to finalize this Pix.
Transaction not completed. Recipient account unavailable.
Pix not completed. The account of the person you want to transfer to is not available.
Error. Recipient account unavailable.
Transaction not completed. Recipient account non-existent.
Pix not completed. The account of the person you want to transfer to does not exist.
Error. Recipient account non-existent.
Transaction not completed. Processing error. We had a failure processing your Pix. Try again.
Sorry, we had a technical failure. Try again.

Mandatory
Recommended

Version 7.3 Pix with manual insertion of transaction account data

DESTINATION: Payer's PSP and Payee's PSP

9:30
Receipt
Balance: R$ 990.00
Share Save on mobile
Statement /
Refund

Name: Nadir da Silva
CPF/CNPJ: *** .993.555 -**
PSP: PSP XYZ
PAYER INFORMATION
Name: Fernanda Costa
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
RECIPIENT INFORMATION
Transaction ID: 885544756782258
Date/time: 21/01/2020 - 21:34:05
Final Value: R$10.00
Description: Barbecue
PIX CONFIRMED

9:30
Statements Investments
Pix Transfer
2,010.00
Available
Balance
R$
Acct: 8888-8
Branch: 4321
Hello, Fernanda!
PSP ABCD

Make payment receipt available to payer and payee users during the period established in current regulation, containing, at minimum:

Name, CPF (masked or not)/CNPJ and name of the payer's PSP;
Name, CPF (masked or not)/CNPJ and name of the payee's PSP;
"Description" field (whenever filled),
Value and Transaction ID;
Date and time/minute/second (Brasília time) of settlement.

When the transaction involves an SFI, the name of the SFI must appear on the receipt. The message and minimum fields that must be presented to the user are represented on the screen to the side.

The Transaction ID refers to the "EndtoEndID" present in pacs.008;
The "Description" field refers to "informacoesEntreUsuarios" in pacs.008;
The "Description" field must not contain HTML tags. The payer's user application must display the characters of this field literally and, therefore, must not render links or any dynamic content.

Payee name and transaction value.

Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS

This is the generation of a static QR Code and the receipt by the payee user of a transaction initiated with this QR Code. Generation of static QR Code

Version 7.3 Generation of static QR Code

DESTINATION: Payee's PSP

9:30
Receive
Balance: R$ 1,000.00
Advanced Continue
Cell Phone CPF Random
Key Email
Select the type of key
+55 (00) 0 0000 0000
?
?
?
Value (optional)
Identifier (optional)
Small description of the transaction
0 of 25 characters
R$ 0.00

9:30
Pix
Pix with
Key / Manual
Pix Copy and Paste
Pix with
QR Code Receive Pix
My limits Pix
Pix
Automatic
Statement /
Refund
My keys
R$10.00
Value Payment via Key
Roberto da Silva
R$30.00
Value
João da Silva
LAST TRANSACTIONS
Cell Phone
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva

The user must link a type of key with the PSP.
We suggest that means be made available to help the user with this new understanding.

The payee user must be given the possibility to generate the static QR Code from the four keys:

Cell phone number, email, CPF/CNPJ or random key.

01 The Receive Pix option must be highlighted and easily accessible to the user.

Mandatory

Version 7.3 Generation of static QR Code

DESTINATION: Payee's PSP

9:30
Receive
Balance: R$ 1,000.00
Advanced Continue
Key
Cell Phone CPF Email
Select the type of key ?
?
?
0 of 25 characters
Small description of the transaction
Identifier (optional)
Value (optional)
R$ 0.00
Key: +55 61 98888-8888
Understood

Question: The key is necessary to be able to receive a Pix in a practical way. Learn more.

Question: The Identifier and Value fields are optional for creating the QR Code. If you do not specify the value, the field will be filled in by the payer.

Select or register a key before performing this action.

The user will be notified when pressing the help icon.
When trying to continue without the selection of a key, the user will be alerted regarding its mandatory nature.

When generating the static QR Code, if the user does not have any registered key, a message must be presented informing this need and redirecting them to the Pix key registration screen.

Optional fields (identifier and value) must be presented, emphasizing to the user that they are not mandatory to fill in.

Identifier and value;
The Identifier field refers to the "TxId" field in pacs.008 and is used by the
receiver to reconcile their receipts.

Mandatory
Recommended

Version 7.3 Generation of static QR Code

DESTINATION: Payee's PSP

9:30
Pix
Balance: R$ 1,000.00
Receive
Pix Copy and
Paste Share Save on mobile
Change
Pix Key
Insert identifier
Change value
Show or share this QR Code or the Pix
Copy and Paste to receive the Pix.
SUCCESS!
Receiver

9:30
Receive
Balance: R$ 1,000.00
Pix Copy and
Paste Share Save on mobile
Change
Pix Key
Insert identifier
Change value
Show or share this QR Code or the Pix
Copy and Paste to receive the Pix.
SUCCESS!
Understood
QR Code created successfully! The data will be visible when read by the payer. Receiver

9:30
Transfer Confirmation
Balance: R$ 1,000.00
Cancel Schedule Finalize
R$ 10.00
Final Value
Identifier: Barbecue
PSP: PSP XYZ
CPF/CNPJ: *.993.555 -
Name: Nadir da Silva
RECIPIENT INFORMATION
Payer

08 07

As can be seen on the payer's screen, all data are visible when read by the QR code reader.

08 Provide option to save QR Code image on the user's mobile device.

07 Provide option to Copy QR Code to enable the Pix Copy and Paste functionality.

06 Provide option to share the QR Code image.

05
Inform that the data filled in when generating the static QR Code will be viewed by the user who reads this QR Code.

Recommended
Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS

This is payment initiated by the payer user through the reading of a static QR Code. Payment through static QR Code

Version 7.3 Payment through static QR Code

DESTINATION: Payer's PSP

9:30
Pay with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Point the camera at a Pix QR Code
Payment - Static QR Code

9:30
Recipient / Value
Balance: R$ 1,000.00
Cancel Schedule Finalize
R$ 10.00
Final Value
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
Name: Fernanda Costa
RECIPIENT INFORMATION

9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
My limits Pix
Pix
Automatic
Statement /
Refund
My keys
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell Phone
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva

When choosing payment with QR Code, the user will be directed to read the QR Code. Here other options are suggested for payment in case the QR Code does not work. After reading the QR Code, the user will be directed to an area with information about the payment and DICT information.

Payer user can cancel payment, but cannot edit data read from the QR Code.

Before confirming the payment, the DICT data about the payee user must be returned to the payer user:

Name, CPF (masked) / CNPJ (unmasked) and value read from the QR Code (if any).
The branch number and account number of the payee must not be returned to the payer user.
The return of the payee's PSP name information is optional and is at the discretion of
the participant. In the case of CNPJ, the name provided must be the Trade Name of the company, if it exists. If it does not exist, the name provided must be the Legal Name/Corporate Name;
Cancel Option. This option is not necessarily a "Cancel" button. It is simply
the cancellation functionality available before the completion of the transaction. Its implementation aims to reduce the number of returns of erroneous transactions.
The "Description" field ("informacoesEntreUsuarios" in pacs.008) must not be made available for the payer user to fill in transactions initiated by QR
Code.

Mandatory

Version 7.3 Payment through static QR Code

DESTINATION: Payer's PSP

9:30
Transfer Confirmation
Balance: R$ 1,000.00
Cancel Schedule Finalize
R$ 10.00
Final Value
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
Name: Fernanda Costa
RECIPIENT INFORMATION

9:30
Recipient / Value
Balance: R$ 1,000.00
Cancel Continue
R$ 0.00
Value
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
Name: Fernanda Costa
RECIPIENT INFORMATION

In this case, the payee user did not fill in any data in the QR Code since all are optional.

Attention: to complete the transaction, R$ XX.XX from the [Credit_Line_Name] will be used/To finalize this Pix, R$ [value] will be withdrawn from the credit line [name of the credit line].

If there is no value in the static QR Code, the payer user must enter it before confirming the payment.

If there is a value in the static QR Code, this field cannot be changed by the payer user.

Mandatory

29
Version 7.3 Payment via Static QR Code
RECIPIENT: PSP of the payer user
9:30
Pay with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Transaction not completed.
Invalid QR Code.
9:30
Pay with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Transaction not completed.
Key unavailable.
9:30
Pay with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Transaction not completed. Communication failure.
Try again.
09
07
06
09 The user must be informed if the scanned QR Code is invalid.
08
The payer must be informed about an error resulting from reading a QR Code with a key linked to an account or user with restrictions on receiving Pix transactions due to involvement in fraud, and the impossibility of concluding the transaction for this reason. Mandatory message: It must indicate that the destination account or receiving user was involved in a transaction with a well-founded suspicion of fraud and that it is not possible to conclude the transaction. Examples:

Account or receiver involved in a transaction with a well-founded suspicion of fraud. It is not possible to perform the Pix.
Destination account involved in a transaction with a well-founded suspicion of fraud. The Pix cannot be performed.
07
The payer must be informed about an error resulting from reading a QR Code with a non-existent or blocked key. Mandatory message: It must indicate that the transaction was not performed and that the key is non-existent or unavailable. Examples:
Transaction not completed. Key unavailable;
Key not found. Try again;
An error occurred. It was not possible to find this key.
06
If a communication failure occurs with the DICT, the payer user must be informed about this situation. Mandatory message: It must indicate that the transaction was not performed and that there was a technical or communication problem. Examples:
Transaction not completed. Communication failure. Try again;
Your Pix was not finalized. We had a technical problem. Try again;
Sorry, we had a communication problem. Try again.
Mandatory

30
Version 7.3 Payment via Static QR Code
RECIPIENT: PSP of the payer user
9:30
Transfer Confirmation
Balance: R$ 0.00
Cancel Finalize
R$ 10.00
Final Value
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
Name: Fernanda Costa
RECIPIENT INFORMATION
I understand
Transaction not completed.
Insufficient balance.
9:30
Transfer Confirmation
Balance: R$ 1,000.00
Cancel Finalize
R$ 10.00
Final Value
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
Name: Fernanda Costa
RECIPIENT INFORMATION
I understand
Transaction not completed. Processing time exceeded. Try again.
11
11
10
The insufficient balance alert will occur when attempting to finalize the operation. 11 Before the option to confirm payment, the balance of the transactional account may be made available to the user. 10 Error messages during settlement must be specific and clear to the user, in order to indicate the effective reason for the non-processing of the transaction. Mandatory messages: They must indicate that the transaction was not performed and specify the problem occurring in cases of insufficient balance, unavailable receiver account, non-existent receiver account, processing error, or technical failure, time exceeded. In the event of settlement errors associated with processing, participant unavailability, or time limit exceeded, it must be clear to the user that the error stems from the PSP itself. Examples:

Try another value, insufficient balance;
Pix not performed, the balance you have was not sufficient;
You do not have a balance to finalize this Pix;
Transaction not completed. Receiver account unavailable;
Pix not completed. The account of the person you want to transfer to is not available;
Error. Receiver account unavailable;
Transaction not completed. Receiver account non-existent;
Pix not completed. The account of the person you want to transfer to does not exist;
Error. Receiver account non-existent;
Transaction not completed. Processing error. We had a failure processing your Pix. Try again;
Sorry, we had a technical failure. Try again.
Recommended
Mandatory

31
Version 7.3 Payment via Static QR Code
RECIPIENT: PSP of the payer user and PSP of the receiver user 9:30 Receipt Balance: R$ 990.00 Share Save on mobile Statement / Refund PSP: PSP XYZ CPF/CNPJ: * .993.555 - Name: Nadir da Silva PAYER INFORMATION PSP: PSP ABCD CPF/CNPJ: *.777.888 - Name: Fernanda Costa RECIPIENT INFORMATION Identifier: BBQ Final Value: R$10.00 Date/Time: 21/01/2020 - 21:34:05 Transaction ID: 885544756782258 PIX CONFIRMED 9:30 Statements Investments Pix Transfer 2,010.00 Available Balance R$ Cc: 8888-8 Ag: 4321 Hello, Fernanda! PSP ABCD 13 13 12 14 The PSP cannot save the Pix key nor should it provide an option to save the Pix key linked to the Static QR Code payment when the TxId is filled. 13 Make a payment receipt available to payer and receiver users during the period established in the current regulation, containing, at minimum:

Name, CPF (masked or not)/CNPJ and name of the PSP of the payer user;
Name, CPF (masked or not)/CNPJ and name of the PSP of the receiver user;
Message from the "Identifier" field (TxId), whenever filled;
Value and Transaction ID;
Date and time/minute/second (Brasília time) of settlement.
When the transaction involves a PSI, the name of the PSI must appear on the receipt. The display of the Pix key linked to the Static QR Code and the banking data (branch and account) of the receiver on the payment receipt is prohibited when the "Identifier" field (TxId) is filled. The message and minimum fields that must be presented to the user are shown in the screen on the side.
The Transaction ID refers to the "EndtoEndID" present in pacs.008.
12
The payer user must receive a notification as soon as the transaction is completed. The method of sending the notification is at the free choice of the PSP. The notification must contain, at minimum, the following information:
Receiver name and transaction value.
Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
07
This is a payment initiated by the payer user through reading a dynamic QR Code. Immediate payment or payment with maturity via Dynamic QR Code

33
Version 7.3 Immediate payment or payment with maturity via Dynamic QR Code RECIPIENT: PSP of the payer user and PSP of the receiver user 9:30 Receiver / Value Cancel Finalize Balance: R$ 1,000.00 R$ 824.00 Final Value Interest: 1% Interest/Period: Per month Fine: 2% Fine/Period: After 15/02/2021 Lot number: 123456 Discount: 10% until 10/02/2021 ADDITIONAL INFORMATION CPF/CNPJ: * .222.333 - Name: Roberdo da Silva DEBTOR INFORMATION Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Original Value: R$ 800.00 GENERAL INFORMATION Interest: R$ 8.00 Fine: R$ 16.00 Payment Date Maturity Date:
PAYMENT WITH MATURITY
15/02/2021
Today At maturity Schedule
Payment with maturity
9:30
Receiver / Value
Balance: R$ 1,000.00
Cancel Schedule Finalize
R$ 800.00
Final Value
Name: Nadir da Silva
Name: Roberto da Silva
CPF/CNPJ: * .993.555 -
CPF/CNPJ: * .222.333 -
PSP: PSP XYZ
DEBTOR INFORMATION
RECIPIENT INFORMATION
Immediate payment
9:30
Pix with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Point the camera at a Pix
QR Code
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
My limits Pix
Pix
Automatic
Statement /
Refund
My keys
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Mobile
CPF
Key
Random
E-mail
Balance: R$ 1,000.00
Nadir da Silva
01
02
02
When choosing payment via QR
Code, the user will be directed to perform the reading. Here other payment options are suggested in case the QR Code does not work. After reading the QR Code, the user will be directed to an area with information about the payment and DICT information. Example reading QR Code. 02 The payer user can cancel the payment, but cannot edit the QR Code data, except for the value (if allowed by the receiver user) and the field for requesting information from the payer (if any). 01 Before confirming the immediate payment, the following data must be returned to the payer user, using the DICT data on the receiver user in the applicable fields:

Name and CPF (masked) / CNPJ (unmasked) of the receiver. In the case of CNPJ, the name provided must be the Company Trade Name, if it exists. If it does not exist, the name provided must be the Company Name/Legal Name. The branch number and account number of the receiver must not be returned to the payer user. The return of the receiver PSP name information is optional and is at the participant's discretion;
Debtor data (CPF/CNPJ and Name), if provided;
The "infoAdicionais" field, if provided, must contain only characters or HTML without any dynamic content, such as scripts (javascript, php, cgi, among others);
The "Request to Payer" field, if provided: description and text box for the payer user to fill in;
The value (If the receiver user indicates that the value can be changed using the "Value Change Modality" field, as defined in the Pix Initiation Standards Manual, the payer user must be allowed to edit the value. Otherwise, the value cannot be editable).
The "Description" field ("informacoesEntreUsuarios" from pacs.008) must not be made available for the payer user to fill in transactions initiated by QR Code. Mandatory

34
Version 7.3 Immediate payment or payment with maturity via Dynamic QR Code RECIPIENT: PSP of the payer user and PSP of the receiver user 9:30 Receiver / Value Cancel Continue Balance: R$ 1,000.00 R$ 824.00 Final Value Interest: 1% Interest/Period: Per month Fine: 2% Fine/Period: After 15/02/2021 Lot number: 123456 Discount: 10% until 10/02/2021 ADDITIONAL INFORMATION CPF/CNPJ: * .222.333 - Name: Roberdo da Silva DEBTOR INFORMATION Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Original Value: R$ 800.00 GENERAL INFORMATION Interest: R$ 8.00 Fine: R$ 16.00 PAYMENT WITH MATURITY Today At maturity Schedule Payment Date Maturity Date: 15/02/2021 Payment with maturity 03 03 Before confirming the payment with maturity, the following data must be returned to the payer user, using the DICT data on the receiver user in the applicable fields.

Maturity date field;
Options for the payer, if they wish, to inform the Intended Payment Date (DPP), defined in the Pix Initiation Standards Manual, for the same day, the maturity date, or a scheduled date;
Values: original, deduction, discount, interest, fine (if provided), and final value;
Name and CPF (masked) / CNPJ (unmasked) of the receiver. In the case of CNPJ, the name provided must be the Company Trade Name, if it exists. If it does not exist, the name provided must be the Company Name/Legal Name. The branch number and account number of the receiver must not be returned to the payer user. The return of the receiver PSP name information is optional and is at the participant's discretion;
Debtor data (CPF/CNPJ and Name);
The "infoAdicionais" field, if provided, as defined in the Pix Initiation Standards Manual, must be used to indicate the rules governing the calculation of the charge value (discounts, interest, and fines), among other information the receiver user wishes to transmit to the payer user;
The "infoAdicionais" field must contain only characters or HTML without any dynamic content, such as scripts (javascript, php, cgi, among others);
The "Request to Payer" field, if provided: description and text box for the payer user to fill in;
Receiver address fields: State (UF); City; Street and ZIP Code (this information may be made available to the user through another object, such as an icon or button). The "Description" field ("informacoesEntreUsuarios" from pacs.008) must not be made available for the payer user to fill in transactions initiated by QR Code.
Mandatory

35
Version 7.3 Immediate payment or payment with maturity via Dynamic QR Code RECIPIENT: PSP of the payer user 9:30 Receiver / Value Cancel Finalize Balance: R$ 1,000.00 R$ 824.00 Final Value Interest: 1% Interest/Period: Per month Fine: 2% Fine/Period: After 15/02/2021 Lot number: 123456 Discount: 10% until 10/02/2021 ADDITIONAL INFORMATION CPF/CNPJ: * .222.333 - Name: Roberdo da Silva DEBTOR INFORMATION Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Original Value: R$ 800.00 GENERAL INFORMATION Interest: R$ 8.00 Fine: R$ 16.00 Payment Date Maturity Date:
PAYMENT WITH MATURITY
15/02/2021
Today At maturity Schedule
Intended Payment Date:
Maturity Date:
I understand
Transaction not completed.
Insufficient balance.
9:30
Pix with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Transaction not completed.
Communication failure.
Try again.
9:30
Pix with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Transaction not completed.
Invalid QR Code.
07
07 06
04
07
Before the option to confirm payment, the balance of the transactional account may be made available to the user. 06 The user must be informed if the scanned QR Code is invalid. 05 If any type of credit is used, the payer user must be informed of this before confirming the payment. Mandatory message: It must indicate the value and the credit line that will be used. Examples:

Attention: to complete the transaction, R$hXX,XX of the/[Credit_Line_Name] will be used/To finalize this Pix, R$ [value] will be withdrawn from credit line [credit line name].
04
When the receiver PSP is unavailable to query the data of the dynamic QR Code payload, the payer PSP must send specific communication to the payer user about this situation. Mandatory message: It must indicate that the transaction was not performed and that there was a technical or communication problem. Examples:
Transaction not completed. Communication failure. Try again.
Your Pix was not finalized. We had a technical problem.
Sorry, we had a communication problem. Try again.
Recommended
Mandatory

36
Version 7.3 Immediate payment or payment with maturity via Dynamic QR Code RECIPIENT: PSP of the payer user 9:30 Receiver / Value Cancel Continue Balance: R$ 1,000.00 R$ 824.00 Final Value Interest: 1% Interest/Period: Per month Fine: 2% Fine/Period: After 15/02/2021 Lot number: 123456 Discount: 10% until 10/02/2021 ADDITIONAL INFORMATION CPF/CNPJ: * .222.333 - Name: Roberdo da Silva DEBTOR INFORMATION Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Original Value: R$ 800.00 GENERAL INFORMATION Interest: R$ 8.00 Fine: R$ 16.00 PAYMENT WITH MATURITY Today At maturity Schedule Intended Payment Date:
Maturity Date: 15/02/2021
Payment with maturity
08
09
10
The payer must be informed about an error resulting from reading a QR Code with a key linked to an account or user with restrictions on receiving Pix transactions due to involvement in fraud, and the impossibility of concluding the transaction for this reason. Mandatory message: It must indicate that the destination account or receiving user was involved in a transaction with a well-founded suspicion of fraud and that it is not possible to conclude the transaction. Examples:

Account or receiver involved in a transaction with a well-founded suspicion of fraud. It is not possible to perform the Pix.
Destination account involved in a transaction with a well-founded suspicion of fraud. The Pix cannot be performed.
09
If the QR Code expiration period has been exceeded, the payer user must be notified about this. The message must indicate that the transaction was not completed and specify the error. Examples:
Transaction not completed. Invalid QR Code;
Error performing Pix. Invalid QR Code.
08
The payer must be informed about an error resulting from reading a QR Code with a non-existent or blocked key. Mandatory message: It must indicate that the transaction was not performed and that there was a technical or communication problem. Examples:
Transaction not completed. Communication failure. Try again;
Your Pix was not finalized. We had a technical problem. Try again;
Sorry, we had a communication problem. Try again.
Mandatory

37
Version 7.3 Immediate payment or payment with maturity via Dynamic QR Code RECIPIENT: PSP of the payer user 9:30 Receiver / Value Cancel Continue Balance: R$ 1,000.00 R$ 824.00 Final Value Interest: 1% Interest/Period: Per month Fine: 2% Fine/Period: After 15/02/2021 Lot number: 123456 Discount: 10% until 10/02/2021 ADDITIONAL INFORMATION CPF/CNPJ: * .222.333 - Name: Roberdo da Silva DEBTOR INFORMATION Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Original Value: R$ 800.00 GENERAL INFORMATION Interest: R$ 8.00 Fine: R$ 16.00 PAYMENT WITH MATURITY Today At maturity Schedule Intended Payment Date:
Maturity Date: 15/02/2021
Payment with maturity
I understand
Transaction not completed.
Receiver account non-existent.
9:30
Receiver / Value
Cancel Continue
Balance: R$ 1,000.00
R$ 824.00
Final Value
Interest: 1%
Interest/Period: Per month
Fine: 2%
Fine/Period: After 15/02/2021
Lot number: 123456
Discount: 10% until 10/02/2021
ADDITIONAL INFORMATION
CPF/CNPJ: * .222.333 -
Name: Roberdo da Silva
DEBTOR INFORMATION
Name: Nadir da Silva
CPF/CNPJ: * .993.555 -
PSP: PSP XYZ
RECIPIENT INFORMATION
Original Value: R$ 800.00
GENERAL INFORMATION
Interest: R$ 8.00
Fine: R$ 16.00
PAYMENT WITH MATURITY
Today At maturity Schedule
Intended Payment Date:
Maturity Date: 15/02/2021
Payment with maturity
I understand
Transaction not completed. Expired QR Code.
This QR Code does not accept payment after expiration. 11 12 12 Error messages during settlement must be specific and clear to the user, in order to indicate the effective reason for the non-processing of the transaction. Mandatory messages: They must indicate that the transaction was not performed and specify the problem occurring in cases of insufficient balance, unavailable receiver account, non-existent receiver account, processing error, or technical failure, time exceeded. In the event of settlement errors associated with processing, participant unavailability, or time limit exceeded, it must be clear to the user that the error stems from the PSP itself. Examples:

Try another value, insufficient balance;
Pix not performed, the balance you have was not sufficient;
You do not have a balance to finalize this Pix;
Transaction not completed. Receiver account unavailable;
Pix not completed. The account of the person you want to transfer to is not available;
Error. Receiver account unavailable;
Transaction not completed. Receiver account non-existent;
Pix not completed. The account of the person you want to transfer to does not exist;
Error. Receiver account non-existent;
Transaction not completed. Processing error. We had a failure processing your Pix. Try again;
Sorry, we had a technical failure. Try again.
11
If the document does not accept payment after maturity, attempts to send an order outside this period must be refused, and the user must be informed about this condition. The message must indicate that the transaction was not completed and specify the error. Examples:
Transaction not completed. Expired QR Code. This QR Code does not accept payment after expiration. Pix not performed. Expired QR Code.
Mandatory

38
Version 7.3 Immediate payment or payment with maturity via Dynamic QR Code RECIPIENT: PSP of the payer user and PSP of the receiver user 9:30 Receipt Share Save on mobile Statement / Refund Balance: R$ 1,000.00 Interest: 1% Interest/Period: Per month Fine: 2% Fine/Period: After 15/02/2021 Lot number: 123456 Discount: 10% until 10/02/2021 ADDITIONAL INFORMATION Name: Fernanda Costa CPF/CNPJ: * .777.888 - PSP: PSP ABCD PAYER INFORMATION CPF/CNPJ: * .222.333 - Name: Roberdo da Silva DEBTOR INFORMATION Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Original Value: R$ 800.00 Transaction ID: 885544756782258 Interest: R$ 8.00 Fine: R$ 16.00 Final Value: R$ 824.00 Date/Time: 16/02/2020 at 19:35:05 Identifier: BBQ PIX CONFIRMED Payment with maturity 9:30 Receipt Balance: R$ 1,000.00 Share Save on mobile Statement / Refund Name: Fernanda Costa CPF/CNPJ: * .777.888 - PAYER INFORMATION PSP: PSP ABCD Name: Roberto da Silva DEBTOR INFORMATION CPF/CNPJ: * .222.333 - Name: Nadir da Silva CPF/CNPJ: * .993.555 - PSP: PSP XYZ RECIPIENT INFORMATION Transaction ID: 885544775112258 Value: R$ 800.00 Date/Time: 21/01/2020 at 19:34:05 Identifier: BBQ PIX CONFIRMED Immediate payment 16 16 14 14 16 If provided, debtor data (name and CPF - masked or not - or CNPJ) may be included in the payment receipt for payer and receiver users. 15 The PSP cannot save the Pix key nor should it provide an option to save the Pix key linked to the Dynamic QR Code payment. 14 Make a payment receipt available to payer and receiver users, during the period established in the current regulation, containing, at minimum:

Name, CPF (masked or not)/CNPJ and name of the PSP of the payer user;
Name, CPF (masked or not)/CNPJ and name of the PSP of the receiver user;
Message from the "Identifier" field (TxId);
Value and Transaction ID,
Date and time/minute/second (Brasília time) of settlement.
Other necessary information from the Dynamic QR Code payload must also be presented, according to the type of payment. When the transaction involves a PSI, the name of the PSI must appear on the receipt. The display of the Pix key linked to the Dynamic QR Code and the banking data (branch and account) of the receiver on the payment receipt is prohibited. The screen on the side presents an illustrative example of a payment receipt made via Dynamic QR Code.
The Transaction ID refers to the "EndtoEndID" present in pacs.008.
13
The payer user must receive a notification as soon as the transaction is completed, including for scheduled payment with maturity. The method of sending the notification is at the free choice of the PSP. The notification must contain, at minimum, the following information:
Receiver name and transaction value.
Recommended
Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
08
Statement of payments, receipts, and refunds made in Pix, in which users obtain access to information related to each transaction performed. Statement

40
Version 7.3 Excerpt
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Pix Statement / Receipt
Balance: R$ 1,000.00
Share Return Save on cell phone
PSP: PSP ABCD
CPF/CNPJ: * .777.888 -*
ID/Transaction: 885544774112258
Debited amount: R$ 10.00
Date/Time: 06/06/2021 at 21:34:05
Fernanda Costa
Receipt - Pix via Key
POSTING
9:30
Pix Statement / Receipt
Balance: R$ 1,000.00
Share Save on cell phone
PSP: PSP ABCD
CPF/CNPJ: * .777.888 -*
ID/Transaction: 885544774112269
Debited amount: R$ 100.00
Date/Time: 15/05/2021 at 21:34:05
João da Silva
Payment - Pix via Key
POSTING
9:30
Pix Statement / All
Balance: R$ 1,000.00
Receipts with or without return
Pix via
QR Code
Pix via
Key or Manual
All
Search
Receipt - Pix via QR Code
Date/Time: 01/05/2021 at 17:16:45
Roberto da Silva
Received amount: R$ 5.00 (updated)
Return
Amount: R$ 40.00
Date/Time: 10/05/2021 at 10:31:42
Energia S/A
Automatic Pix
Debited amount: R$ 100.00
Date/Time: 15/05/2021 at 21:34:05
João da Silva
Pix via Key
LAST POSTINGS
9:30
Statement
Balance: R$ 1,000.00
Credit Card Pix
Account current All
Search
Amount: R$ 100.00
Date: 27/06/2021
Fernanda Costa
Scheduled Pix
Scheduled amount: R$ 30.00
Date: 25/06/2021
ONG Animal Life
Scheduled Pix
FUTURE POSTINGS
Change amount: R$ 10.00
Purchase amount: R$ 40.00
Date/Time: 01/05/2021 at 11:24:02
Store GHJK
Pix Change
Debited amount: R$ 90.00
Date/Time: 14/05/2021 at 20:24:04
Sabrina Ferreira
Transfer via TED
Debited amount: R$ 100.00
Date/Time: 06/06/2021 at 21:34:05
DETRAN-DF
Tax payment
LAST POSTINGS
08
07
06
04
03
02
01
09
It is recommended that Pix transactions initiated by the PSI be identified in the PSP statement with reference to the participant that provided the initiation service. 08 Recovery of payment, receipt, and scheduling receipts available in the statement functionality. 07 Option to initiate return in the statement functionality. 06 Provide a specific statement containing only Pix transactions. Recommended 05 Returns related to Pix transactions disputed under the Special Return Mechanism (MED) must be identified as such in the account statement and, if provided, in the Pix statement, including the protocol number of the corresponding return request, when it exists. If the returned funds come from an account different from the receiving account of the root transaction, the sender's name must not be displayed in the statement. 04 Payments made by Automatic Pix must be identified as such in the account statement and, if provided, in the Pix statement. The immediate payment of authorization shifts 3 and 4 constitutes an exception to this rule, not being identified with the Automatic Pix nomenclature in the account statement or Pix statement, but rather as a Pix transaction. 03 Scheduled Pix transactions that have not yet been settled must be identified with this nomenclature in the account statement and, if provided, in the Pix statement, as future postings. Alternatively, the identification of Scheduled Pix can be done in a specific query menu for schedules. 02 The postings of Pix Change transactions in the transactional account statement and in the specific statement of Pix transactions, if provided, must display the purchase and change values separately. 01 Pix transactions (payments, receipts, withdrawals, including the amount of cash resources made available in a Pix Change, and returns) must be present in the transactional account statement, so that these transactions can be easily differentiated from transactions that are not Pix. Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
09
Functionality that allows Pix users to return, partially or fully, the value of a received transaction. Return

42
Version 7.3 Return
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Pix Statement / Return
Balance: R$ 1,000.00
Receipts with or without return
Pix via
QR Code
Pix via
Key or Manual
All
Search
Return
Received amount: R$ 5.00 (updated)
Date/Time: 01/05/2021 at 21:34:05
Roberto da Silva
Receipt - Pix via QR Code
Withdrawn amount: R$ 50.00
Date/Time: 01/05/2021 at 21:34:05
Store GHJK
Pix Withdrawal
Debited amount: R$ 100.00
Date/Time: 15/05/2021 at 21:34:05
Name: João da Silva
Pix via Key
LAST POSTINGS
9:30
Return
Balance: R$ 1,000.00
Cancel Continue
Description (optional)
Small description of the transaction
R$ 0.00
Amount to be returned (full or partial)
R$ 10.00
Original value
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: * .222.333 -*
ID/Transaction: 885544774112258
Date/Time: 06/06/2021 at 21:35:05
Name: Roberto da Silva
Receipt - Pix via Key
ORIGINAL RECEIPT INFORMATION
9:30
Pix Statement / Return
Balance: R$ 1,000.00
Share Return Save on cell phone
PSP: PSP ABCD
CPF/CNPJ: * .777.888 -*
ID/Transaction: 885544774112258
Received amount: R$ 10.00
Date/Time: 06/06/2021 at 21:34:05
Name: Fernanda Costa
Receipt - Pix via Key
POSTING
04
04
03
02
01
04
The return option may be presented in the query of the transactional account statement or in the query of the Pix statement, if this is provided. 03 The user must quickly identify the original posting to which the return refers. 02 To be able to select the return, the user must, at minimum, view the payer's name, the value of the original transaction, and the payment date of the original transaction. 01 There must be functionality for the user to return any receipt occurred in the last 90 days. Mandatory Recommended

43
Version 7.3 Return
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Pix Statement / Return
Balance: R$ 1,000.00
Share Return Save on cell phone
Description: Return of barbecue
Date/time: 25/01/2020 at 21:34:05
Returned amount: R$ 5.00
RETURN INFORMATION
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: * .222.333 -*
Original value: R$ 10.00
ID/Transaction: 885544774112258
ORIGINAL RECEIPT INFORMATION
Updated value: R$ 5.00
Date/Time: 06/06/2021 at 21:34:05
Name: Roberto da Silva
Receipt - Pix via Key
RETURN
9:30
Return
Balance: R$ 1,000.00
Cancel Continue
Description (optional)
Small description of the transaction
R$ 0.00
Amount to be returned (full or partial)
R$ 10.00
Original value
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: * .222.333 -*
ID/Transaction: 885544774112258
Date/Time: 06/06/2021 at 21:35:05
Name: Roberto da Silva
Receipt - Pix via Key
ORIGINAL RECEIPT INFORMATION
9:30
Receipt
Balance: R$ 1,000.00
Share Save on cell phone
Statement /
Return
ID/Transaction: 885544774112258
Receipt: via QR Code
Payer: Roberto da Silva
Identifier: Barbecue
PSP: PSP ABCD
CPF/CNPJ: * .222.333 -*
Original value: R$ 10.00
Date/time: 21/01/2020 at 10:22:02
ORIGINAL RECEIPT INFORMATION
Description: Return of barbecue
Returned amount: R$ 5.00
Updated value: R$ 5.00
Date/time: 25/01/2020 - 21:34:05
ID/Transaction: 54286327411258
PIX CONFIRMED
08
07
06
05
09
Before the option to confirm the return, the balance of the transactional account may be made available to the user. 08 The aggregated value of all returns made for a specific transaction must be easily consultable by the user. 07 Provide a receipt of the return, during the period established in regulation, containing, at minimum, the name and CPF (masked or not) / CNPJ of the recipient of the return, the name of the PSP of the recipient of the return, the date of the original transaction, the value of the original transaction, the date of the return, the value of the return, and the ID of the return and of the original transaction. The message and the minimum fields that must be presented to the user are represented in the screen next to it.

The ID/transaction refers to the "EndtoEndID" present in the original pacs.008;
The "Description" corresponds to the field "informacoesEntreUsuarios" of the pacs.004;
The "Description" field must not contain HTML tags. The application of the user sender of the return must display the characters of this field literally and, therefore, must not render links or any dynamic content. 06 The "Description" field, optional filling by the user, must be presented for filling.
In the formation of the pacs.004, the text of the "Description" field must be inserted in the field "informacoesEntreUsuarios".
05
The user must be offered the possibility to make partial returns of the received resources. Mandatory Recommended

44
Version 7.3 Return
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Camera Email PSP XYZ
20
Calendar
A precautionary block was made in your account, in the amount of R$ 10.00, referring to the Pix transaction made by Nadir da Silva, on 21/01/2020, at 21:34:05. This value may remain blocked for up to 72 hours. PSP XYZ - 15:00 Payee 9:30 Return Balance: R$ 0.00 Cancel Finish Receipt - Pix via Key ORIGINAL RECEIPT INFORMATION RETURN INFORMATION Name: Roberto da Silva R$ 5.00 Returned amount Date/Time: 21/01/2020 at 10:22:02 ID/Transaction: 885544774112258 CPF/CNPJ: * .222.333 -* PSP: PSP ABCD Identifier: Barbecue Original value: R$ 10.00 Description: Return of barbecue Understood Return not completed. Insufficient balance 9:30 Return Balance: R$ 1,000.00 Cancel Finish Receipt - Pix via Key ORIGINAL RECEIPT INFORMATION RETURN INFORMATION Name: Roberto da Silva R$ 5.00 Returned amount Date/Time: 21/01/2020 at 10:22:02 ID/Transaction: 885544774112258 CPF/CNPJ: * .222.333 -* PSP: PSP ABCD Identifier: Barbecue Original value: R$ 10.00 Description: Return of barbecue Understood Return not completed. Data incompatible with the original transaction 9:30 Pix Statement / Return Balance: R$ 1,000.00 Share Return Save on cell phone Receipt - Pix via Key Date/Time: 06/06/2021 at 21:34:05 Name: Fernanda Costa Received amount: R$ 10.00 Blocked transaction POSTING ID/Transaction: 885544774112258 CPF/CNPJ: * .777.888 -* PSP: PSP ABCD 12 11 11 10 12 The payee of the original transaction must be immediately notified about the precautionary block in their account. The notification must contain, at minimum, the following information:

Reason for the block;
Blocked amount;
Payer's user name;
Date/time/minute/second (Brasília time) of the original transaction;
Maximum block period (72 hours).
11
In case of precautionary block, the receiver's PSP must provide the possibility of total return of the resources by the receiving user, prohibiting partial return in this case. 10 Error messages in settlement must be specific and clear to the user, in order to highlight the effective reason for non-processing of the return transaction. Mandatory messages: Error messages in the return process must highlight that the transaction was not performed and specify the problem occurred at least in cases of data incompatible with the original transaction, period exceeding 90 days, and value higher than the transaction. Examples:
Return not completed. Data incompatible with the original transaction;
Error making the return, check if you entered the data correctly;
Error returning Pix, check if the data are correct;
Return not completed. The return is limited to transactions made in the last
90 days;
Error returning Pix because the 90-day deadline has passed;
Return not completed. Value of the return(s) higher than the original transaction;
Error returning Pix. Check the informed value;
Try another value, insufficient balance;
Return not completed. The balance you have is not sufficient;
You are out of balance to finalize this Pix.
Mandatory

45
Version 7.3 Return
RECIPIENT: Payer's PSP and Payee's PSP
9:30
PSP ABCD Email
The amount of R$ 10.00 was credited in your account, referring to the return of the Pix transaction received by Fernanda Costa, on 21/01/2020, at 21:34:05, in the amount of R$ 10.00. PSP ABCD - 15:00 Payer 9:30 Camera Email PSP XYZ 20 Calendar The return was made to Nadir da Silva of the amount of R$10.00, blocked on 23/01/2020, at 13:45:07, referring to the transaction made on 21/01/2020, at 21:34:05, in the amount of R$ 10.00. PSP XYZ - 15:00 Payee 9:30 Camera Email PSP XYZ 20 Calendar The amount of R$ 10.00 was made available in your account, blocked on 23/01/2020, at 13:45:07, referring to the Pix transaction made by Nadir da Silva, on 21/01/2020, at 21:34:05, in the amount of R$ 10.00. PSP XYZ - 15:00 Payee 15 14 13 15 The payer of the original transaction must be immediately notified about the credit in their account resulting from a return. The notification must contain, at minimum, the following information:

Credited amount;
Sender's name of the return;
Date/time/minute/second (Brasília time) of the original transaction;
Value of the original transaction.
14
The payee of the original transaction must be immediately notified, if the blocked resources have been effectively returned to the payer. The notification must contain, at minimum, the following information:
Returned amount;
Date/time/minute/second (Brasília time) of the block;
Recipient's name of the return;
Date/time/minute/second (Brasília time) of the original transaction;
Value of the original transaction.
13
The payee of the original transaction must be immediately notified upon the release, in their account, of resources until then blocked. The notification must contain, at minimum, the following information:
Amount made available;
Date/time/minute/second (Brasília time) of the block;
Payer's user name;
Date/time/minute/second (Brasília time) of the original transaction;
Value of the original transaction.
Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
10
Functionality that allows Pix users to register, delete, and portability of keys in Pix. My Keys

47
Version 7.3 My Keys
RECIPIENT: Payer's PSP and Payee's PSP
9:30
My Keys
Balance: R$ 1,000.00
Learn more about the
Keys
Register new Key
The registration of the key is necessary to receive a Pix in a practical way. It is possible to register four types of key:

your mobile phone number;
your CPF/CNPJ;
your email address.
Random Key
Register one through the button “Register new Key”.
No registered keys
REGISTERED KEYS
9:30
Key registration
Balance: R$ 1,000.00
Skip
Contacts
The registration of the key is necessary to receive a Pix in a practical way. With the key, instead of the payer having to type all the information to identify your account, it will be enough to inform the key registered which can be the cell phone number, CPF or email. 9:30 Key registration Balance: R$ 1,000.00 Skip Contacts Each key can only be linked to a single account. Each individual person can register up to 5 keys for the same account. 01 02 Obligatory present, whenever there is key registration, consent message that informs, at minimum, that payer users who have knowledge of the key will view the following data of the receiving user when sending them payments:
Full name;
CPF with mask (e.g.: .777.888-).
The name of the payment service provider to which the key is linked may be displayed, at the discretion of the payer's PSP. Furthermore, the consent message must inform that all other Pix users who have the information of the email or the mobile phone number of the user will be able to know that he registered this email and/or this mobile phone number as a Pix key. 01 It is mandatory that, upon first access to My Keys, the user is informed about the key, addressing, at minimum:
That the key identifies the receiver in a practical way and facilitates the payment or transfer experience;
Types (cell phone number, email, CPF/CNPJ, random key);
Restriction that each key can only be linked to a single account;
That up to 5 keys can be registered for the same account.
Mandatory

48
Version 7.3 My Keys
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Key registration
Balance: R$ 1,000.00
Cancel Continue
+55 (61) 98888 8888
CELL PHONE EMAIL
CPF/CNPJ KEY
RANDOM
Select the type of Key you want to register Register the cell phone number 9:30 Pix Receive Pix Pix with QR Code Pix Copy and Paste Pix with Key / Manual My Pix limits Pix Automatic Statement / Return My keys R$30.00 Value João da Silva R$10.00 Value Payment via Key Roberto da Silva LAST TRANSACTIONS Cell Phone CPF Key Random Email Balance:R$ 1,000.00 Nadir da Silva 9:30 My Keys Balance: R$ 1,000.00 ? Key - Cell phone Creation date: 19/01/2020 at 10:24:36 Key: +55 61 988888888 Key - CPF/CNPJ Creation date: 17/01/2020 at 10:26:36 Key: 111.993.222.44 Random key Creation date: 21/01/2020 at 21:34:36 Key: erewrwe3454354324324ds... REGISTERED KEYS Key Email Creation date: 20/01/2020 at 10:28:36 Key: nadir@email.com Learn more about the Keys Register new Key 07 06 04 03 07 The screens that will be built can exemplify the four experiences (registration, deletion, portability, and claim), for different types of key. 06 The My Keys functionality must be offered through quick and clear access for the user. The options for registration, deletion, and portability must be offered to the user. 05 There should be no temporal limits for the user to request the deletion of their keys. The effective execution of the deletion is carried out during the DICT operating hours. 04 The user must be able to include and exclude keys for the four possible types (cell phone number, email, CPF/CNPJ, and random key). 03 The keys registered in the transactional account must be available for management by the user. Mandatory Recommended

49
Version 7.3 My Keys
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Key registration
Balance:R$ 1,000.00
Cancel Continue
+55 (61) 98888 8888
Register the cell phone number
KEY
RANDOM CPF/CNPJ
CELL PHONE EMAIL
Select the type of Key you want to register Key linked to PSP ABCD. Do you want to start the portability process? To complete this process it is necessary that you confirm it in the other participant's application within 7 (seven) days. Cancel Confirm 9:30 Statements Investments Pix Transfer 2,010.00 Available balance R$ Cc: 8888- Ag: 4321 Hello, Fernanda! PSP ABCD 08 08 09 In the portability process, the PSP receiving the key can send messages to the user, guiding him to access the Pix environment of the other participant to confirm the portability request, within a period of up to 7 (seven) days. 08 Portability and possession claim process. Whenever the user tries to register a key that is already registered in the DICT, their PSP must ask if the user wants to start the portability process, if the key is linked to the user's own CPF, or possession claim, if the key is linked to another user's CPF. The mandatory message for portability must highlight that the key already has a link, to which PSP it is linked, ask for consent for portability, and inform the deadline or limit date. Examples:

Key linked to PSP XYZ. Do you want to start portability? To bring your key to
[name of PSP] you need to confirm in the application where this key is already registered until day [date] / Key associated with another account. Do you want to bring your key to [name of PSP]? This portability must be confirmed at the institution where the key is active within 7 days. The mandatory message for possession claim must highlight that the key is in use by another user, ask for consent for the claim, and inform the deadline or limit date;
Key registered by another user. Want to claim use? The deadline to finalize this
process is up to 30 days. / Would you like to ask for this key? It is in use by another person. This process, called claim, can be finalized until day [data]. Recommended Mandatory

50
Version 7.3 My Keys
RECIPIENT: Payer's PSP and Payee's PSP
9:30
Key registration
Balance:R$ 1,000.00
+55 (61) 98888 8888
Register the cell phone number
KEY
RANDOM CPF/CNPJ
CELL PHONE EMAIL
Select the type of Key you want to register We received a possession claim request for Pix key [insert key]. This means that another user registered a request for this key to be linked to another account. To cancel this process and for you to continue using this key, it is necessary that you perform a new validation of possession within 7 (seven) days. Cancel Confirm Donor PSP 9:30 Key registration Balance:R$ 1,000.00 +55 (61) 98888 8888 Register the cell phone number KEY RANDOM CPF/CNPJ CELL PHONE EMAIL Select the type of Key you want to register We received the portability request for Pix key [Insert key]. This means that PSP ZYX registered a request in your name for this key to be linked to another account. To complete this process it is necessary your confirmation within 7 (seven) days. Do you confirm the portability request? Cancel Confirm Donor PSP 11 10 11 The donor PSP must immediately communicate the user, clearly, about the start of the possession claim process. In the mandatory message to inform that a possession claim request was requested, it must state what the key is and the deadline or limit date for revalidation of the key. Examples:

We received a possession claim request for Pix key [key]. This means that
another user registered a request for this key to be linked to another account. To cancel this process and for you to continue using this key, it is necessary that you perform a new validation within 7 days. / Another person asked for the key [insert key]. The use of this key was claimed by another user. If you want to continue using this key you need to do a new validation until day [date]. 10 The donor PSP must immediately communicate the start of the portability process to the user, upon access to the Pix environment. The mandatory message must be sent, at least once, to communicate that a portability request was requested, and must inform what the key is and the deadline or limit date for confirmation, as well as have the option to confirm or cancel portability. It is at the discretion of the donor PSP to send the mandatory message more than once during the period for confirmation or cancellation of portability. Examples:
We received your portability request for key [key]. If you really want
to change you have until day [date] to confirm, but we hope you stay with us!
We received portability request for Pix key [insert key]. This means that the
PSP ZYX registered a request in your name for this key to be linked to another account. To complete this process, your confirmation is necessary within 7 days. Mandatory

51
Version 7.3 My Keys
RECIPIENT: Payer user's PSP and Payee user's PSP 9:30 My Keys Balance: R$ 1,000.00 ? Random Key Creation date: 01/21/2020 at 21:34:36 Key: erewrwe3454354324324ds... Email Key Creation date: 01/20/2020 at 10:28:36 Key: nadir@email.com Cell Phone Key Creation date: 01/19/2020 at 10:24:36 Key: +55 61 988888888 CPF/CNPJ Key Creation date: 01/17/2020 at 10:26:36 Key: 111.993.222.44 REGISTERED KEYS Learn more about the Keys Register new Key I understand Pix Key erewrwe3454354324324ds... registered successfully! Now, Pix users can make payments to you by providing this key, without the need to type your data. 12 12 The user must be notified by the PSP about the completion (both in case of success and failure) of the registration, deletion, alteration, portability, and claim of ownership processes. Success messages must specify at least which operation was performed and that it was successful. Attention: the key registration success message must not imply that this key is necessary to pay with Pix, since the key is only used for receiving. Failure messages must specify at least which operation could not be performed and the reason for failure. Examples:

Key registered/changed/edited/deleted successfully!
Ready, your key is already registered!
Registration successful! You can now receive Pix in a very easy way, just
provide your key [key].
Error registering your key. Ownership confirmation is missing. Try again.
Unable to register your key as we did not identify the ownership confirmation.
The key [key] is now yours! The claim of ownership was completed successfully.
Ready! Portability completed. You can now use the key [key].
Claim of ownership for key [key] refused. The person who registered this
key confirmed that they still use it.
Request to move the key to PSP ZYX refused. The portability was not completed,
as we did not identify the confirmation at the origin institution. Mandatory

52
Version 7.3 My Keys
RECIPIENT: Payer user's PSP and Payee user's PSP 9:30 Key registration Balance: R$ 1,000.00 +55 (61) 98888 8888 Register the cell phone number KEY RANDOM CPF/CNPJ CELL PHONE EMAIL Select the type of Key you want to register I understand Transaction not completed. Communication failure. Try again 13 14 If the user attempts to register, delete, alter, port, or claim ownership of keys during a time when the participant does not make these functionalities available, the user must be informed about the expected timeframe for completion or the time when the functionality will be available to the user. Examples:

Key registration pending. Its completion will occur tomorrow, by 8 AM (if the
attempt was made before midnight);
Key deletion pending. Its completion will occur today, by 8 AM (if the attempt
was made after midnight);
Operation available from 8 AM to 8 PM. Please try at another time.
13
In case of communication failure with the DICT, the user must be informed of this situation through a clear message. Mandatory message: It must highlight that the operation was not performed and that there was a technical or communication problem. Examples:
The operation was not completed. Communication failure. Try again;
The operation was not finalized. We had a technical problem. Try again;
Sorry, we had a communication problem. Try again.
Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
11
Functionality that allows Pix users to consult and manage Pix limits, including for Pix Withdrawal/Pix Change, Scheduled Pix, and Automatic Pix, and to register accounts or beneficiaries with differentiated limits. My Pix Limits

54
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
My Pix Limits
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Schedule Management
Beneficiary Registration
Account Registration
Automatic Pix
Scheduled Pix
Pix Withdrawal and Pix Change
Pix for businesses
Pix for individuals
MY PIX LIMITS
I understand
You can define the total value in

Pix transactions in each period
(daytime and nighttime).
9:30
My Pix Limits
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Schedule Management
Beneficiary Registration
Account Registration
Automatic Pix
Scheduled Pix
Pix Withdrawal and Pix Change
Pix for businesses
Pix for individuals
MY PIX LIMITS
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell Phone
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
My
Pix Limits
Pix
Automatic
Statement /
Return
My keys
02
01
02
Information must be provided for each item of the "My Pix Limits" menu, addressing, at a minimum, the following points:

Pix for individuals
The user can define the limit for the total value of Pix transactions for individuals
(accounts associated with CPF), per period (daytime and nighttime).
Pix for businesses
The user can define the daily limit for the total value of Pix transactions for businesses
(accounts associated with CNPJ).
Pix Withdrawal and Pix Change
The user can define, for each period (daytime and nighttime), the limit for the total value of
Pix Withdrawal and Pix Change transactions;
It must be evident that the limits for the value of Pix Withdrawal and Pix Change transactions are
defined independently of the other limits;
The change limit refers only to the portion of the transaction related to cash withdrawal;
The limits cannot be higher than the values determined by the Central Bank: R$
3,000.00 (daytime period) and R$ 1,000.00 (nighttime period).
Scheduled Pix
The user can define the daily limit for the total value of Scheduled Pix transactions;
It must be evident that the limit for the value of Scheduled Pix transactions is defined in
a manner independent of the other limits.
Automatic Pix
The user can define the daily limit for the total value of Automatic Pix transactions for
businesses (accounts associated with CNPJ);
It must be evident that the limit for the value of Automatic Pix transactions is defined in
a manner independent of the other limits.
Account Registration (if this functionality is made available)
The user can register beneficiary accounts with differentiated daily limits and
manage the value of each of these limits;
The user can register beneficiary accounts that will have a differentiated global daily
limit and manage the value of this limit.
Beneficiary Registration (if this functionality is made available)
The user can register beneficiaries with differentiated daily limits and manage the
values of each of these limits;
The user can register beneficiaries that will have a differentiated global daily limit and
manage the value of this limit.
01
In the Pix environment, the "My Pix Limits" menu must be made available, with functionalities that allow the user to consult and manage transaction value limits for Pix, including Pix Withdrawal/Pix Change, Scheduled Pix, and Automatic Pix, and by type of beneficiary (individual and legal entity). It is at the discretion of the PSP to make available the functionalities for registering specific limits for accounts and for registering specific limits for beneficiaries, observing that at least one of them must be made available. Mandatory

55
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Pix for individuals
Balance: R$ 1,000.00
Cancel Finish
8:00 PM to 6:00 AM
If you want higher limits, click on "Request higher limits".
Period limit:
Nighttime period:
R$ 500.00
R$ 0.00 R$1,000.00
R$ 0.00 R$4,000.00
Period limit: R$ 3,000.00
Daytime period:
ALTER LIMITS
6:00 AM to 8:00 PM
R$ 500.00
R$ 3,000.00
Request higher limits
9:30
Pix for individuals
Balance: R$ 1,000.00
Alter
Limits
Period limit: R$ 500.00
8:00 PM to 6:00 AM
Nighttime period
Period limit: R$ 3,000.00
6:00 AM to 8:00 PM
Daytime period
PIX FOR INDIVIDUALS
9:30
My Pix Limits
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Schedule Management
Beneficiary Registration
Account Registration
Automatic Pix
Scheduled Pix
Pix Withdrawal and Pix Change
Pix for businesses
Pix for individuals
MY PIX LIMITS
04
03
03
04
The limit management functionality for individuals, for businesses, for Scheduled Pix, and for Automatic Pix must allow the user to request higher limits than those made available for alteration (i.e., beyond the parameters defined by the Central Bank), leaving it at the discretion of the payer PSP to attend to these requests. 03 The limit management functionality must allow the user to consult and alter the values of Pix transaction limits, including Pix Withdrawal/Pix Change, Scheduled Pix, and Automatic Pix. Mandatory

56
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Pix for individuals
Balance: R$ 1,000.00
Alter
Limits
Period limit: R$ 500.00
8:00 PM to 6:00 AM
Nighttime period
Period limit: R$ 3,000.00
6:00 AM to 8:00 PM
Daytime period
PIX FOR INDIVIDUALS
I understand
Your request will be analyzed and, if approved, your new limit will be available between 24 and 48 hours. 9:30 Pix for individuals Balance: R$ 1,000.00 Cancel Finish 8:00 PM to 6:00 AM If you want higher limits, click on "Request higher limits". Period limit:
Nighttime period:
R$ 500.00
R$ 0.00 R$1,000.00
R$ 0.00 R$4,000.00
Period limit: R$ 3,000.00
Daytime period:
ALTER LIMITS
6:00 AM to 8:00 PM
R$ 500.00
R$ 3,000.00
Request higher limits
9:30
Pix for individuals
Balance: R$ 1,000.00
Cancel Finish
R$ 5,000.00
?
?
8:00 PM to 6:00 AM
Period limit:
Nighttime period
6:00 AM to 8:00 PM
Period limit:
Daytime period
REQUEST HIGHER LIMITS
05
05
In all requests for limit increase, except in the case of Automatic Pix, the user must be informed that the alteration will be processed between 24 and 48 hours and, if the requested limit is higher than the value of the parameter defined by the BC, the user must be informed that the increase is subject to approval by the payer PSP. 06 In the request for limit increase for Automatic Pix, the user must be informed that the alteration will be processed within 8 hours and, if the requested limit is higher than the value of the parameter defined by the BC, the user must be informed that the increase is subject to approval by the payer PSP. Mandatory

57
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Pix for individuals
Balance: R$ 1,000.00
Alter
Limits
Period limit: R$ 500.00
8:00 PM to 6:00 AM
Nighttime period
Period limit: R$ 2,000.00
6:00 AM to 8:00 PM
Daytime period
PIX FOR INDIVIDUALS
I understand
The limit reduction was completed successfully!
9:30
Pix for individuals
Balance: R$ 1,000.00
Alter
Limits
Period limit: R$ 500.00
8:00 PM to 6:00 AM
Nighttime period
Period limit: R$ 3,000.00
6:00 AM to 8:00 PM
Daytime period
PIX FOR INDIVIDUALS
9:30
Pix for individuals
Balance: R$ 1,000.00
Cancel Finish
8:00 PM to 6:00 AM
If you want higher limits, click on "Request higher limits".
Period limit:
Nighttime period:
R$ 500.00
R$ 0.00 R$1,000.00
R$ 0.00 R$4,000.00
Period limit: R$ 3,000.00
Daytime period:
ALTER LIMITS
6:00 AM to 8:00 PM
R$ 500.00
R$ 2,000.00
Request higher limits
9:30
Scheduled Pix
Balance: R$ 1,000.00
Cancel Finish
If you want higher limits, click on "Request higher limits".
R$ 0.00 R$4,000.00
Daily limit: R$ 3,000.00
ALTER LIMIT
R$ 2,000.00
Request higher limits
Cancel I understand Confirm
There are scheduled payments with values higher than the established limit. Reducing the limit may prevent the execution of these payments on the scheduled date. Are you sure you want to confirm the reduction? 07 08 07 If the user requests a limit reduction, the PSP must immediately inform that the reduction was completed successfully. 08 The user must be informed if scheduled Pix limit reduction requests result in the impossibility of settling already scheduled appointments. In these situations, before completing the limit reduction, the PSP must present a message reporting the problem and ask the user if they really want to complete the request. Mandatory

58
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Pix Withdrawal Pix Change
Balance: R$ 1,000.00
Alter
Limits
The value limits for the total of Pix
Withdrawal and Pix Change transactions per period are defined in a manner independent of the other limits". Period limit: R$ 500.00 8:00 PM to 6:00 AM Nighttime period Period limit: R$ 2,000.00 6:00 AM to 8:00 PM Daytime period PIX WITHDRAWAL PIX CHANGE I understand Your request was completed and the alteration will be effectuated between 24 and 48 hours. 9:30 Pix Withdrawal Pix Change Balance: R$ 1,000.00 Alter Limits The value limits for the total of Pix Withdrawal and Pix Change transactions per period are defined in a manner independent of the other limits. Period limit: R$ 500.00 8:00 PM to 6:00 AM Nighttime period Period limit: R$ 2,000.00 6:00 AM to 8:00 PM Daytime period PIX WITHDRAWAL PIX CHANGE 9:30 Pix Withdrawal Pix Change Balance: R$ 1,000.00 Cancel Finish 8:00 PM to 6:00 AM Period limit:
Nighttime period:
R$ 500.00
R$ 0.00 R$1,000.00
R$ 0.00 R$3,000.00
Period limit: R$ 2,000.00
Daytime period:
ALTER LIMITS
06
00 AM to 8:00 PM
R$ 500.00
09 R$ 2,500.00
09
The Pix Withdrawal and Pix Change limits cannot be higher than those determined by the Central Bank of up to R$ 3,000.00 for the daytime period and up to R$ 1,000.00 for the nighttime period. Mandatory

59
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Account Registration
Balance: R$ 1,000.00
Register new account
Registration date: 12/05/2021 at 12:01:45
Key: 61 98888-5555
Account holder: Fernanda Costa
REGISTERED ACCOUNT
Daily limit: R$ 5,000.00
I understand
Your request was completed. The timeframe for account registration completion is 24 to 48 hours. 9:30 Account Registration Balance: R$ 1,000.00 Register new account Registration date: 10/01/2021 at 21:34:36 Key: 61 99222-2222 Account holder: João da Silva Daily limit: R$ 2,000.00 REGISTERED ACCOUNTS Registration date: 05/01/2021 at 11:15:40 Key: 62 98211-3333 Account holder: Maria Pereira Daily limit: R$ 5,000.00 9:30 Register new account Balance: R$ 1,000.00 Cancel Finish +55 (61) 98888 5555 Random Key Cell Phone CPF Email Select the type of key Account information Daily limit:
Account holder: Fernanda Costa
ACCOUNT DATA
KEY
Register using the Key or account data
R$ 0.00 R$10,000.00
R$ 5,000.00
9:30
My Pix Limits
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Schedule Management
Beneficiary Registration
Account Registration
Automatic Pix
Scheduled Pix
Pix Withdrawal and Pix Change
Pix for businesses
Pix for individuals
MY PIX LIMITS
11
12
10
10
12
When requesting the registration of a new account, the user must be informed that the registration process will be completed within 24 to 48 hours. 11 The account registration functionality must allow easy alteration of the registered limits and deletion of accounts. 10 If made available, the account registration functionality must allow the user to register beneficiary accounts, of the same ownership or different ownership, with differentiated daily limits for each account, through a Pix key or account data. At the discretion of the PSP, a differentiated daily limit applicable to all registered accounts may be used. Mandatory

60
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Beneficiary Registration
Balance: R$ 1,000.00
Register new beneficiary
CPF: 111.111.111-22
Beneficiary name: Maria da Silva
NEW BENEFICIARY
I understand
Your request was completed. The timeframe for beneficiary registration completion is 24 to 48 hours. 9:30 Beneficiary Registration Balance: R$ 1,000.00 Register new beneficiary Daily limit: R$ 5,000.00 Each beneficiary can receive up to this value per day BENEFICIARY LIMITS CPF: 123.456.789-00 Beneficiary name: José Pereira CPF: 987.654.321-00 Beneficiary name: Carlos Silva REGISTERED BENEFICIARIES 9:30 Register new beneficiary Balance: R$ 1,000.00 Cancel Finish Maria da Silva 111.111.111-22 Beneficiary name:
CPF:
NEW BENEFICIARY
9:30
My Pix Limits
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Schedule Management
Beneficiary Registration
Account Registration
Automatic Pix
Scheduled Pix
Pix Withdrawal and Pix Change
Pix for businesses
Pix for individuals
MY PIX LIMITS
15
13
14
14
13
15
When requesting the registration of a new beneficiary, the user must be informed that the registration process will be completed within 24 to 48 hours. 14 The beneficiary registration functionality must allow easy alteration of the registered limits and deletion of beneficiaries. 13 If made available, the beneficiary registration functionality must allow the user to register beneficiaries with differentiated daily limits. At the discretion of the PSP, a differentiated daily limit applicable to all registered beneficiaries may be used. Mandatory

61
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Register new beneficiary
Balance: R$ 1,000.00
Cancel Finish
Fernanda Costa
888.777.666-22
Daily limit:
Beneficiary name:
CPF:
R$ 0.00 R$20,000.00
NEW BENEFICIARY
R$ 4,000.00
I understand
The indicated limit is lower than the limit already registered for account of this beneficiary. Indicate a higher value or reduce the limit registered in the account of this beneficiary 9:30 Register new account Balance: R$ 1,000.00 Cancel Finish Cell Phone CPF Random Key Email Select the type of key R$ 0.00 R$10,000.00 ACCOUNT DATA KEY +55 (61) 98888 5555 Account information Daily limit:
Account holder: Fernanda Costa
Register using the Key or account data
I understand
The indicated limit is higher than the limit already registered for the beneficiary who is the holder of this account. Indicate a lower value or increase the limit registered for this beneficiary. R$ 5,000.00 16 If the PSP makes available both functionalities for registering specific limits (accounts and beneficiaries), the user must be informed about the impossibilities of registering limits, by account or by beneficiary, if there is incompatibility with pre-registered limits. Examples:

If the limit indicated for a beneficiary's account is higher than the limit already registered
for the beneficiary: "The indicated limit is higher than the limit already registered for the beneficiary who is the holder of this account. Indicate a lower value or increase the limit registered for this beneficiary".
If the limit indicated for a beneficiary is lower than the limit already registered for the account
of that beneficiary: "The indicated limit is lower than the limit already registered for the account of this beneficiary. Indicate a higher value or reduce the limit registered in the account." Mandatory

62
Version 7.3 My Pix Limits
RECIPIENT: Payer user's PSP
9:30
Schedule Management
Balance: R$ 1,000.00
Cancel Finish
Nighttime period: from 10:00 PM to 6:00 AM
Daytime period: from 6:00 AM to 10:00 PM
You are choosing:
From 10:00 PM to 6:00 AM
From 8:00 PM to 6:00 AM
Choose the nighttime period you prefer to make transactions with reduced values.
SCHEDULE MANAGEMENT
9:30
My Pix Limits
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Schedule Management
Beneficiary Registration
Account Registration
Automatic Pix
Scheduled Pix
Pix Withdrawal and Pix Change
Pix for businesses
Pix for individuals
MY PIX LIMITS
17
The limit management functionality may allow the alteration of the start of the nighttime hour to 8:00 PM or 10:00 PM. 18 When requesting an alteration of the start of the nighttime hour, the user must be informed that the alteration will be completed within 24 to 48 hours. Recommended Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
12
Functionality that allows single scheduling and recurring scheduling of Pix transactions. Scheduled Pix

64
Version 7.3 Scheduled Pix
RECIPIENT: PSP of the payer user
9:30
Scheduling Confirmation
Balance: R$ 1,000.00
Payment Date: 02/21/2024
R$ 100.00
Final Value
Description: service provision
CPF/CNPJ: *.777.888 -
Key: 61 99999 9999
Name: Fernanda Costa
RECIPIENT INFORMATION
Cancel Finish
9:30
Recipient / Value
Balance: R$ 1,000.00
Continue Enter agency and account
Key random Cell CPF Email
Select the type of key ?
Value
R$ 100.00
Description (optional)
Small transaction description
0 of 140 characters
+55 (61) 99999 9999
Recipient information
Name: Fernanda Costa
CPF/CNPJ: .777.888 - *
Date now, 11/17/2023
Repeat this Pix
Confirm
Sun Mon Tue Wed Thu Fri Sat
18
Sun
19 20 21 22 23 24 25
Sat
17
February 2024
Date
SCHEDULING
9:30
Recipient / Value
Balance: R$ 1,000.00
Continue Enter agency and account
Key random Cell CPF Email
Select the type of key ?
Value
R$ 100.00
Description (optional)
Small transaction description
0 of 140 characters
+55 (61) 99999 9999
Recipient information
Name: Fernanda Costa
CPF/CNPJ: .777.888 - *
Date now, 01/17/2024
Repeat this Pix
Initiation with Pix key
9:30
Scheduling Receipt
Balance: R$ 1,000.00
Share Save on cell
Statement /
Return
Name: Nadir da Silva
CPF/CNPJ: *** .993.555 -
PAYER INFORMATION
Name: Fernanda Costa
CPF/CNPJ: *.777.888 -
RECIPIENT INFORMATION
Payment Date: 02/21/2024
Value: R$ 100.00
Description: service provision
Scheduling made on: 01/17/2024
PIX SCHEDULING
IMPORTANT: the scheduling can be cancelled until 23:59 on the day before the scheduled date and its execution will depend on balance availability and daily Scheduled Pix limit on the payment date. 05 03 02 01 01 "Schedule" option available before finalizing the transaction. 05 On the scheduling receipt, the PSP may inform that the completion of the transaction depends on account balance and daily Scheduled Pix limit available on the date scheduled for payment. 04 For one-time schedulings made via dynamic QR code with due date, the PSP must provide a scheduling receipt to the payer user containing, at minimum, the scheduled payment date, the value, the date on which the scheduling was made, the name and CPF (masked or not)/CNPJ of the payer and payee users, the "Identifier" field message (TxId), as well as the necessary information from the dynamic QR Code payload.

When the transaction involves a PSI, the PSI name must appear on the receipt.
03
For one-time schedulings made via Pix key or manual insertion of transaction account data, the PSP must provide a scheduling receipt to the payer user containing, at minimum, the scheduled payment date, the value, the date on which the scheduling was made, as well as the name and CPF (masked or not)/CNPJ information of the payer and payee users and the "Description" field (whenever it is filled).
The "Description" field refers to "informacoesEntreUsuarios" of pacs.008;
The "Description" field must not contain HTML tags. The payer user's application must
display the characters of this field literally, and therefore must not render links or any dynamic content;
When the transaction involves a PSI, the PSI name must appear on the receipt.
02
Before the confirmation of the one-time scheduling, data for verification, according to the type of transaction initiation chosen, must be displayed to the payer user. The specifications of this data are available in the chapters "Pix with Pix key", "Pix with manual insertion of transaction account data" and "Immediate payment or with due date via dynamic QR Code". For initiation by key and account data, the scheduled payment date must also be presented. 01 The option to schedule Pix transactions must be made available to the payer user, including for non-business days. Recommended Mandatory

65
Version 7.3 Scheduled Pix
RECIPIENT: PSP of the payer user
9:30
Scheduling Receipt
Balance: R$ 1,000.00
Share Save on cell
Statement /
Return
PIX SCHEDULING
Name: Nadir da Silva
CPF/CNPJ: *** .993.555 -**
PAYER INFORMATION
Name: Fernanda Costa
CPF/CNPJ: *.777.888 -
RECIPIENT INFORMATION
Value: R$ 100.00
Scheduling made on: 01/17/2024
IMPORTANT: the scheduling can be cancelled until 23:59 on the day before the scheduled date and its effective execution will depend on balance availability and daily Scheduled Pix limit on the payment date. First Pix: 02/21/2024 Next payments: monthly, every day 21 Number of payments: 10 Last Pix: 11/21/2024 9:30 Recipient / Value Balance: R$ 1,000.00 Cancel Continue Select the type of key Recipient information Name: Fernanda Costa CPF/CNPJ: *.777.888 - * +55 (61) 99999 9999 Value R$ 100.00 Date ? CPF Email Key random Cell Define the repetitions Continue Total number of payments 10 REPEAT THIS PIX:
REPETITIONS
Custom
Every week
Every month
9:30
Recipient / Value
Balance: R$ 1,000.00
Small transaction description
0 of 140 characters
Cancel Continue
Select the type of key
Recipient information
Name: Fernanda Costa
CPF/CNPJ: *.777.888 - *
+55 (61) 99999 9999
Value
R$ 100.00
Date
21/02/2024
Description (optional)
Repeat Pix
?
CPF Email Key random Cell
9:30
Recipient / Value
Balance: R$ 1,000.00
Continue Enter agency and account
Key random Cell CPF Email
Select the type of key ?
Value
R$ 100.00
Description (optional)
Small transaction description
0 of 140 characters
+55 (61) 99999 9999
Recipient information
Name: Fernanda Costa
CPF/CNPJ: *.777.888 - *
Date
21/02/2024
Repeat this Pix
9:30
Scheduling Confirmation
Balance: R$ 1,000.00
Cancel Finish
RECIPIENT INFORMATION
Final Value
R$ 100.00
Name: Fernanda Costa
Key: 61 99999 9999
CPF/CNPJ: *.777.888 - *
Description: service provision
First Pix: 02/21/2024
Next payments: monthly, every day 21
Number of payments: 10
Last Pix: 11/21/2024
10
09
10
08
06
06
11
The PSP may offer the payer user functionality that allows customization of the recurring scheduling for periodicities additional to those made available mandatory. The PSP may also offer, at its discretion, the choice of recurrence for an indefinite period. 10 The one-time or recurring scheduling receipt must contain the term "Pix Scheduling" and a "calendar clock" type icon prominently at the top of the document, in order to distinguish it expressly from the payment receipt. It must also present clear and prominent information that the scheduling can be cancelled, as well as the deadline for cancellation. 09 For recurring schedulings made via Pix key or manual insertion of transaction account data, the PSP must provide a scheduling receipt to the payer user containing, at minimum, the date on which the scheduling was made, the value, the date of the first Pix, the recurrence frequency, the number of payments, if informed, and the date of the last Pix (if existing), as well as the name and CPF (masked or not)/CNPJ information of the payer and payee users and the field "Description" (whenever it is filled).

The "Description" field refers to "informacoesEntreUsuarios" of pacs.008;
The "Description" field must not contain HTML tags. The payer user's application must
display the characters of this field literally, and therefore must not render links or any dynamic content;
When the transaction involves a PSI, the PSI name must appear on the receipt.
08
Before the confirmation of the recurring scheduling, data for verification, according to the type of transaction initiation chosen, must be displayed to the payer user. The specifications of this data are available in the chapters "Pix with Pix key" and "Pix with manual insertion of transaction account data". The date of the first Pix, the recurrence frequency, the number of payments (if informed) and the date of the last Pix (if existing) must also be displayed. 07 In the configuration of the recurring scheduling, the PSP must offer the user at least one of the following options: number of desired payments and end date of the transactions. 06 The option for recurring scheduling of Pix transactions must be made available to the payer user, allowing, at minimum, weekly and monthly recurrence. Recommended Mandatory

66
Version 7.3 Scheduled Pix
RECIPIENT: PSP of the payer user
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
Dispute
Pix
MED
Pix
Scheduled
My
Pix limits
Pix
Automatic
9:30
Pix Statement / Scheduled Pix
Balance: R$ 1,000.00
Search
Scheduled
Value: R$ 100.00
Date: 01/17/2024
Fernanda Costa
Pix Scheduled
POSTINGS
Pix
Scheduled
Receipts with or without return
Pix via
QR Code
Pix via
Key or Manual Scheduled
Value: R$ 40.00
ONG Vida Animal
Pix Scheduled
Recurrence: monthly, until 05/25/2024
9:30
Receipt
Balance: R$ 1,000.00
Share Save on cell
Statement /
Return
Description: service provision
Value: R$ 100.00
Date/Time: 01/17/2024 - 21:34:05
ID/Transaction: 54286327411258
PIX CONFIRMED
Name: Nadir da Silva
CPF/CNPJ: *** .993.555 -**
PAYER INFORMATION
PSP: PSP XYZ
Name: Fernanda Costa
PSP: PSP ABCD
CPF/CNPJ: *.777.888 -
RECIPIENT INFORMATION
Next payments: monthly, every day 17
Number of payments: 10
Last Pix: 10/17/2024
9:30
Statement
Balance: R$ 1,000.00
Pix Credit Card
Account current All
Search
Scheduled Value: R$ 40.00
Date: 01/25/2024
ONG Vida Animal
Pix Scheduled
FUTURE POSTINGS
Debited Value: R$ 100.00
Date/Time: 01/19/2024 at 20:30:05
DETRAN-DF
Tax payment
Debited Value: R$ 100.00
Date/Time: 01/17/2024 at 21:34:05
Fernanda Costa
Pix
LAST POSTINGS
12 13
15
If the date of the first transaction is on days that do not exist in subsequent months days 29, 30 and/or 31), the PSP may offer the payer user the option to advance, in the months where applicable, the day of settlement of the recurring scheduling. 13 The payer user must be made available functionality to query scheduled transactions. The way in which the functionality will be made available is at the PSP's discretion. 12 In cases of recurring schedulings where the first Pix is an immediate transaction, the PSP must provide a payment receipt containing, at minimum, besides the information required according to the type of transaction initiation chosen, the following data:

Recurrence frequency;
Number of payments (if selected);
Date of the last Pix (if existing).
The information contained in the payment receipts for each type of initiation are available in the chapters "Pix with Pix key" and "Pix with manual insertion of transaction account data". 14 The PSP may offer the payer user the option to customize the name of a recurring scheduling with the objective of facilitating its identification in the query of the schedulings. Recommended Mandatory

67
Version 7.3 Scheduled Pix
RECIPIENT: PSP of the payer user
9:30
Recipient / Value
Balance: R$ 1,000.00
Continue Enter agency and account
Cell CPF Key random Email
Select the type of key
+55 (61) 99999 9999
?
R$ 5,000.00
21/02/2024
Small transaction description
Recipient information
CPF/CNPJ: *.777.888 - *
Name: Fernanda Costa
Value
Date
Repeat this Pix
Description (optional)
0 of 140 characters
I understand
The indicated value is higher than your
Scheduled Pix limit available.
Indicate a lower value or select a new date for the scheduling.
9:30
Recipient / Value
Balance: R$ 1,000.00
Continue Enter agency and account
Cell CPF Key random Email
Select the type of key
+55 (61) 99999 9999
?
R$ 1,200.00
21/02/2024
Small transaction description
Recipient information
CPF/CNPJ: *.777.888 - *
Name: Fernanda Costa
Value
Date
Repeat this Pix
Description (optional)
0 of 140 characters
I understand
You indicated a value higher than the limit of R$ 1,000.00 available for schedulings made at this time. Indicate a lower value or select a 17 new date for the scheduling. 16 17 If the user makes a scheduling in the period between 8:00 PM and 12:00 AM, for transactions where the payee user is a natural person distinct from the payer user and with settlement scheduled for the next day, the PSP must verify if the transaction value is within a specific limit available for the time. When the Scheduled Pix transaction value exceeds this limit, the user must immediately receive a message communicating the reason for the scheduling failure. 16 When the user schedules a scheduling, the PSP must verify if the value of the transaction is within the daily Scheduled Pix limit available on the date scheduled for the settlement. For recurring schedulings, the limit verification must be done at least for the nearest scheduled date. If the scheduling exceeds the limit, the user must immediately receive a message communicating the impossibility of finalizing the scheduling and its reason. There must be additional guidance to the user so that they perform some action that enables the execution of a new scheduling, such as requesting an increase in the Scheduled Pix limit, reducing the value informed in the scheduling or changing the scheduled date for the transaction settlement. Mandatory

68
Version 7.3 Scheduled Pix
RECIPIENT: PSP of the payer user
9:30
Scheduled Pix / Posting
Balance: R$ 1,000.00
Cancel scheduling
Value: R$ 40.00
Scheduling made on: 01/12/2024
ONG Vida Animal
Pix Scheduled
RECURRING DATA
First Pix: 01/25/2024
Next payments: monthly, every day 25
Number of payments: 5
Last Pix: 05/25/2024
POSTING
Share Save on cell
Statement /
Return
9:30
Pix Statement / Schedulings
Balance: R$ 1,000.00
Return Finish
SELECT THE SCHEDULINGS TO BE
CANCELLED:
Date: 05/25/2024
ONG Vida Animal - 5 of 5
Select all
Date: 01/25/2024
ONG Vida Animal - 1 of 5
Date: 02/25/2024
ONG Vida Animal - 2 of 5
Date: 03/25/2024
ONG Vida Animal - 3 of 5
Date: 04/25/2024
ONG Vida Animal - 4 of 5
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
Pix
Scheduled
My
Pix limits
Pix
Automatic
Dispute
Pix
MED
9:30
Pix Scheduled
Balance: R$ 1,000.00
Search
Value: R$ 100.00
Fernanda Costa
PIX SCHEDULED
Value: R$ 500.00
Store GHJK
Value: R$ 120.00
ABCD Landscaping
Scheduled Date: 06/05/2024
Recurrence: weekly, until 12/02/2024
Recurrence: monthly, until 05/25/2024
Recurrence: monthly, indefinite
Value: R$ 40.00
ONG Vida Animal
18
20
Functionality may be offered to the payer user that allows editing all schedulings linked to a recurrence at once. The fields subject to editing may include the value and recurrence frequency, and the number of payments or the end date of the scheduling. If the functionality is offered, the deadline for editing a scheduling must be informed to the payer user. 19 Functionality may be offered to the payer user that allows suspending recurring schedulings for a determined period. If the functionality is offered, the deadline for temporary suspension of a scheduling must be informed to the payer user. 18 Cancellation functionality for scheduled transactions must be offered to the payer user. In the case of recurring schedulings, at minimum, the cancellation of the nearest scheduled scheduling must be made available. The payer user must also have access to functionality that allows cancelling all schedulings linked to a recurrence at once. The deadline for cancelling a scheduling must be informed to the user payer. Mandatory Recommended

69
Version 7.3 Scheduled Pix
RECIPIENT: PSP of the payer user
9:30
Camera Email PSP XYZ
20
Calendar
The payment to ONG Vida Animal, in the amount of R$ 40.00, was not made due to lack of balance. A new attempt will be made today, until 21:00, and you will be notified of the result of this new attempt. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar The last payment attempt to ONG Vida Animal, in the amount of R$ 40.00, was made, but it was not possible to execute it due to lack of balance. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar Your daily limit for Scheduled Pix was exceeded, so the payment to ONG Vida Animal, in the amount of R$ 40.00, was not made. To execute the payment, you must make a new Pix. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar The payment to ONG Vida Animal, in the amount of R$ 40.00, was not made, because the Pix key no longer belongs to the payee informed on the day of the scheduling. PSP XYZ 22 24 21 23 22 After the last settlement attempt made by the PSP, if the lack of balance persists, a notification must be sent to the payer user informing the reason for not having been able to execute the Pix transaction. 24 If the scheduled transaction is not executed due to difference in ownership or non-existence of the Pix key at the time of settlement, the PSP must send a notification to the payer user informing that the transaction was not executed for this reason. 25 If the scheduled payment is not executed due to operational failure after sending the payment order for settlement, the PSP must not send a notification to the user, except if the failure occurs in the last settlement attempt. In this case, a notification must be sent informing them that it was not possible to execute the Scheduled Pix payment due to operational failure and that they must make a new Pix. 26 The payer user must receive a notification as soon as the scheduled transaction is settled. When the settlement occurs between zero hours and six hours in the morning, the notification must be sent, preferably, after this time. The notification must contain, at minimum, the following information:

Payee name;
Transaction value
23
If the scheduled transaction is not executed due to insufficiency of the daily limit available for Scheduled Pix transactions, the PSP must send a notification immediately after the end of the first settlement window, informing that the transaction was not executed for this reason. 21 If the scheduled transaction is not executed due to lack of balance, the PSP must send a notification immediately after the end of the first settlement window, informing that the Pix was not executed for this reason and that a new attempt will be made on the same day. It must be indicated even the deadline for the additional mandatory attempt, in order to allow the user to replenish the balance until this time 28 The PSP may send a notification one day before the date of the Scheduled Pix debit informing the user about the need for balance in the account. 27 The method of sending notifications is at the free choice of the PSP. If the notification is via push, part of the information, at the PSP's choice, may be detailed when the user clicks on the notification. Recommended Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
13
Provision of option to the payer user, in the mobile banking interface, to paste code. Pix Copy and Paste

71
Version 7.3 Pix Copy and Paste
RECIPIENT: PSP of the payer user
9:30
Pix Copy and Paste
Balance: R$ 1,000.00
Cancel Continue text
Insert the code in the field below:
9:30
Pix
Pix with
Key / Manual
Pix Copy and Paste
Pix with
QR Code Receive Pix
My
Pix limits
Pix
Automatic
Statement /
Return
My keys
R$10.00
Value Payment via Key
Roberto da Silva
R$30.00
Value
João da Silva
LAST TRANSACTIONS
Cell
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
02
01
After pasting the code in the field, the data will be loaded immediately below for verification. To access the initiation of Pix Copy and Paste payment, the user only needs to press the specific button on the main screen and paste the code in the informed field. 02 The PSP's mobile banking application must make available a quick and easy access option for the user, to make payments for transactions and/or withdrawals of funds in cash, through the code paste option (Pix Copy and Paste). 01 Pix Copy and Paste must be made available on the first screen of the Pix environment. Mandatory

72
Version 7.3 Pix Copy and Paste
RECIPIENT: PSP of the payer user
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
My
Pix limits
Pix
Automatic
Statement /
Return
My keys
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
9:30
Text
00020101021226720014br.gov.b-cb.pix2550bx.com.br/ pix/8b3-da2f3-9a41-40d1- a91abd93113bd4415204000053039865406123.455802BR5913Fulano de Tal6008BRASILIA62190515RP12345678-2019630445C8 Here is the Pix code... Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do Today Chat 9:30 PIX PREVIOUS NEXT Copy Point the cell camera at the QR-code/image below or copy the code and pay in your Internet Banking. 00020101021226720014br.gov.bcb.pix2550bx.com.br/pix/8b3 a2f3-9a41-40d1- a91abd93113bd4415204000053039865406123.455802BR5913Ful ano de Tal6008BRASILIA62190515RP12345678-2019630445C8 QR-code Code FINALIZE YOUR PURCHASE FINALIZE YOUR PURCHASE Polo shirt R$ 50.00 Order summary Shipping: R$ 5.00 Total: R$ 55.00 STORE ZYXW 9:30 BOLETO PAY AT THE STORE CREDIT CARD PIX NEXT PAYMENT METHODS FINALIZE YOUR PURCHASE Polo shirt R$ 50.00 Order summary Shipping: R$ 5.00 Total: R$ 55.00 STORE ZYXW 01 The code that represents the QR Code can be easily sent via messaging applications. The user needs only to copy the received message. After that, the experience is the same for the mobile platform case, from step (2) below. 01 Pix Copy and Paste must be made available on the first screen of the Pix environment. Mandatory

73
Version 7.3 Pix Copy and Paste
RECIPIENT: PSP of the payer user
9:30
Receipt
Share Save to mobile
Statement /
Return
Balance: R$ 1,000.00
Discount: 10% until 02/10/2021
Lucky number: 654321
Fine/Period: After 02/15/2021
Fine: 2%
Interest/Period: Per month
Interest: 1%
ADDITIONAL INFORMATION
CPF/CNPJ: *** .993.555 -**
Name: Nadir da Silva
DEBTOR INFORMATION
PSP: PSP XYZ
CPF/CNPJ: 12.345.678/0001-90
Name: Store ZYXW
RECIPIENT INFORMATION
Final value: R$ 55.00
Fine: R$ 0.00
Interest: R$ 0.00
Original value: R$ 55.00
Date/time: 01/21/2020 at 21:34:05
Transaction ID: 885544756782258
PIX CONFIRMED
9:30
Recipient / Value
Cancel Schedule Finish
Balance: R$ 1,000.00
R$ 55.00
Final value
Discount: 10% until 02/10/2021
Lucky number: 654321
Fine/Period: After 02/15/2021
Fine: 2%
Interest/Period: Per month
Interest: 1%
ADDITIONAL INFORMATION
CPF/CNPJ: *** .993.555 -**
Name: Nadir da Silva
DEBTOR INFORMATION
PSP: PSP XYZ
CPF/CNPJ: 12.345.678/0001-90
Name: Store ZYXW
RECIPIENT INFORMATION
Fine: R$ 0.00
Interest: R$ 0.00
Original value: R$ 55.00
Intended payment date: 02/15/2021
GENERAL INFORMATION
Enter the code in the field below:
00020101021226720014br.gov.bcb.pix2550bx ...
02
After the code, the data regarding the purchase will appear immediately below the field. Example of pasting code. 02 The mobile banking application of the PSP must make available a quick and easy access option for the user, to perform payment transactions, through the paste code option (Pix Copy and Paste). Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
14
Allows Pix users to withdraw cash from withdrawal agents or participants and to consult the locations that make available the service. Pix Withdrawal and Pix Change

75
Version 7.3 Pix Withdrawal and Pix Change
RECIPIENT: PSP of the withdrawing user
9:30
Pix Withdrawal
Balance: R$ 1,000.00
Commercial establishments and banking correspondents cannot charge fees for Pix Withdrawal and Pix Change. You are entitled to 8 free withdrawal transactions per month, including Pix Withdrawal and Pix Change and traditional withdrawals. Access 9:30 Pix Withdrawal Balance: R$ 1,000.00 You can consult information about the Pix Withdrawal and Pix Change service points in "Pix Withdrawal and Pix Change Locations". Skip 9:30 Pix Withdrawal Balance: R$ 1,000.00 With Pix Withdrawal and Pix Change, you will have new possibilities to make withdrawals, with Pix Change, the withdrawal happens together with the realization of a purchase. Commercial establishments and banking correspondents may, at their discretion, make Pix Withdrawal and Pix Change available. Pix Withdrawal can also be made available in electronic cash machines, at the discretion of participating institutions. Skip 01 02 It is recommended to make available the information in item 01 in a help or informational option of Pix. 01 It is mandatory that, upon first access to Pix, after the start of the validity of Pix Withdrawal and Pix Change, the user is informed about the main rules of the service, addressing, at minimum:

What the service is;
That commercial establishments and banking correspondents may, at their discretion,
make Pix Withdrawal and Pix Change available;
That participating institutions may, at their discretion, make Pix Withdrawal available
directly through electronic cash machines;
That the user can consult information about Pix Withdrawal and Pix Change service points, when the PSP of the withdrawing user makes this functionality available;
Information about the fees practiced by the PSP, including regarding the free services
defined in the regulation;
That it is prohibited to charge fees by commercial establishments or
banking correspondents.
Recommended
Mandatory

Recommended 7
A functionality may be made available that allows the user to consult information regarding the locations where Pix Withdrawal and Pix Change are made available. 03 Mandatory The participant that makes available the consultation functionality cannot give discriminatory treatment, omitting or restricting information from any withdrawal agent or participant that makes Pix Withdrawal and/or Pix Change available, doing so based on open data published on the Central Bank's Open Data Portal. 04 9:30 Pix Nadir da Silva Balance: R$ 1,000.00 CPF Email Key

Random Mobile
LAST TRANSACTIONS
Roberto da Silva João da Silva
Payment

via Key
My

keys
Statement /

Return
My

Pix limits
Pix

Scheduled
Pix

Automatic
Pix with

Key / Manual
Pix Copy

and Paste
Pix with

QR Code Receive Pix
My

Pix limits
Pix

Automatic
9:30
Pix
Balance: R$ 1,000.00
CPF Email
Complain

here Pix Locations

Withdrawal / Change Key

Random Mobile
LAST TRANSACTIONS
Roberto da Silva João da Silva
Payment

via Key
Receipt

via Key
MED
Pix
03 Scheduled
Complain

here Pix Locations

Withdrawal / Change
Dispute

Pix
Pix with

Key / Manual
Pix Copy

and Paste
Pix with

QR Code Receive Pix
Value
R$10.00
My

keys
To access the option
"Pix Withdrawal and Pix Change Locations", the user just needs to press the screen in the indicated location and drag to the left. Statement /

Return
Value
R$30.00
Receipt

via Key Nadir da Silva
Value
R$10.00
Value
R$30.00
76

77
Version 7.3 Pix Withdrawal and Pix Change
RECIPIENT: PSP of the withdrawing user
9:30
Pix
Balance: R$ 1,000.00
Pix
Change
Pix
Change
Pix
Withdrawal
Store
$ Maximum value (8pm to 10pm): R$ 100.00
$ Maximum value (7am to 8pm): R$ 300.00
From Monday to Saturday, from 7am to 10pm.
Av. AAA, 180, Center, Rio de Janeiro. Zip: 11111-222 Store KJHG $ Maximum value (4pm to 7pm): R$ 150.00 $ Maximum value (9am to 4pm): R$ 300.00 From Monday to Saturday, from 9am to 7pm. Rua da CCC, 200, Center, Rio de Janeiro. Zip: 44444-333 Store GHJK Withdrawal agents and participants facilitating the Pix Withdrawal and/or Pix Change service. 9:30 Pix Pix with Key / Manual Pix Copy

and Paste
Pix with
QR Code Receive Pix
R$10.00
Value Payment

via Key
Roberto da Silva
R$30.00
Value
João da Silva
LAST TRANSACTIONS
Mobile
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
Pix Locations

Withdrawal / Change
Complain

here Dispute
Pix
MED
Pix
Scheduled
05
05
08
It is recommended to make available to the user the geolocation of the service points that will make the withdrawal service available. 07 The information contained in the previous items must be kept updated, reflecting any changes that occurred. 06 The provision of the following information is optional for withdrawal agents, but if provided, must be made available by participants to users:

Maximum value available per transaction;
Conditions for making the withdrawal service available. The field must not contain HTML
tags. The payer user application must display the characters of this field literally and, therefore, must not render links or any dynamic content. 05 When the consultation functionality is made available, the following information must be available to users at the time of consultation:
Name of the withdrawal agents or the participant that makes Pix
Withdrawal and/or Pix Change available directly. The name of the withdrawal agent informed must be the Trade Name of the company, if it exists. If it does not exist, the informed name must be the Business Name/Legal Name. In the case of the participant itself, it must be the reduced name registered in the Information System on Entities of Interest of the Central Bank (Unicad);
Address of the service points that will make the withdrawal service available;
Product made available by the withdrawal agent (Pix Withdrawal, Pix Change or both products)
or by the participant (Pix Withdrawal);
Availability (days and hours) of the withdrawal service.
Recommended
Mandatory

Mandatory 7
It must be evident to the withdrawing user that it is a Pix Withdrawal transaction. 09 The PSP of the withdrawer must display the information that no additional value can be charged at the time of the transaction. 10 Before the confirmation of a Pix Withdrawal through static QR Code, the following data must be returned to the withdrawing user:

Name and CNPJ of the withdrawal agent or the participant that makes Pix Withdrawal available directly.

The agency number and the account number of the payee must not be returned to the withdrawing user. The return of the information of the PSP name of the payee is at the discretion of the participant;

The "infoAdicionais" field, if informed, must contain only characters or HTML without any dynamic content, such as scripts (javascript, php, cgi, among others);

The withdrawal value.
11
If there is a value in the static QR Code, this field cannot be altered by the user withdrawer. 12 If there is no value in the static QR Code, the user withdrawer must type it before the confirmation of the withdrawal. 13 9:30 Pix Nadir da Silva Balance: R$ 1,000.00 CPF Email Key

Random Mobile
LAST TRANSACTIONS
Roberto da Silva João da Silva
Payment

via Key
Pix

Automatic
Pix

Scheduled
My

keys
Statement /

Return
My

Pix limits
Pix with

Key / Manual
Pix Copy

and Paste
Pix with

QR Code Receive Pix
Receipt

via Key
Pix

Installment
Dispute
Pix
Make available the information indicated in item 01.
11
Complain

here
Pix Locations

Withdrawal / Change
10
9:30
Pix Withdrawal
Balance: R$ 1,000.00
RECIPIENT INFORMATION ?
Store GHJK
CNPJ: 00.111.222/0001-33
WITHDRAWAL VALUE
R$ 10.00
No additional value can be charged at the time of the transaction. 09 12 Value R$10.00 Value R$30.00 Pix Withdrawal - Static QR Code 9:30 Pay with QR-Code Balance: R$ 1,000.00 Point the camera at a Pix QR Code Cancel Pix with Key / Manual To perform a Pix Withdrawal (Static QR) the user must select the Pix with QR Code option in the environment dedicated to Pix. Cancel Finish 78

79
Version 7.3 Pix Withdrawal and Pix Change
RECIPIENT: PSP of the withdrawing user
9:30
Pay with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Point the camera at a
Pix QR Code
Pix Withdrawal - Dynamic QR Code
9:30
Pix Withdrawal
Balance: R$ 1,000.00
Cancel Finish
No additional value can be charged at the time of the transaction. R$ 10.00 WITHDRAWAL VALUE CPF/CNPJ: *** .777.888 -** Name: Nadir da Silva WITHDRAWER INFORMATION CNPJ: 00.111.222/0001-33 PSP: PSP XYZ Store GHJK RECIPIENT INFORMATION ? 9:30 Pix Receive Pix Pix with QR Code Pix Copy

and Paste
Pix with
Key / Manual
My
Pix limits
Pix

Automatic
Statement /

Return
My

keys
R$30.00
Value
João da Silva
R$10.00
Value Payment

via Key
Roberto da Silva
LAST TRANSACTIONS
Mobile
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
14
Make available the information indicated in item 01.
14
Before the confirmation of a Pix Withdrawal through dynamic QR Code, the following data must be returned to the withdrawing user:

Name and CNPJ of the withdrawal agent or the participant that makes Pix Withdrawal available directly.
The agency number and the account number of the payee must not be returned
to the withdrawing user. The return of the information of the PSP name of the payee is at the discretion of the participant;
The "infoAdicionais" field, if informed, must contain only characters or HTML without
any dynamic content, such as scripts (javascript, php, cgi, among others);
The "Request to Payer" field, if informed: description and text box for
filling by the withdrawing user;
The withdrawal value (if the receiving user informs that the value can be altered
using the respective value alteration modality field, as defined in the Pix Initiation Standards Manual, the value must be allowed to be edited by the withdrawing user. Otherwise, the value cannot be editable). Mandatory

80
Version 7.3 Pix Withdrawal and Pix Change
RECIPIENT: PSP of the withdrawing user
9:30
Pay with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Point the camera at a
Pix QR Code
Pix Change - Dynamic QR Code
9:30
Pix Change
Balance: R$ 1,000.00
Cancel Finish
No additional value can be charged at the time of the transaction. R$ 60.00 Final value Change value: R$ 10.00 Purchase value: R$ 50.00 VALUES CPF/CNPJ: *** .777.888 -** Name: Nadir da Silva WITHDRAWER INFORMATION PSP: PSP XYZ CNPJ: 00.111.222/0001-33 Store GHJK RECIPIENT INFORMATION ? 9:30 Pix Receive Pix Pix with QR Code Pix Copy

and Paste
Pix with
Key / Manual
My
Pix limits
Pix

Automatic
Statement /

Return
My

keys
R$30.00
Value
João da Silva
R$10.00
Value Payment

via Key
Roberto da Silva
LAST TRANSACTIONS
Mobile
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
16
Make available the information indicated in item 01.
16
Before the confirmation of a Pix Change through dynamic QR Code, the following data must be returned to the withdrawing user:

Name and CNPJ of the withdrawal agent that makes Pix Change available. The name informed must
be the Trade Name of the company, if it exists. If it does not exist, the informed name must be the Business Name/Legal Name;
The agency number and the account number of the payee must not be returned
to the withdrawing user. The return of the information of the PSP name of the payee is at the discretion of the participant;
The "infoAdicionais" field, if informed, must contain only characters or HTML without
any dynamic content, such as scripts (javascript, php, cgi, among others);
The "Request to Payer" field, if informed: description and text box for
filling by the withdrawing user;
The purchase value;
The change value (if the receiving user informs that the value can be altered
using the value alteration modality field, as defined in the Manual of Standards for Pix Initiation, the value must be allowed to be edited by the user. If otherwise, the value cannot be editable);
The final value of the transaction.
15 It must be evident to the withdrawing user that it is a Pix Change transaction. Mandatory

81
Version 7.3 Pix Withdrawal and Pix Change
RECIPIENT: PSP of the withdrawing user
9:30
Pix Change Receipt
Balance: R$ 1,000.00
Share Save to mobile
Statement /

Return
If this transaction is subject to fees, the value R$ XX.XX will be charged. CPF: *** .777.888 -** Name: Nadir da Silva WITHDRAWER INFORMATION PSP: PSP XYZ CNPJ: 00.111.222/0001-33 Name: Store GHJK RECIPIENT INFORMATION Final value: R$60.00 Change value: R$10.00 Purchase value: R$50.00 Date/time: 07/01/2021 - 15:35:10 Transaction ID: 885544756782258 PIX CONFIRMED 9:30 Pix Withdrawal Receipt Balance: R$ 1,000.00 Share Save to mobile Statement /

Return
If this transaction is subject to fees, the value R$ XX.XX will be charged. CPF: *** .777.888 -** Name: Nadir da Silva WITHDRAWER INFORMATION PSP: PSP XYZ CNPJ: 00.111.222/0001-33 Name: Store GHJK RECIPIENT INFORMATION Withdrawal value: R$10.00 Date/time: 07/01/2021 - 15:35:10 Transaction ID: 885544756782258 PIX CONFIRMED 19 19 20 If the incidence of fees cannot be determined at the time of providing the service of sending resources with the purposes of withdrawal or change, within the scope of Pix, the receipt must inform the value of the fee subject to charge. 19 Make available Pix Withdrawal or Pix Change receipt during the period established in the current regulation, containing, at minimum, the information of the name, the CPF (masked or not) and the name of the PSP of the withdrawing user and the name, the CNPJ and the name of the PSP of the receiving user, as well as value and ID of the transaction, hour/minute/second (Brasília time) of settlement, and value of the fee charged, if it can be determined at the time of the transaction. The message and the minimum fields that must be presented to the user are represented in the screens to the side.

The ID/transaction refers to the "EndtoEndID" present in the pacs.008.
18
The withdrawing user must receive notification as soon as the transaction is completed. The method of sending the notification is at the free choice of the PSP. The notification must contain, at minimum, the following information:
Name of the payee and final value of the transaction.
17
If any type of credit is used to perform Pix with the purpose of withdrawal or change, the withdrawing user must be informed of this before confirming the payment. Mandatory message: It must highlight the value and the credit line that will be used. Examples:
Attention: to complete the transaction, R$ XX.XX of the/o
[Name_of_credit_line]/To finalize this Pix, R$ [value] will be withdrawn from the credit line [name of the credit line]. Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
15
Functionality that allows Pix users to perform transactions recurring automatically, with prior authorization. Automatic Pix

Mandatory 3
In the Pix environment, the "Automatic Pix" menu must be made available with, at minimum, the following functionalities:

QR Code reading for the purpose of authorizing Automatic Pix;

Consultation and management of pending authorizations;

Consultation and management of active authorizations;

Consultation and management of scheduled payments;

Consultation of the history of authorizations;

Learn More.
01
Information must be made available for each item of the "Automatic Pix" menu, addressing, at minimum, the following points:

QR Code reading for authorization: possibility of reading QR Code provided by the payee so that the payer user can effectuate an authorization of recurring payments through Automatic Pix.

Pending authorizations: authorizations for recurring payments through Automatic Pix awaiting confirmation by the payer user.

Active authorizations: authorizations for recurring payments through Automatic Pix granted by the payer user and that are active.

Through this functionality, the user can, for each authorization:

Establish the maximum value of recurring payments, in cases of variable value authorization;

Define whether they wish to receive notifications regarding the scheduling of payments;

Express themselves on the use of pre-approved credit line in case of insufficient balance (e.g., overdraft) for payments through Automatic Pix;

Cancel the authorization.

Scheduled payments: functionality that allows consultation and cancellation of scheduled payments within the scope of Automatic Pix.

History of authorizations: functionality that allows consulting all authorizations of recurring payments through Automatic Pix - active, pending or cancelled - with date of authorization and cancellation, if they have already been made and cancelled, respectively.

Authorization settings (if this functionality is made available): functionality that allows the payer user to edit a parameter of the authorization (e.g., maximum payment value) for all authorizations in a single session.

My Automatic Pix Limit (if this functionality is also made available in the Automatic Pix menu): functionality that allows the user to consult and manage daily limit of the total value of Automatic Pix transactions.

Learn more: information about what the service is, advantages and operation of Automatic Pix, as provided in item 4. 02 Recommended In the "Automatic Pix" menu, functionalities for consultation and management of authorization parameters and Automatic Pix limit can be made available. 03 9:30 Pix Nadir da Silva Balance: R$ 1,000.00 CPF Email Key

Random Mobile
LAST TRANSACTIONS
Roberto da Silva João da Silva
Payment

via Key
My

keys
Statement /

Return
Pix

Automatic
My

Pix limits
Pix with

Key / Manual
Pix Copy

and Paste
Pix with

QR Code Receive Pix
03
9:30
Automatic Pix
AUTOMATIC PIX ?
Read QR code for authorization ?
? Pix Locations

Withdrawal / Change
Active authorizations ?
Scheduled payments ?
History of authorizations ?
Authorization settings ?
My Automatic Pix Limit ?
Learn more ?
02
Value
R$10.00
Value
R$30.00
Pix

Scheduled 01
Receipt

via Key Balance: R$ 1,000.00
Pix

Installment Pending authorizations Dispute

Pix
Complain

here
83

84
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Pix Automatic
Balance: R$ 1,000.00
Access
How Pix Automatic works
You confirm the Pix Automatic authorization for each service only once via your account app. With each service charge, the payment is scheduled and executed via Pix, automatically. Payments can occur on any day (weekdays and non-weekdays). You can cancel the Pix Automatic authorization at any time. You can cancel a scheduled payment until 23:59 on the day before the payment date. 9:30 Pix Automatic Balance: R$ 1,000.00 Skip Your payment is executed on the correct date, automatically, without delay or fines. It is free! You see the date of the first payment when authorizing Pix Automatic. You can define the maximum payment value, choose whether to receive or not notifications upon scheduling and disable the use of pre-approved credit line (e.g. overdraft). It can be activated for the most varied payments (electricity, water, condominium, school, subscription services, etc). Check if the company you want to pay offers this option. Advantages of Pix Automatic 9:30 Pix Automatic Balance: R$ 1,000.00 Skip What is Pix Automatic With Pix Automatic, your recurring payments are made upon prior authorization via your account app, without you needing to confirm the operation for each charge. It's Pix bringing even more convenience to you! 04 It is mandatory, upon first access to the Pix environment, after the start of the validity of Pix Automatic, that the user be informed about the main rules of the service, addressing, at minimum, what the service is, its advantages (including free of charge), general functioning addressing authorization, scheduling, possibility of canceling the scheduling and the authorization, possibility of configuring maximum value, notifications of scheduling and use of credit line, as well as making a new attempt of payment on the same day, if the payment is not executed due to insufficient balance, and the possibility of making new payment attempts, at the discretion of the payee, on days later. Examples:

What is Pix Automatic:
With Pix Automatic, your recurring payments are made upon prior
authorization via your account app, without you needing to authorize each payment. It's Pix bringing even more convenience to you!
Advantages of Pix Automatic
Your payment is executed on the correct date, automatically, without delay or fines;
It is free;
You see the expected date of the first payment when authorizing Pix Automatic;
You configure as you prefer. You can define the maximum payment value, choose
whether to receive or not notifications upon scheduling and disable the use of pre-approved credit line (e.g. overdraft);
It can be activated for the most varied periodic payments (electricity, water,
condominium, school, gym, subscription services, etc). Check if the company you want to pay offers this option.
Functioning of Pix Automatic
You confirm the authorization for each service only once via your account app;
With each charge, the payment is scheduled and executed, automatically;
You receive a notification upon scheduling and can check if the value is correct
and if you will have sufficient balance. The scheduling will appear in future transactions and in "Scheduled Payments" in the Pix Automatic menu;
You receive another notification when the payment is executed, with information
such as payment date, value and name of the payee;
Payments can occur on any day (weekdays and non-weekdays);
If on the debit date there is insufficient balance and the payment is not executed
by 8:00, you will receive a notification that the payment was not made and at least one more attempt will be made on the same day;
You can cancel a Pix Automatic authorization at any time;
You can cancel a scheduling of a specific payment until 23:59 on the
day before the payment date;
If any payment is executed in disagreement with any parameter of the
authorization, you may contest the transaction.
Mandatory

85
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Pending Authorizations
Balance: R$ 1,000.00
ABC School
Streaming Top
Energy S/A
The following recurring payments via
Pix Automatic are pending authorization.
Select the payment you wish to authorize:
PENDING AUTHORIZATIONS
9:30
Pix Automatic
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Scheduled Payments
Authorization Settings
Authorization History
Learn More
Active Authorizations
Pending Authorizations
Scan QR Code for Authorization
PIX AUTOMATIC
My Pix Automatic Limit ?
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
My
Pix Limits
Pix
Automatic
Statement /
Return
My keys
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell Phone
CPF
Key
Random
E-mail
Balance: R$ 1,000.00
Nadir da Silva
9:30
Camera E-mail PSP XYZ
20
Calendar
The authorization request for payment of the electricity bill to Energy S/A, in the name of Nadir da Silva, is already available, until 12/30, in Pix Automatic. Access "Pix Automatic" -> "Pending Authorizations" and confirm the authorization PSP XYZ 07 05 08 After selecting the payee in the "Pending Authorizations" menu regarding journey 1, the user must be directed to the screen with the authorization information (continuation of the authorization journey in item 16). 07 The confirmation of the authorization of recurring payments via Pix Automatic in journey 1 must always be executed in the logged-in Pix account environment. Upon clicking the "Pending Authorizations" menu, the list of authorizations that have not yet been confirmed by the user must be displayed, identified by the name of the payee, which, at the PSP's discretion, may also inform the identifier of the charge object (for example, the contract number or customer code). It is recommended that the list be sorted from oldest to newest. The PSP, at its discretion, may offer other sorting options. The name of the payee must be the Trade Name of the company, if it exists. If it does not exist, the name provided must be the Corporate Name/Legal Name. 06 In journey 1, if on the day of expiration of the pending authorization the user has not executed its confirmation, the payer PSP must send a notification with, at minimum, the following information:

Alert of expiration of the authorization request;
Name of the payee;
Name of the debtor, when it is different from the payer;
Object of the payment.
The notification may contain a link to direct the user to the screen with the information of the authorization, upon prior authentication in the account app. 05 In situations where there is direct interaction between the payer user and the payee user, outside the Pix ecosystem, and it is agreed that payments will be made in a recurring manner via Pix Automatic (journey 1 of authorization), the payer PSP must send a notification to the payer user immediately after receiving the request for confirmation of the recurrence from the payee PSP, informing that he must access the menu "Pending Authorizations" to confirm the Pix Automatic authorization (the notification may contain a link to direct the user to the screen with the information of the authorization, upon prior authentication in the account app). The notification must contain, at minimum:
Name of the payee;
Name of the debtor, when it is different from the payer;
Object of the payment;
Expiration date of the pending authorization.
The "Object of the payment" corresponds to the "descricao" field of pain.009, of optional filling. If it has been filled, it must be displayed to the payer user. Mandatory

86
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Pix Automatic Authorization
Balance: R$ 1,000.00
Delete Continue
R$ 800.00
Object of the payment: electricity bill,
Acácias Street
First payment: 01/21/2024
Maximum payment value
Next payments: monthly, day 21
Authorization term: indefinite
ADDITIONAL INFORMATION
Customer code: 874354-7
CPF: *** .222.333 -**
Name: Nadir da Silva
DEBTOR INFORMATION
Name: Energy S/A
CNPJ: 03.649.902/0001-23
PAYEE INFORMATION
?
If the value of the recurring payment is higher than the maximum value defined, the payment will not be scheduled and you will be notified to seek other ways to execute the payment. ? Finish I will not authorize Pix Automatic because:
I have no interest in Pix Automatic for this payment I do not recognize the relationship with this payee 9:30 Pix Automatic Authorization Balance: R$ 1,000.00 R$ 800.00 Delete Continue ? Object of the payment: electricity, Street of the Acácias First payment: 01/21/2024 Maximum payment value Next payments: monthly, day 21 Authorization term: indefinite ADDITIONAL INFORMATION Customer code: 874354-7 CPF: *** .222.333 -** Name: Nadir da Silva DEBTOR INFORMATION Name: Energy S/A CNPJ: 03.649.902/0001-23 PAYEE INFORMATION ? If the value of the recurring payment is higher than the maximum value defined, the payment will not be scheduled and you will be advised. 9:30 Pending Authorizations Balance: R$ 1,000.00 ABC School Streaming Top Energy S/A The following recurring payments via Pix Automatic are pending authorization. Select the payment you wish to authorize:
PENDING AUTHORIZATIONS
09
09
10 10
The screen with the authorization information (items 16 and 19) may contain a help button or "Learn More", directing the user to the content regarding the main rules of Pix Automatic set forth in item 4. 09 A functionality for rejecting an authorization of journey 1 that is pending confirmation must be made available to the user, who must indicate as motivation that he does not recognize the relationship with the payee or that he has no interest in Pix Automatic for that payment. Mandatory Recommended

87
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Receipt
Balance: R$ 564.22
Share Save on cell
Statement /
Return
PIX CONFIRMED
PSP: PSP XYZ
CPF/CNPJ: *** .993.555 -**
Name: Nadir da Silva
PAYER INFORMATION
PSP: PSP ABCD
CPF/CNPJ: 03.649.902/0001-93
Name: Energy S/A
RECIPIENT INFORMATION
Identifier: Light Account
Value/final: R$435.78
Date/time: 01/21/2020 - 21:34:05
Transaction ID: 885544756782258
No Yes
You can make the next payments of
Energy S/A via Pix Automatic.
Do you want to know more about it?
9:30
Recipient / Value
Balance: R$ 1,000.00
Cancel Schedule Finalize
R$ 435.78
Final value
PSP: PSP ABCD
Identifier: Light Account - Acácias Street
CNPJ: 03.649.902/0001-93
Name: Energy S/A
RECIPIENT INFORMATION
9:30
Pix with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Point the camera at a
Pix QR Code
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
My
Pix Limits
Pix
Automatic
Statement /
Return
My keys
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell Phone
CPF
Key
Random
E-mail
Balance: R$ 1,000.00
Nadir da Silva
11
After reading the QR Code, the user will be directed to an area with information about the payment and information about the DICT. 13 In journey 4, if an error occurs in reading only the part of the QR Code relative to the recurrence, the user must be allowed to complete the payment journey, without advancing to the step of offering Pix Automatic for the next payments. 12 In journey 4, after confirming that he wishes to authorize Pix Automatic for the next payments, the user must be directed to the screen with the information of the authorization (continuation of the authorization journey in item 16). 11 In situations where the user is making a payment via a QR Code, and this contains information relative to Pix Automatic (journey 4 of authorization), at the end of this journey the possibility of making the next payments via Pix Automatic must be offered, giving the option for the user to cancel or continue to confirm the authorization. Mandatory

88
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Scan QR Code for Authorization
Balance: R$ 1,000.00
Cancel Pix Copy and Paste
Point the camera at a
Pix QR Code
QR Code reading in the environment of Pix Automatic 9:30 Pix Copy and Paste Balance: R$ 1,000.00 Pix with QR-Code Cancel Continue Code Insert the code in the field below:
Pix Copy and Paste
9:30
Pix with QR-Code
Balance: R$ 1,000.00
Cancel Pix with Key / Manual
Point the camera at a
Pix QR Code
QR Code reading in the journey of payment
9:30
Pix Automatic
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Scheduled Payments
Authorization Settings
Authorization History
Learn More
Active Authorizations
Pending Authorizations
Scan QR Code for Authorization
PIX AUTOMATIC
My Pix Automatic Limit ?
9:30
Pix
Receive Pix Pix with
QR Code
Pix Copy and Paste
Pix with
Key / Manual
My
Pix Limits
Pix
Automatic
Statement /
Return
My keys
R$30.00
Value
João da Silva
R$10.00
Value Payment via Key
Roberto da Silva
LAST TRANSACTIONS
Cell Phone
CPF
Key
Random
E-mail
Balance: R$ 1,000.00
Nadir da Silva
14
15
In journey 2, after reading the QR Code provided by the payee for authorization of Pix Automatic or the insertion of the code via Pix Copy and Paste, the user must be directed to the screen with the information of the authorization (continuation of the journey of authorization in item 16). 14 In situations where the payee user makes available, through actions of communication, digital channels or other means, a QR Code and/or the respective code, with the information of the recurrence for purposes of authorization of Pix Automatic (journey 2 of authorization), the payer PSP must make possible:

the reading of this specific QR Code in the logged-in account environment, in the menu of Pix
Automatic, so that the payer user can evaluate the information and confirm the authorization.
the reading of this specific QR Code by the same QR Code reader used in journeys
of payment by QR Code.
the insertion of the code via the Pix Copy and Paste option.
Mandatory

89
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Pix Automatic Authorization Receipt
Balance: R$ 1,000.00
Share Save on cell
Active
Authorizations
Object of the payment: electricity bill,
Acácias Street.
ADDITIONAL INFORMATION
ID: RR8863984020240110z817zghe67d
Authorization term: indefinite
Maximum payment value: R$ 800.00
Customer code: 874354-7
Next payments: monthly, day 21
First payment: 01/21/2024
Name: Nadir da Silva
CPF: *** .222.333 -**
DEBTOR INFORMATION
CNPJ: 03.649.902/0001-23
Name: Energy S/A
PAYEE INFORMATION
You will be notified when the recurring payments, subject to the availability of Pix Automatic limit, are scheduled. Upon accessing Pix Automatic -> Active Authorizations, you can:

Disable the receipt of notifications or the
use of credit limit for payments via
Pix Automatic;
Change the maximum payment value; or
Request the cancellation of this authorization at
any time.
AUTHORIZATION CONFIRMED
9:30
Confirmation
Balance: R$ 1,000.00
Cancel Continue Finalize
Maximum payment value: R$ 800.00
Authorization term: indefinite
Next payments: monthly, day 21
First payment: 01/21/2024
Customer code: 874354-7
Object of the payment: electricity bill,
Acácias Streets
ADDITIONAL INFORMATION
CPF: *** .222.333 -**
Name: Nadir da Silva
DEBTOR INFORMATION
Name: Energy S/A
CNPJ: 03.649.902/0001-23
PAYEE INFORMATION
IMPORTANT! Check all information before authorizing Pix Automatic. 9:30 Pix Automatic Authorization Balance: R$ 1,000.00 If the value of the recurring payment is higher than the maximum value defined, the payment will not be scheduled and you will be advised. This authorization provides for payment attempts after the due date, if the original payment cannot be executed due to insufficient balance. Payments executed after the due date may result in interest and fines added to the next payment. Maximum payment value Authorization term: indefinite Next payments: monthly, day 21 First payment: 01/21/2024 Customer code: 874354-7 Object of the payment: electricity bill, Acácias Streets ADDITIONAL INFORMATION CPF: *** .222.333 -** Name: Nadir da Silva DEBTOR INFORMATION CNPJ: 03.649.902/0001-23 Name: Energy S/A PAYEE INFORMATION Maximum value starting from R$ 300.00 Delete Continue ? ? 17 16 17 As soon as the authorization of the recurring payment via Pix Automatic is completed (journeys 1, 2 and 4), the payer user must be immediately informed that:
Notifications will be sent when payments are scheduled;
The receipt of scheduling notifications and the use of credit limit for
payments via Pix Automatic can be disabled;
The cancellation of the authorization can be done at any time;
The maximum payment value can be changed (if established);
Payments are conditioned to the availability of balance and Pix Automatic limit.
The information of the authorization ID must be made available.
16
In journeys 1, 2 and 4, before the confirmation of the authorization of recurring payments via Pix Automatic, the following information must be displayed, at minimum:
Name of the payee;
CNPJ of the payee;
Name of the debtor;
CPF (masked)/CNPJ of the debtor;
Object of the payment (if informed);
Identifier of the charge object (contract number, customer code, etc);
Expected date of the first payment;
Periodicity of future payments;
Authorization term or number of installments;
Expected value of payments (if fixed);
Retry rules on other days, as defined by the payee user (if
existent).
The name of the payee user must be the Trade Name of the company, if it exists. If it does not exist, the name provided must be the Corporate Name/Legal Name. The return of the information of the name of the payee PSP is optional and is at the discretion of the participant. The "Object of the payment" corresponds to the "descricao" field of pain.009 or to the "vinculo.objeto" of the QR Code payload, of optional filling. If it has been filled, it must be displayed to the payer user. The "Identifier of the charge object" corresponds to the "numeroContrato" field of pain.009 or to the "vinculo.contrato" of the QR Code payload, of mandatory filling. The authorization term can be for an indefinite time. If the payment values are variable, an option must be made available for the user to define whether he wishes to establish the maximum value for the payments. If the user opts to establish the maximum value, the field for filling must be enabled and informed that if the value of a payment is higher than the maximum value defined, the payment will not be scheduled and the user will be notified. If the payee user has established a minimum value for the maximum value field, the PSP must inform this data to the payer user and only allow the configuration of the value from the minimum established. If the authorization establishes attempts to settle the payment after its due date, the payer PSP must inform the payer user of the existence of this condition and that it may result in the incidence of interest and fines on the next charge. Mandatory

90
Version 7.3 Pix Automatic
DESTINATARY: PSP of the payer user
9:30
Scan QR Code for Authorization
Balance: R$ 1,000.00
Cancel Pix Copy and Paste
Point the camera at a
Pix QR Code
"Scan QR Code", in the environment of Pix Automatic 9:30 Pay with Pix Copy and Paste Balance: R$ 1,000.00 Code Insert the code in the field below:
Cancel Continue
Pix Copy and Paste
9:30
Pay with QR-Code
Balance: R$ 1,000.00
QR Code reading in the journey of payment
Cancel Pix with Key / Manual
Point the camera at a
Pix QR Code
9:30
Pix
Automatic
PREVIOUS NEXT
Copy
Point the cell phone camera at the QR-code/image below or copy the code and pay in your Internet Banking. 00020101021226720014br.gov.bcb.pix2550bx.com.br/pix/8b3 a2f3-9a41-40d1- a91abd93113bd4415204000053039865406123.455802BR5913Ful ano de Tal6008BRASILIA62190515RP12345678-2019630445C8 Pix Copy and Paste QR-code FINALIZE YOUR PURCHASE FINALIZE YOUR PURCHASE Signature Digital Library Order Summary Total: R$ 19.90 STORE ABC 18 In situations where the payee makes available a QR Code or a code with the information of the recurrence and the immediate payment (journey 3 of authorization), the PSP payer must make possible the reading of this QR Code or the insertion of the code via the Pix Copy and Paste option for purposes of confirmation of the first immediate payment and of the authorization of the subsequent recurring payments via Pix Automatic. The reading of this QR must be allowed both by the "Scan QR Code" option, in the environment of Pix Automatic, as well as by the QR Code reading option in payment journeys, as well as by the use of Pix Copy and Paste. Mandatory

91
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Authorization Receipt
Balance: R$ 1,000.00
Share Save to cell
Active
Authorizations
Name: Nadir da Silva
CPF: *** .222.333 -**
DEBTOR INFORMATION
Name: Store ABC
CNPJ: 15.436.940/0001-03
RECEIVER INFORMATION
ADDITIONAL INFORMATION
Value of recurring payments: R$ 17.90
Authorization term: 24 weeks
Payment object: Digital Library
ID: RN0375890220240105ej873k8il9a
First recurring payment: 17/01/2024
Value: R$19.90
Date/time: 10/01/2024 - 9:30:56
ID/Transaction: 975342678309753
The first payment was made!
Subscription number: 5282023
Next payments: weekly, on
Wednesdays
You will be notified when the recurring payments, subject to the availability of the Pix Automatic limit, are scheduled. By accessing Pix Automatic -> Active Authorizations, you can:

Disable the receipt of notifications or the
use of credit limit for payments by means of Pix Automatic;
Change the maximum payment value; or
Request the cancellation of this authorization at
any time.
AUTHORIZATION CONFIRMED
9:30
Confirmation
Balance: R$ 1,000.00
Cancel Continue Finish
ADDITIONAL INFORMATION
Payment object: Digital Library
Next payments: weekly, on
Wednesdays
Value of recurring payments: R$ 17.90
First recurring payment: 17/01/2024
Immediate payment value: R$ 19.90
Authorization term: 24 weeks
Subscription number: 5282023
CPF: *** .222.333 -**
Name: Nadir da Silva
DEBTOR INFORMATION
Name: Store ABC
CNPJ: 15.436.940/0001-03
RECEIVER INFORMATION
I authorize future recurring payments related to the Digital Library subscription. IMPORTANT! Check all information before making the first immediate payment and authorizing Pix Automatic. 9:30 Pix Automatic Authorization Balance: R$ 1,000.00 ? Cancel Continue Payment object: Digital Library Next payments: weekly, on Wednesdays Value of recurring payments: R$ 17.90 First recurring payment: 17/01/2024 Immediate payment value: 19.90 Authorization term: 24 weeks ADDITIONAL INFORMATION The first payment, in the amount of R$ 19.90, will be made immediately, continuing the Pix Automatic authorization process. Subscription number: 5282023 CPF: *** .222.333 -** Name: Nadir da Silva DEBTOR INFORMATION Name: Store ABC CNPJ: 15.436.940/0001-03 RECEIVER INFORMATION 19 19 In journey 3, before the confirmation of the immediate payment and the authorization of Pix Automatic as a form of recurring payment, the following information must be displayed, at a minimum:
Receiver's name;
Receiver's CNPJ;
Debtor's name;
Debtor's CPF (masked)/CNPJ;
Payment object (if informed);
Identifier of the billing object (contract number, customer code, etc);
Scheduled date of the first recurring payment;
Frequency of future payments;
Authorization term or number of installments;
Expected value of payments (if fixed);
The "infoAdicionais" field, if informed, must contain only characters or HTML without
any dynamic content, such as scripts (javascript, php, cgi, among others);
The "Request to Payer" field, if informed: description and text box for
filling in by the payer user.
The "Description" field ("informacoesEntreUsuarios" of pacs.008) must not be made available for filling in by the payer user in transactions initiated by QR Code. If the receiver user informs that the value of the immediate payment can be changed using the "Value change modality" field, as defined in the Pix Initiation Standards Manual, the payer user must be allowed to edit the value. Otherwise, the value cannot be editable. The receiver user's name must be the Company's Trade Name, if it exists. If it does not exist, the name informed must be the Corporate Name/Legal Name. The agency number and the receiver's account number must not be presented to the payer user. The return of the receiver PSP's name information is optional and is at the participant's discretion. The authorization term can be for an indefinite period. If the payment values are variable, an option must be made available for the user to define whether they wish to establish the maximum value for payments. If the user activates this option, the field for filling in must be enabled and informed that if the value of a recurring payment is higher than the maximum value defined, the payment will not be scheduled and the user will be notified. The immediate payment value is not subject to the maximum value established by the user. If the receiver user has established a minimum value for the maximum value parameter, the PSP must inform this data to the payer user and only allow the configuration of the value from the established minimum. If the authorization establishes attempts to settle the payment after its due date, the payer PSP must inform the payer user of the existence of this condition and that it may result in the incidence of interest and fines on the next billing. Mandatory

92
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Receipt
Balance: R$ 1,000.00
Cancel Continue Finish
Name: Nadir da Silva
CPF: *** .222.333 -**
DEBTOR INFORMATION
Name: Store ABC
CNPJ: 15.436.940/0001-03
RECEIVER INFORMATION
PIX CONFIRMED
Value: R$19.90
Date/time: 10/01/2024 - 9:30:56
ID/Transaction: 975342678309753
I understand
The first payment was made, but the authorization for Pix Automatic was not completed. Contact the receiver to enable future payments. 9:30 Confirmation Balance: R$ 1,000.00 Cancel Continue Finish ADDITIONAL INFORMATION Payment object: Digital Library Next payments: weekly, on Wednesdays Value of recurring payments: R$ 17.90 First recurring payment: 17/01/2024 Immediate payment value: 19.90 Authorization term: 24 weeks Subscription number: 5282023 CPF: *** .222.333 -** Name: Nadir da Silva DEBTOR INFORMATION Name: Store ABC CNPJ: 15.436.940/0001-03 RECEIVER INFORMATION IMPORTANT! Check all information before making the first immediate payment and authorizing Pix Automatic. I understand Failed to complete the first payment. The authorization for Pix Automatic was not completed. 9:30 Authorization Receipt Balance: R$ 1,000.00 Share Save to cell Active Authorizations Name: Nadir da Silva CPF: *** .222.333 -** DEBTOR INFORMATION Name: Store ABC CNPJ: 15.436.940/0001-03 RECEIVER INFORMATION ADDITIONAL INFORMATION Value of recurring payments: R$ 17.90 Authorization term: 24 weeks Payment object: Digital Library ID: RN0375890220240105ej873k8il9a First recurring payment: 17/01/2024 Value: R$19.90 Date/time: 10/01/2024 - 9:30:56 ID/Transaction: 975342678309753 The first payment was made! Subscription number: 5282023 Next payments: weekly, on Wednesdays You will be notified when the recurring payments, subject to the availability of the Pix Automatic limit, are scheduled. By accessing Pix Automatic -> Active Authorizations, you can:

Disable the receipt of notifications or the
use of credit limit for payments by means of Pix Automatic;
Change the maximum payment value; or
Request the cancellation of this authorization at
any time.
AUTHORIZATION CONFIRMED
9:30
Confirmation
Balance: R$ 1,000.00
Cancel Continue Finish
ADDITIONAL INFORMATION
Payment object: Digital Library
Next payments: weekly, on
Wednesdays
Value of recurring payments: R$ 17.90
First recurring payment: 17/01/2024
Immediate payment value: R$ 19.90
Authorization term: 24 weeks
Subscription number: 5282023
CPF: *** .222.333 -**
Name: Nadir da Silva
DEBTOR INFORMATION
Name: Store ABC
CNPJ: 15.436.940/0001-03
RECEIVER INFORMATION
I authorize future recurring payments related to the Digital Library subscription. IMPORTANT! Check all information before making the first immediate payment and authorizing Pix Automatic. 23 22 21 20 Situations when authorization does not occur. 24 In journeys 1, 2, 3 and 4, after confirmation of the Pix Automatic authorization by the payer user, if the receiver PSP does not respond within the time established for the payer user experience in granting the Pix Automatic authorization, the payer PSP must immediately display a message to the payer user informing them that the authorization is being processed and that they will be notified of the result later. 23 If the immediate payment related to journey 3 is made, but an error occurs in the authorization processing, the following must be immediately presented to the user:
Receipt of the immediate payment. The message and the minimum fields that must
be presented to the user are represented in the screen to the side;
Message guiding the user to contact the receiver to
enable subsequent payments, due to the failure to complete the authorization. The ID/transaction refers to the "EndtoEndID" present in pacs.008. 22 If the immediate payment related to journey 3 does not materialize for any reason, the user must immediately receive a message with information that the authorization process was not completed. 21 As soon as the immediate payment and the Pix Automatic authorization of journey 3 are completed, the user must be immediately informed that:
The immediate payment was made;
Notifications will be sent when the next payments made by means of Pix
Automatic are scheduled;
The receipt of notifications of the schedules and/or the use of credit limit
for payments by means of Pix Automatic can be disabled;
The cancellation of the authorization can be done at any time;
The maximum value of payments can be changed (if established);
Payments are conditioned to the availability of balance and Pix Automatic limit.
The authorization ID information must be made available.
20
In journey 3, before the confirmation of the authorization, information must be present with emphasis that there will be an immediate payment (including the payment value), evidencing that the settlement of this payment is a necessary condition for the authorization process. There must be a field (check box) for the user to attest knowledge that they are authorizing future recurring payments for a certain product or service by means of Pix Automatic. Mandatory

93
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Active Authorizations
Balance: R$ 1,000.00
This authorization provides for payment attempts after the due date, when there is no sufficient account balance on the day contracted for the billing. Payments made after the due date may result in interest and fines added to the next payment. Authorization term: indefinite Next payments: monthly, on the 21st First payment: 21/01/2024 Customer code: 874354-7 Payment object: electricity bill, Acacia Streets ADDITIONAL INFORMATION CPF: *** .222.333 -** Name: Nadir da Silva DEBTOR INFORMATION CNPJ: 03.649.902/0001-23 Name: Energy S/A RECEIVER INFORMATION Maximum payment value: R$ 800.00 ID: RR8863984020240110z817zghe67d ? Cancel authorization 9:30 Active Authorizations Balance: R$ 1,000.00 School ABC João Antônio Silva Streaming Top Vip Plan Energy S/A Acacia Streets ACTIVE AUTHORIZATIONS 9:30 Pix Automatic Balance: R$ 1,000.00 ? ? ? ? ? ? ? ? Scheduled payments Authorization settings Authorization history Learn more Active Authorizations Pending Authorizations Scan QR code for authorization PIX AUTOMATIC My Pix Automatic limit ? 25 26 26 The query of active authorizations must display, at a minimum, the following information:

Receiver's name;
Receiver's CNPJ;
Debtor's name;
Debtor's CPF (masked)/CNPJ;
Authorization ID;
Payment object (if informed);
Identifier of the billing object (contract number, customer code, etc);
Scheduled date of the first recurring payment;
Frequency of future payments;
Authorization term or number of installments;
Expected value of payments (if fixed);
Maximum payment value (if defined by the payer).
The receiver user's name must be the Company's Trade Name, if it exists. If it does not exist, the name informed must be the Corporate Name/Legal Name. The authorization term can be for an indefinite period. If the authorization establishes attempts to settle the payment after its due date, the existence of this condition must be informed in the authorization data, as well as the possibility of incidence of interest and fines on the next billing, if the payment occurs after the due date. 25 Query, editing and cancellation functionality of active authorizations must be made available. Mandatory

94
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Cancel authorization
Balance: R$ 1,000.00
Maximum payment value: R$ 800.00
Authorization term: indefinite
Next payments: monthly, on the 21st
First payment: 21/01/2024
Customer code: 874354-7
Payment object: electricity bill,
Acacia Streets
ID: RR8863984020240110z817zghe67d
ADDITIONAL INFORMATION
CPF: *** .222.333 -**
Name: Nadir da Silva
DEBTOR INFORMATION
CNPJ: 03.649.902/0001-23
Name: Energy S/A
RECEIVER INFORMATION
CANCEL AUTHORIZATION
?
No Yes
If you cancel the authorization, the operation cannot be undone and the scheduled payments will be cancelled automatically, except for the one scheduled for today, if it exists. Are you sure you want to cancel? 9:30 Active Authorizations Balance: R$ 1,000.00 This authorization provides for payment attempts after the due date, when there is no sufficient account balance on the day contracted for the billing. Payments made after the due date may result in interest and fines added to the next payment. Maximum payment value: R$ 800.00 Authorization term: indefinite Next payments: monthly, on the 21st First payment: 21/01/2024 Customer code: 874354-7 Payment object: electricity bill, Acacia Streets ID: RR8863984020240110z817zghe67d ADDITIONAL INFORMATION CPF: *** .222.333 -** Name: Nadir da Silva DEBTOR INFORMATION CNPJ: 03.649.902/0001-23 Name: Energy S/A RECEIVER INFORMATION ? Cancel authorization 9:30 Active Authorizations Balance: R$ 1,000.00 Energy S/A Acacia Streets ACTIVE AUTHORIZATIONS Streaming Top Vip Plan School ABC João Antônio Silva 27 The user must be informed that, in case of cancellation of the Pix Automatic authorization, the operation cannot be undone and the scheduled payments related to this authorization will also be cancelled automatically, except those scheduled for the same day. Mandatory

95
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
Energy S/A
ACTIVE AUTHORIZATIONS
Streaming Top
School ABC
9:30
Active Authorizations
Balance: R$ 1,000.00
Energy S/A
Acacia Streets,
ACTIVE AUTHORIZATIONS
Streaming Top
Vip Plan
School ABC
João Antônio Silva
I understand
Your request was completed.
The new maximum value will apply to future payments that have not yet been scheduled. 9:30 Edit authorization parameters Balance: R$ 1,000.00 Cancel Finish ? ? ? R$ 400.00 Current maximum value: R$ 500.00 Use of credit limit
Schedule notifications
STREAMING TOP - VIP PLAN
9:30
Active Authorizations
Balance: R$ 1,000.00
Energy S/A
Acacia Streets
ACTIVE AUTHORIZATIONS
Streaming Top
Vip Plan
School ABC
João Antônio Silva
9:30
Pix Automatic
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Scheduled payments
Authorization settings
Authorization history
Learn more
Active Authorizations
Pending Authorizations
Scan QR code for authorization
PIX AUTOMATIC
My Pix Automatic limit ?
28
30
31
If the maximum value is changed to a value lower than that of a payment already scheduled, it is optional for the payer PSP to inform the fact to the payer user and offer the possibility of cancelling the scheduled payment. 30 If the payer user changes the maximum value or the settings related to the receipt of schedule notifications or the use of credit line, they must be immediately informed that the change was completed successfully. 29 The following standard must be adopted for the authorization parameters, before any eventual editing made by the user:
-Maximum value: disabled
-Receipt of schedule notifications: enabled -Credit line use (if offered by the PSP): enabled 28 For each active authorization, the user can edit the maximum value parameters (in variable value authorizations), credit line use (if offered by the PSP) and receipt of schedule notifications, activating or deactivating each parameter. In the case of the maximum value, if the user wishes to edit it, they must fill in the maximum value in the specific field. If the receiver user has established a minimum value for the maximum value parameter, the PSP must inform this data to the payer user and only allow the configuration of the value from the established minimum. The user must be informed that the new maximum value will apply to future schedules, not applying to schedules already made. Recommended Mandatory

96
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
School ABC
Balance: R$ 1,000.00
Active Authorizations
Cancel Continue
Cancel the schedule
Payment object: João Antônio Slva
Contract number: 2023256
Payment date: 01/08/2023
Value: R$ 1,790.00
ADDITIONAL INFORMATION
CPF: *** .222.333 -**
Name: Nadir da Silva
DEBTOR INFORMATION
Name: School ABC
CNPJ: 03.649.902/0001-23
RECEIVER INFORMATION
9:30
Scheduled payments via Pix Automatic
Balance: R$ 1,000.00
Energy S/A - Acacia Streets
Payment date: 15/07/2023
SCHEDULED PAYMENTS
Streaming Top - Vip Plan
Payment date: 30/07/2023
School ABC - João Antônio Silva
Payment date: 01/08/2023
9:30
Pix Automatic
Balance: R$ 1,000.00
?
?
?
?
?
?
?
?
Scheduled payments
Authorization settings
Authorization history
Learn more
Active Authorizations
Pending Authorizations
Scan QR code for authorization
PIX AUTOMATIC
My Pix Automatic limit ?
32
34
33
34
The cancellation of a scheduled payment can be made until 11:59 PM on the day before the scheduled payment date. 33 The query of the scheduled payment must display, at a minimum, the following information:

Receiver's name;
Receiver's CNPJ;
Debtor's name;
Debtor's CPF (masked)/CNPJ;
Payment object (if informed);
Identifier of the billing object (contract number, customer code, etc);
Scheduled payment date;
Payment value;
"Description", with additional information about the payment (whenever it is
filled).
The receiver user's name must be the Company's Trade Name, if it exists. If it does not exist, the name informed must be the Corporate Name/Legal Name. The "Description" refers to "informacoesEntreUsuarios" of pain.013, a field used for sending information from the receiver user to the payer user (example: data about interest and fines added to the payment). The "Description" field must not contain HTML tags. The payer user's application must display the characters of this field literally and, therefore, must not render links or any dynamic content. 32 Query and cancellation functionality of scheduled payments must be made available to the payer user. Mandatory

97
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Authorization History
Balance:R$ 1,000.00
ID: RR8362046920231121jd8jj39slw
Status: Cancelled by receiver
Authorization date: 21/11/2023
Cancellation date: 05/01/2024
Receiver: Gym Malhação
Status: In process
Receiver: Telephony S/A
ID: RN7385052920180812j38dm93k3l0
Status: Expired
Authorization date: 25/01/2023
End of validity date: 31/12/2023
Receiver: School ABC
Confirmation deadline: 25/02/2024
Status: Pending
Authorization term: until 17/12/2024
Authorization date: 17/12/2023
Status: Active
ID: RR8863984020240110z817zghe67d
Receiver: Energy S/A
AUTHORIZATION HISTORY
If you have pending authorizations, access Pix Automatic -> Pending Authorizations, to check the information and confirm the Pix Automatic authorization. 9:30 Pix Automatic Balance:R$ 1,000.00 ? ? ? ? ? ? ? ? Authorization history Learn more Scan QR code for authorization Authorization settings Scheduled payments Active Authorizations Pending Authorizations PIX AUTOMATIC My Pix Automatic limit ? 36 35 Sorting (by date, receiver, status) and filter functionalities by status in the query of the authorization history may be offered. 35 Query functionality of the history of all authorizations must be made available to the payer user, with, at a minimum, the following information:

Receiver's name;
Status: pending, active, expired, cancelled and in process;
Authorization date, except in the case of pending authorizations;
In pending ones: date of expiration of the deadline for confirmation of the authorization;
In active ones: authorization term (inform if the term is indefinite);
In expired ones: end of validity date;
In cancelled ones: date of cancellation, indicating whether the authorization was cancelled by the
receiver or by the payer. The cancellation information by the receiver's initiative must be available in a clear and accessible manner to the payer user. The in-process status refers to authorizations confirmed by the payer user and that are still in the process of completion. In cases where the payer user has Pix Automatic authorizations granted directly to their PSP, as well as consents effected through a PSI, the query functionality of the history must encompass all these authorizations, regardless of the channel used for their granting, in order to guarantee a unified experience for the payer user. The nomenclature used to indicate the status of the authorizations must be standardized, avoiding the use of distinct terms to represent equivalent situations of authorizations and consents. Recommended Mandatory

98
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Maximum Value
Balance: R$ 1,000.00
Cancel Finish
?
Enter the maximum value starting from R$ 300.00 Enter the maximum debit value Energy S/A - Acacias Street, 26 Maximum Value: R$ 500.00 MAXIMUM VALUE Streaming Top - Vip Plan Maximum Value: R$ 50.00 ABC School João Antônio Silva When activating the maximum value, you must fill in the field with the maximum value of each recurring payment via Pix Automatic. If the recurring payment value is higher than the defined maximum value, the payment will not be scheduled and you will be notified. 9:30 Use of Credit Limit Balance: R$ 1,000.00 Cancel Finish ? Energy S/A Acacias Street, 26 USE OF CREDIT LIMIT Streaming Top Vip Plan ABC School João Antônio Silva By activating the use of the credit limit, you are agreeing that any available balance of contracted credit limit will be used for payments via Pix Automatic. 9:30 Authorization Settings Balance: R$ 1,000.00 ? ? ? Maximum Value AUTHORIZATION SETTINGS Use of Credit Limit Scheduling Notifications 9:30 Pix Automatic Balance: R$ 1,000.00 ? ? ? ? ? ? ? ? Scheduled Payments Authorization Settings Authorization History Learn More Active Authorizations Pending Authorizations Scan QR code for authorization PIX AUTOMATIC My Pix Automatic Limit ? 37 38 39 39 When selecting the “maximum value” parameter, the user can activate or deactivate this parameter and edit its value for all variable value authorizations in a single journey. It must be stated that if the value of a payment is higher than the defined maximum value, the payment will not be scheduled and the user will be notified. If the receiving user has established a minimum value for the maximum value parameter, the PSP must inform this data to the payer user and only allow the configuration of the value starting from the established minimum. The user must be informed that the new maximum value will apply to future schedules, not applying to schedules already made. If the maximum value is changed to a value lower than that of an already scheduled payment, the payer PSP may inform the user of the fact and offer the possibility of canceling the scheduled payment. 38 When selecting the parameters receiving scheduling notifications or use of credit limit, the user can activate or deactivate this parameter for all authorizations in a single journey (single screen). 37 Functionality for consulting and managing parameters of active authorizations may be made available to the payer user: maximum value, use of credit line and receiving scheduling notifications. Recommended

99
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user and PSP of the receiving user 9:30 Statement Balance: R$ 1,000.00 Pix Credit Card Account current All Search Value: R$ 100.00 Date/Time: 11/08/2023 at 19:01:34 Store GHJK Pix Withdrawal Value debited: R$ 250.00 Date/Time: 14/08/2023 at 13:46:12 João da Silva Transfer via TED Value: R$ 17.90 Date/Time: 15/08/2023 at 10:31:42 Energy S/A Pix Automatic LAST ENTRIES Share Save on cell Statement / Return 9:30 Pix Balance: R$ 1,000.00 Payment Object: Digital Library ADDITIONAL INFORMATION Subscription Number: 874354744445 Name: Fernanda Costa CPF/CNPJ: * .777.888 -* PAYER INFORMATION PSP: PSP ABCD Name: Nadir da Silva CPF/CNPJ: * .993.555 -* DEBTOR INFORMATION PSP: PSP XYZ Name: Store ABC PSP: XYWZ CNPJ: 15.436.940/0001-03 RECEIVER INFORMATION ID/Transaction: 841839083003289 Date/time: 15/08/2023 - 10:31:42 Value/final: R$17.90 PIX AUTOMATIC CONFIRMED 40 40 42 42 The debtor data (name and CPF - masked or not - or CNPJ) can be included in the recurring payment receipt for payer and receiving users. 41 The immediate payment receipt of journey 3 of authorization and the immediate payment receipt or the collection with maturity of journey 4 of authorization must not be identified with the Pix Automatic nomenclature and must follow the minimum requirements set forth in the chapters “Payment through static QR Code” and “Immediate payment or with maturity through dynamic QR Code”, depending on the type of collection linked to the QR Code. 40 Make available a recurring payment receipt for payer and receiving users during the period established in the current regulation, containing, at minimum:

Identification that the transaction is a Pix Automatic;
Name and CNPJ of the receiver;
Name of the PSP of the receiver;
Name and CPF (masked or not)/CNPJ of the payer;
Object; of the payment (if informed)
Identifier of the collection object (contract number, customer code, etc);
ID; of the transaction ("EndtoEndID" present in the pacs.008)
Date and time/minute/second (Brasília time) of settlement;
Value.
When the transaction involves a PSI, the name of the PSI must appear on the receipt. The message and the minimum fields that must be presented to the user are represented on the screen to the side. Recommended Mandatory

100
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Confirmation
Balance: R$ 1,000.00
Cancel Continue Finish
Payment Object: Digital Library
Expected date of future payments: 15
Expected value of future payments: R$ 17.90 Date of first payment: 10/07/2023 Authorization Period: Indeterminate Subscription Number: 5282023 ADDITIONAL INFORMATION CPF: * .222.333 -* Name: Nadir da Silva DEBTOR INFORMATION Name: Store ABC CNPJ: 15.436.940/0001-03 RECEIVER INFORMATION IMPORTANT! Check all information before making the first immediate payment and authorize Pix Automatic. Value of first payment: R$ 19.90 I Understand Processing error. It was not possible to make the payment and confirm the authorization of Pix Automatic. Try again. 9:30 Confirmation Balance: R$ 1,000.00 Cancel Continue Finish Maximum value of payments: R$ 800.00 Authorization Period: indeterminate Next payments: monthly, day 21 First payment: 21/01/2024 Customer Code: 874354-7 Payment Object: electricity bill, Acacias Street ADDITIONAL INFORMATION CPF: * .222.333 -* Name: Nadir da Silva DEBTOR INFORMATION Name: Energy S/A CNPJ: 03.649.902/0001-23 RECEIVER INFORMATION IMPORTANT! Check all information before authorizing Pix Automatic. I Understand Failed to confirm your Pix Automatic authorization. Try again. 43 Error messages must be specific and clear to the user. Mandatory messages must show that the transaction was not performed and specify the problem occurred in cases of non-processing of the authorization and failure in the settlement of the first immediate payment:
Examples:

Failed to confirm your Pix Automatic authorization. Try again.
Processing error. It was not possible to make the payment and confirm the
authorization of Pix Automatic. Try again.
First payment made, but there was a failure in processing your
authorization. Contact the receiver to enable future payments.
Mandatory

101
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Camera Email PSP XYZ
20
Calendar
Your daily limit for Pix Automatic has been exceeded, so the payment to Energy S/A, in the amount of R$ 478.90, was not made. You can request a higher limit and, if approved, settlement may occur, until 21:00, when we make a new payment attempt PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar The payment to Energy S/A via Pix Automatic, in the amount of R$ 478.90, was not made due to lack of balance. New attempts may be made in the coming days. You will be notified of the result of these attempts. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar The payment to Energy S/A via Pix Automatic, in the amount of R$ 478.90, was not made due to lack of balance. A final attempt will be made today, starting from 20:00, and you will be notified of the result. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar Pix Automatic scheduled for Energy S/A, in the amount of R$ 478.90, to be paid on 30/06/2023. To cancel the
schedule, access Pix Automatic -> Scheduled
Payments, until 29/06/2023, and make the cancellation.
PSP XYZ
46 45
44 47
47
If the scheduled payment is not made due to insufficiency of the daily limit available for Pix Automatic transactions, the PSP must send notification immediately after the end of the first settlement window, informing that the transaction was not made due to this reason. It must be advised that, if the user requests an increase in the limit and the request is approved, settlement may occur in a new attempt, until the deadline of the second mandatory settlement window, or over the following days, in cases where the authorization establishes collection attempts after the due date. 46 In cases where the authorization establishes collection attempts after the due date, if the settlement of the payment order is not made due to insufficiency of balance or transactional limit after the last attempt on the day scheduled for settlement, the PSP must send notification to the payer user, informing that the transaction was not made due to this reason and that new attempts may be made over the following days. 45 If the scheduled payment is not made due to insufficiency of balance, the PSP must send notification immediately after the end of the first settlement window, informing that the transaction was not made due to this reason and that a new attempt will be made on the same day. It must also indicate the time, within the second mandatory settlement window, after which the final attempt will be made, so as to allow the user to replenish the balance by that time. 44 If the payer user has not disabled the receipt of scheduling notifications, the payer PSP must send notification to the user immediately after scheduling with the following information:

Scheduled Pix Automatic transaction;
Name; of the receiver
Value;
Payment date.
Mandatory

102
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Camera Email PSP XYZ
20
Calendar
Energy S/A canceled Pix Automatic for the electricity bill, Acacias Street. The scheduled payments will be canceled, except those scheduled for today. New schedules will not be made. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar Energy S/A canceled the scheduled Pix Automatic for 30/06/2023, in the amount of R$ 478.90. We suggest contacting them to seek information about the payment. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar Pix Automatic successfully paid to Energy S/A, on 30/06/2023, in the amount of R$ 478.90. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar A final payment attempt was made to Energy S/A via Pix Automatic, in the amount of R$ 478.90, but it was not possible to execute the payment due to lack of balance. Please seek other means to make the payment. PSP XYZ 50 48 52 51 52 The PSP must send notification to the payer user as soon as there is cancellation of the recurrence by the receiving user, containing, at minimum, the following information:

Cancellation; of Pix Automatic at the request of the receiver
Name of the receiver;
Payment object (if informed);
Scheduled debts that will be canceled (if any), making it clear that the
schedules whose settlement is scheduled for the day of sending the notification will not be canceled;
Suspension of new schedules.
51
The PSP must send notification to the user, if a schedule has been successfully canceled by the initiative of the receiver, provided that the user was previously informed about the schedule via notification or the “Scheduled Payments” option, in the “Pix Automatic” menu, or in “Future Entries”. The notification must contain information about the date of the scheduled payment, value and name of the receiver. 50 The PSP must send notification to the user whenever a payment is made via Pix Automatic, with information that it is a transaction within the scope of Pix Automatic, payment date, value and name of the receiver. When settlement occurs between zero hours and six hours in the morning, the notification must be sent, preferably, after this time. 49 If the scheduled payment is not made due to operational failure after sending the payment order for settlement, the PSP must not send notification to the user, except if the failure occurs in the final settlement attempt. In this case, notification must be sent informing that it was not possible to make the payment via Pix Automatic due to operational failure and that he must make the payment by other means. 48 After the final settlement attempt made by the PSP, on the due date or on the following days (depending on what was previously agreed), if there is still insufficiency of balance or daily limit available for Pix Automatic transactions, notification must be sent to the payer user informing that it was not possible to make the payment via Pix Automatic and that he must make the payment by other means. Mandatory

103
Version 7.3 Pix Automatic
RECIPIENT: PSP of the payer user
9:30
Camera Email PSP XYZ
20
Calendar
The Pix Automatic authorization for Energy S/A was confirmed. Access the Authorization History to consult the authorization data. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar Energy S/A canceled the pending Pix Automatic authorization request, due to error in the recurrence data. PSP XYZ 9:30 Camera Email PSP XYZ 20 Calendar The schedule of the value of R$ 600.50 via Pix Automatic for Energy S/A was not made, because it exceeds the maximum value established. Contact the supplier and change the maximum value to enable the payment on the scheduled date. PSP XYZ 58 55 54 53 58 In cases where a schedule was not made due to exceeding the maximum value established for the authorization, the payer PSP may send notification to the user payer informing about the possibility of changing the maximum value and the need to contact the receiver, in order to try to enable the payment in the same cycle. Recommended 57 The method of sending notifications is at the free choice of the PSP. If the notification is via push, part of the information, at the choice of the PSP, may be detailed when the user clicks on the notification. 56 The name of the receiving user in notifications must be the Business Name (Trade Name) of the company, if it exists. If it does not exist, the name informed must be the Corporate Name/Legal Name. 55 The payer user must receive notification of deletion of pending authorization of confirmation regarding journey 1, containing, at minimum, the following data:

Name of the receiver and information that the deletion was at his request;
Motivation for deletion:
error in the recurrence data;
payer user confirmed the recurrence using another means.
54
In the situation where the activation of an authorization confirmed by the user remained pending due to the lack of response from the receiving PSP within the time limit required by regulation, the payer PSP must send notification to the user informing him of the result of the processing of the authorization, including in cases where the maximum time limit has been exceeded that the payer PSP must wait for the conclusion of the authorization process by the receiving PSP. 53 The payer user must receive notification of non-scheduling of the debit when the value is different from that established in the authorization, in the case of fixed value, and when the value exceeds the maximum value established by the user in the authorization. Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
16
Functionality that allows payer users to register, through the application itself, the contestation of Pix transactions resulting from scam, fraud or crime, as well as irregularities in Pix Automatic transactions, and to consult requests already made, within the scope of the Special Refund Mechanism (MED). Self-Service MED

105
Version 7.3 Self-Service MED
RECIPIENT: PSP of the payer user
9:30
Pix
Pix with
Key / Manual
Pix Copy and Paste
Pix with
QR Code Receive Pix
R$10.00
Value Payment via Key
Roberto da Silva
R$30.00
Value
João da Silva
LAST TRANSACTIONS
Cell
CPF
Key
Random
Email
Balance: R$ 1,000.00
Nadir da Silva
Complain here
My
Pix Limits
Pix
Automatic
Statement /
Return
For other types of complaint, contact our
Customer Service Center
If your complaint is not resolved, you can register a complaint on the site of the Central Bank of Brazil. Customer Service MED To contest Pix in cases of scam or unjustified charge in Pix Automatic, click on MED OR 9:30 Pix Pix with Key / Manual Pix Copy and Paste Pix with QR Code Receive Pix R$10.00 Value Payment via Key Roberto da Silva R$30.00 Value João da Silva LAST TRANSACTIONS Cell CPF Key Random Email Balance: R$ 1,000.00 Nadir da Silva Pix Locations Withdrawal / Change Complain here Contest Pix MED Pix Scheduled 01 There must be functionality, in the Pix environment, for the user to contest a Pix or Pix Automatic transaction in cases of scam, fraud or crime or a Pix Automatic transaction in case of operational failure of the payer PSP. The functionality must also provide consultation to registered contestations. The shortcut made available in the Pix environment to access the PSP’s customer service channel for handling complaints must also enable access to this contestation functionality. Mandatory

106
Version 7.3 Self-Service MED
RECIPIENT: PSP of the payer user
9:30
Contest Pix / About MED
Balance: R$ 1,000.00
MED
See how contestation works in cases of scam, fraud or crime:

Your request must be made within 80 days of
the transaction being made
Sending supplementary documentation helps
to prove the fraud
Within 11 days, if your request is
considered valid and there are resources in the receiver's account or in other accounts involved in the fraud, you will receive your money back Were you a victim of a Pix scam or had an unjustified Pix Automatic debit in your account? Activate the MED as soon as possible! Cancel Continue 9:30 MED Balance: R$ 1,000.00 ? Consult contestations ? Contest Pix MED The Special Refund Mechanism (MED) of Pix transactions can be activated if you have been a victim of a scam or received an unjustified charge of Pix Automatic. Only Pix transactions that occurred less than 80 days ago can be contested. Attention, the MED cannot be used for commercial disagreements between buyer and seller, transfers to wrong people or regret of the payer in making the Pix. 04 02 03 When contesting a Pix, the user must be informed, at least on the first access, about the main rules of the MED, addressing, at minimum, in which cases it can be activated, which situations are not covered, the steps of the process and the maximum time limit to request the refund.

Examples:

Were you a victim of a Pix scam or had an unjustified Pix Automatic debit in your account? Activate the MED as soon as possible!

Attention, the MED cannot be used for commercial disagreements that do not can be characterized as seller fraud (e.g. products delivered late or that did not correspond exactly to the buyer's expectation), transfers to wrong people or regret of the payer in making the Pix. The MED is also not applicable to Pix transactions for the purpose of withdrawal and change.

See how contestation works in cases of scam, fraud or crime:

Your request must be made within 80 days of the transaction being made;
Sending supplementary documentation helps to prove the fraud;
Within 11 days, if your request is considered valid and there are resources in the
receiver's account or in other accounts involved in the fraud, you will receive your money back.

See how contestation works in case of unjustified charge in Pix Automatic:

Your request can be made within 80 days of the transaction being made;
If there was any error by your bank in the charge, you will have the value returned
within 24 hours;
If you authorized a Pix Automatic, but discovered that the receiver is a scammer, you can also activate the MED. In this case, the rules for refunding your Pix are the same as those for other contestations due to scam, fraud or crime.
04
03
For each item of the menu of the transaction contestation functionality, clarification information must be provided that addresses, at minimum, the following points:

Registration of contestation of Pix transaction: contestation of values regarding
transactions made in the last 80 days, in situations where the user was a victim of scam, fraud or crime, and in case of irregularities in Pix Automatic transactions;
Consultation of contestation records: verification of the progress and maximum time limit for
the PSP to conclude the analysis of the Pix transaction contestation, access to the contact channel to send supplementary information about the fraud, if made available by the PSP, and cancellation of registered requests. 02 The menu of the transaction contestation functionality must provide options to register a Pix contestation and to consult records of contestations. Mandatory

107
Version 7.3 Self-Service MED
RECIPIENT: Payer's PSP
9:30
Dispute Pix
Balance: R$ 1,000.00
I am requesting the return of this Pix because I suffered the following scam, fraud, or crime:
ANSWER
Other cases where I was a victim of fraud
A fraudster used my password to transfer funds from my account, without my authorization I was threatened or had my freedom restricted to be forced to make a transaction Another person transferred funds from my account, without my knowledge I was deceived by a scammer and made a transaction Send documents Finish Dispute 002356 registered 08/16/2025, 12:17 The recipient's institution will be notified immediately of the suspected fraud. Partial or total return can only occur if the suspected fraud is deemed valid and there is a balance in the recipient's account or in other accounts involved in the fraud. Within 7 days, we will analyze your report and inform you whether the dispute was accepted or not. Send a report of the fraud or documents, such as a police report, that may help in the analysis of your dispute. You can do this now by clicking below or send later by accessing Dispute Pix -> Consult disputes. 9:30 Pix Balance: R$ 1,000.00 Dispute Pix I am requesting the return of this Pix because:
ANSWER
Another type of scam
A fraudster used my password to transfer funds from my account, without my authorization I was threatened or had my freedom restricted to be forced to make a transaction Another person transferred funds from my account, without access to my password and without my knowledge I was deceived by a scammer and made a transaction Cancel Send 9:30 Pix Statement / Transaction Balance: R$ 1,000.00 Dispute PSP: PSP ABCD CPF/CNPJ: *** .777.888 -** Transaction ID: 885544774112258 Debited amount: R$ 10,000.00 Date/Time: 08/15/2025 at 21:34:05 João da Silva Payment - Pix via Key TRANSACTION Share Save to mobile Statement 9:30 Pix Statement Balance: R$ 1,000.00 Receivals with or without return Pix via QR Code Pix via Key or Manual All Search Receival - Pix via QR Code Date/Time: 08/01/2025 at 21:34:05 Roberto da Silva Amount received: R$ 50.00 Debited amount: R$ 400.00 Date/Time: 08/01/2025 at 21:34:05 Energia S/A Automatic Pix Debited amount: R$ 10,000.00 Date/Time: 08/15/2025 at 21:34:05 To register the complaint, select the desired transaction and click the "dispute" button João da Silva Pix via Key LAST TRANSACTIONS 08 07 07 05 10 If the user selects a response that specifically identifies the scam, fraud or crime, the PSP must register the request and immediately open the value recovery in the DICT. The demand registration notification must address, at minimum, the following information:

Request registration protocol number, with date and time of
registration;
Maximum deadline for the PSP's response to the user regarding the acceptance or refusal of
the dispute;
Necessity of having a balance in the recipient's account of the root transaction or in
other accounts involved in the suspected fraud to enable the partial or total return of the value;
Information that the recipient's institution will be notified of the suspected fraud.

08
When selecting in the statement the dispute of a Pix transaction made within 80 days, the user must be asked about what type of scam, fraud or crime they suffered. The answers must be related to the classification adopted in the Operational Manual of the Transactional Account Identifiers Directory (DICT) for the field "cause of fraud" (SituationType) contained in a value recovery. All causes of fraud from the DICT must be included in the list of answers provided to the user. In the example, the user must choose a single answer from the five available:

I was deceived by a scammer and made a transaction; (SituationType: scam)
Another person transferred funds from my account, without access to my password and without
my knowledge; (SituationType: account_takeover)
I was threatened or had my freedom restricted to be forced to make a
transaction; (SituationType: coercion)
A fraudster used my password to transfer funds from my account, without my
authorization; (SituationType: fraudulent_access)
Another type of scam. (SituationType: other)
At the PSP's discretion, the same classification from the DICT Operational Manual for the field "cause of fraud" (SituationType) can be related to more than one answer option about the type of scam, fraud or crime the user was a victim of. The dispute of an Automatic Pix transaction is treated in item 14 of this chapter. 07 If the user tries to register a dispute for a Pix or Automatic Pix transaction made more than 80 days ago, the PSP must inform them that the action cannot be performed within the scope of the MED due to the exceeded time limit. 06 05 When activating the Pix transaction dispute function for scam, fraud or crime or irregularities in Automatic Pix transactions, the user must be directed to the account statement or Pix statement (if available) to select the transaction subject to the dispute. The option to register the dispute must also be made available to the user by accessing the transaction directly, through the account statement or Pix statement (if available), with the rules of the mechanism informed, at least on the first access. Mandatory Mandatory When disputing a Pix transaction, if the user answers that they suffered an unspecified type of fraud (SituationType: other), the PSP must request a report from the user describing the fraud, with up to 2000 characters. The PSP must register the request and immediately open the value recovery in the DICT, proceeding to analyze the report to verify if the case is covered by the MED at a later moment.

The demand registration notification must address, at minimum, the following information:

Request registration protocol number, with date and time of registration;

Maximum deadline for the PSP's response to the user regarding the acceptance or refusal of the dispute;

Necessity of having a balance in the recipient's account of the root transaction or in other accounts involved in the suspected fraud to enable the partial or total return of the value;

Information that the recipient's institution will be notified of the suspected fraud.

09
Recommended
The PSP may provide a field for fraud report in cases where the user selects one of the answers that specifically identify the scam, fraud or crime, provided that after opening the dispute and registering the respective value recovery. The request for the fraud report should occur preferably before the end of the self-service journey, immediately after registering the value recovery, in order to ensure the timeliness of information collection. 10 After confirming to the user the opening of the dispute and registering the respective value recovery, the PSP may request additional information to support the analysis of the suspected fraud or provide a contact channel, in a format of its discretion, for subsequent submission. 11 ANSWER I am requesting the return of this Pix because:
I was deceived by a scammer and made a transaction Another person transferred funds from my account, without access to my password and without my knowledge I was threatened or had my freedom restricted to be forced to make a transaction A fraudster used my password to transfer funds from my account, without my authorization Another type of scam 09 Balance:
9:30
R$ 1,000.00
Cancel Continue
Dispute Pix
Balance:
9:30
TO COMPLETE
Write a brief report about the fraud:
Small description of the fraud
0 of 2,000 characters
09
R$ 1,000.00
Cancel Send
Dispute Pix
09
ANSWER
Choose the best alternative that applies to your case:
Commercial disagreement between buyer and seller 11 Finish Cancel Send documents Continue 108 Balance:
9:30
Dispute 002356 registered

08/16/2025, 09:02
Transfer made to the wrong person or company Regret in making the Pix The recipient's institution will be notified immediately of the suspected fraud.

Partial or total return can only occur if the suspected fraud is deemed valid and there is a balance in the recipient's account or in other accounts involved in the fraud.

Within 7 days, we will analyze your report and inform you whether the dispute was accepted or not.

Send documents, such as a police report, that may help in the analysis of your dispute. You can do this now by clicking below or send later by accessing Dispute Pix -> Consult disputes. Other fraud cases R$ 1,000.00 Dispute Pix

109
Version 7.3 Self-Service MED
RECIPIENT: Payer's PSP
9:30
Pix
Balance: R$ 1,000.00
Dispute Pix
Choose the best alternative that applies to your case:
ANSWER
Other fraud cases
Regret in making the Pix
Transfer made to the wrong person or company Commercial disagreement between buyer and seller I understand The MED cannot be activated for the case selected. You can request the return of the value from the recipient. 9:30 Pix Balance: R$ 1,000.00 Dispute Pix Choose the best alternative that applies to your case:
ANSWER
Other fraud cases
Regret in making the Pix
Transfer made to the wrong person or company Commercial disagreement between buyer and seller Cancel Continue 9:30 Pix Balance: R$ 1,000.00 Dispute Pix I am requesting the return of this Pix because:
ANSWER
Another situation
A fraudster used my password to transfer funds from my account, without my authorization I was threatened or had my freedom restricted to be forced to make a transaction Another person transferred funds from my account, without access to my password and without my knowledge I was deceived by a scammer and made a transaction Cancel Continue 12 13 12 If the user selects one of the situations not covered by the MED, the impossibility of concluding the dispute registration must be communicated and informed that for these cases, one can try to request the return directly from the recipient user. 13 Additionally, the PSP may offer a response option that does not specify the type of situation to be disputed, for example "another situation" or "other case not mentioned before". If the user selects this option, they may be asked again about the reason for the dispute, with answer options for situations not covered by the MED. There must also be a response option for other types of fraud (SituationType: other), if it has not been offered in a previous stage of the journey. The inclusion of situations outside the scope of the MED serves as a control to prevent the registration of transactions that are not eligible for return via MED. Examples:

Commercial disagreement between buyer and seller;
Transfer made to the wrong person or company;
Regret in making the Pix.
12
Recommended
Mandatory

110
Version 7.3 Self-Service MED
RECIPIENT: Payer's PSP
9:30
Pix
Balance: R$ 1,000.00
Dispute Pix
I am requesting the return of this
Automatic Pix because:
ANSWER
Another situation involving undue charge in Automatic Pix The charge made is different from the authorization I made (amount, periodicity, payment date) I already canceled the authorization for this charge I did not authorize Automatic Pix for this charge I authorized a payment via Automatic Pix, but discovered that the recipient was a scammer Cancel Send I understand Dispute registered 08/15/2025, 11:50 We will evaluate your request and if the undue charge is confirmed, the value will be returned within 24 hours. 9:30 Pix Balance: R$ 1,000.00 Dispute Pix I am requesting the return of this Automatic Pix because:
ANSWER
Another situation involving undue charge in Automatic Pix The charge made is different from the authorization I made (amount, periodicity, payment date) I already canceled the authorization for this charge I did not authorize Automatic Pix for this charge I authorized a payment via Automatic Pix, but discovered that the recipient was a scammer Cancel Send 9:30 Pix Statement / Transaction Balance: R$ 1,000.00 Dispute PSP: XYWZ CPF/CNPJ: 15.436.940/0001-03 Transaction ID: 841839083003289 Debited amount: R$ 100.00 Date/Time: 08/01/2025 at 21:34:05 Store ABC CPF/CNPJ: *** .993.555 -** Nadir da Silva Automatic Pix TRANSACTION DEBTOR INFORMATION RECIPIENT INFORMATION Payment object: Digital Library Subscription number: 874354744445 ADDITIONAL INFORMATION Share Save to mobile Statement 9:30 Pix Statement Balance: R$ 1,000.00 Receivals with or without return Pix via QR Code Pix via Key or Manual All Search Receival - Pix via QR Code Date/Time: 08/01/2025 at 21:34:05 Roberto da Silva Amount received: R$ 50.00 Debited amount: R$ 100.00 Date/Time: 08/01/2025 at 21:34:05 Store ABC Automatic Pix Debited amount: R$ 10,000.00 Date/Time: 08/15/2025 at 21:34:05 To register the complaint, select the desired transaction and click the "dispute" button João da Silva Pix via Key LAST TRANSACTIONS 15 14 14 16 16 When selecting the reason for disputing an Automatic Pix, if the user answers that there is another unspecified situation involving undue charge in Automatic Pix, the PSP may request a report from the user describing the occurrence, with up to 2000 characters. If the user selects one of the answers related to an operational failure in sending the payment order for the Automatic Pix, the PSP must register the request, addressing, at minimum, the following information:

Request registration protocol number, with date and time of
registration;
PSP response deadline to the user regarding the evaluation of the request, which must be
no more than 24h;
Indication that, if it is verified that an undue charge indeed occurred,
the value will be reimbursed to the user within the response deadline established in the previous item. 15 When selecting in the statement the dispute of an Automatic Pix transaction, the user must be asked about the reason. If the request was motivated by errors of the payer's PSP in sending a payment order for the Automatic Pix, which include inconsistency between the payment instruction sent by the recipient's PSP and the parameters of the authorization granted by the payer user, non-existence of a valid authorization granted by the payer user or any other operational failure of the payer PSP (for example, sending a payment order after the scheduling has been canceled), the answers must specify clearly and objectively the problem that occurred. It is at the PSP's discretion to define the number of options related to the payer PSP's error, as long as they cover all situations eligible for return provided in the Pix regulation.

There must also be at least one response option provided for cases of scam in an Automatic Pix authorization, which must be related to the classification adopted in the Operational Manual of the Transactional Account Identifiers Directory (DICT) for the field "cause of fraud" (SituationType) of type "scam" contained in a value recovery.

In the example below, the user must choose a single answer from the five available:

I authorized a payment via Automatic Pix, but discovered that the recipient was a
scammer; (SituationType: scam);
I did not authorize Automatic Pix for this charge;
I already canceled the authorization for this charge;
The charge made is different from the authorization I made (amount, periodicity, payment
date);
Another situation involving undue charge in Automatic Pix.
14
Mandatory
Recommended

111
Version 7.3 Self-Service MED
RECIPIENT: Payer's PSP
9:30
Pix
Balance: R$ 1,000.00
Dispute Pix
I am requesting the return of this
Automatic Pix because:
ANSWER
Another situation involving undue charge in Automatic Pix The charge made is different from the authorization I made (amount, periodicity, payment date) I already canceled the authorization for this charge I did not authorize Automatic Pix for this charge I authorized a payment via Automatic Pix, but discovered that the recipient was a scammer Cancel Send Send documents Finish Dispute 004386 registered 08/02/2025, 13:58 The recipient's institution will be notified immediately of the suspected fraud. Partial or total return can only occur if the suspected fraud is deemed valid and there is a balance in the recipient's account or in other accounts involved in the fraud. Within 7 days, we will analyze your report and inform you whether the dispute was accepted or not. Send a report of the fraud or documents, such as a police report, that may help in the analysis of your dispute. You can do this now by clicking below or send later by accessing Dispute Pix -> Consult disputes. 9:30 Pix Balance: R$ 1,000.00 Dispute Pix I am requesting the return of this Automatic Pix because:
ANSWER
Another situation involving undue charge in Automatic Pix The charge made is different from the authorization I made (amount, periodicity, payment date) I already canceled the authorization for this charge I did not authorize Automatic Pix for this charge I authorized a payment via Automatic Pix, but discovered that the recipient was a scammer Cancel Send 9:30 Pix Statement / Transaction Balance: R$ 1,000.00 Dispute PSP: XYWZ CPF/CNPJ: 15.436.940/0001-03 Transaction ID: 841839083003289 Debited amount: R$ 100.00 Date/Time: 08/01/2025 at 21:34:05 Store ABC CPF/CNPJ: *** .993.555 -** Nadir da Silva Automatic Pix TRANSACTION DEBTOR INFORMATION RECIPIENT INFORMATION Payment object: Digital Library Subscription number: 874354744445 ADDITIONAL INFORMATION Share Save to mobile Statement 9:30 Pix Statement Balance: R$ 1,000.00 Receivals with or without return Pix via QR Code Pix via Key or Manual All Search Receival - Pix via QR Code Date/Time: 08/01/2025 at 21:34:05 Roberto da Silva Amount received: R$ 50.00 Debited amount: R$ 100.00 Date/Time: 08/01/2025 at 21:34:05 Store ABC Automatic Pix Debited amount: R$ 10,000.00 Date/Time: 08/15/2025 at 21:34:05 To register the complaint, select the desired transaction and click the "dispute" button João da Silva Pix via Key LAST TRANSACTIONS 17 17 21 The PSP may make available to the user the option to dispute more than one Pix or Automatic Pix transaction at the same time (batch registration). 20 When selecting the reason for disputing an Automatic Pix, the PSP may offer, among the answers provided to the user, an option that reflects a situation not covered by the MED. If the user selects this answer, there must be a message informing that such a situation cannot be handled through the MED, with guidance to seek the recipient directly to resolve the problem. 19 If the user tries to open a dispute registration for a Pix or Automatic Pix transaction that has already been subject to previous analysis and whose return was denied, they must be informed about the impossibility of new registration and guided to contact the customer service channel provided by the PSP for the treatment of complaints involving Pix. 18 If there is a communication failure with the DICT or another operational failure that prevents the registration of the Pix transaction dispute, the payer user must be immediately informed about this situation. The message must highlight that the dispute registration was not performed and that there was a technical or communication problem. Examples:

Failure in registering the Pix dispute. Try again later;
Sorry, we had a communication problem. Try again.
When disputing an Automatic Pix transaction, if the user selects an option related to the occurrence of a scam in the granting of a recurring payment authorization, the PSP must register the request and immediately open the value recovery in the DICT. The demand registration notification must address, at minimum, the following information:
Request registration protocol number, with date and time of
registration;
Maximum deadline for the PSP's response to the user regarding the acceptance or refusal of
the dispute;
Necessity of having a balance in the recipient's account of the root transaction or in
other accounts involved in the suspected fraud to enable the partial or total return of the value;
Information that the recipient's institution will be notified of the suspected fraud.
17
Recommended
Mandatory

112
Version 7.3 Self-Service MED
RECIPIENT: Payer's PSP
9:30
Return Management / Process
Balance: R$ 1,000.00
Consult disputes
Documents or fraud report have not been attached to your dispute yet. If you wish to speed up the analysis time of your request, click on "Send documents" Transaction ID: 885544756782258 Disputed amount: R$ 10,000.00 Recipient: João B. da Silva Deadline for response: 08/27/2025 Status: under analysis Date and time of registration: 08/16/2025, 12:17 PROCESS 2025/002356 Cancel dispute Send documents No Yes Are you sure you want to cancel this dispute? 9:30 Return Management / Process Balance: R$ 1,000.00 Consult disputes Documents or fraud report have not been attached to your dispute yet. If you wish to speed up the analysis time of your request, click on "Send documents" Transaction ID: 885544756782258 Disputed amount: R$ 10,000.00 Recipient: João B. da Silva Date and time of registration: 08/16/2025, 12:17 Status: under analysis Deadline for response: 08/27/2025 PROCESS 2025/002356 Cancel dispute Send documents 9:30 Balance: R$ 1,000.00 CONSULT DISPUTES Status: under analysis Disputed amount: R$ 10,000.00 Recipient: João da Silva Request: 2025/002356 Status: approved Amount returned: R$ 89.00 Disputed amount: R$ 100.00 Recipient: Store ABC Request: 2025/003578 Status: canceled Disputed amount: R$ 500.00 Recipient: Pedro Luis O. Pereira Request: 2025/000890 9:30 MED Balance: R$ 1,000.00 ? ? ? Consult disputes Dispute Pix MED The Special Return Mechanism (MED) of Pix transactions can be activated if you have been a victim of a scam or have received an undue charge from Automatic Pix. Only Pix transactions that occurred less than 80 days ago can be disputed. Attention, the MED cannot be used for commercial disagreements between buyer and seller, transfers to the wrong people or regret of the payer in making the Pix. 25 22 23 24 When requesting the cancellation of the dispute, before confirming, the user must be asked if they are sure they want to cancel. 25 When selecting a specific dispute, the following information must be made available to the user, at minimum:

Number, date and time of the registration protocol;
Status of the request;
PSP response deadline for analyzing the dispute, if the status indicates that it is still
under evaluation;
Name of the recipient of the disputed transaction;
Amount of the disputed transaction;
ID of the disputed transaction;

Amount actually refunded, in case of approved dispute.
When a dispute for fraud, scam, or crime considered valid results in a partial refund or no refund, the PSP must inform the user, after 90 days from the date of the disputed transaction, that refunds or value top-ups will not be possible due to insufficient balance in the receiving account of the root transaction or in other accounts involved in the fraud. For refund requests under analysis and considered valid, the user may request the cancellation of the request.

24
When consulting dispute records, a list of registered requests must be displayed with, at minimum, the following information:

Request protocol number;
Name of the recipient of the root transaction;
Value of the disputed transaction;
Amount actually refunded, in case of approved dispute;
Status of the request, clearly indicating which stage of the process it is in (for example: under analysis/approved/rejected/cancelled).

23
The functionality for consulting dispute records within the MED must allow the user to:

Check the progress of disputes within the MED made through any PSP service channel and the deadline for analysis completion;
If available, view the contact channel, in a format at the PSP's discretion, to send complementary information that will support the PSP's analysis of the dispute;
Cancel registered requests.

22
Mandatory

113
Version 7.3 MED Self-Service
RECIPIENT: PSP of the receiving user
9:30
Camera Email PSP XYZ
20
Calendar
A refund via MED of R$100.00 was made, regarding the transaction made on 08/23/2025, at 13:00:05, for the amount of R$150.00. PSP XYZ - 15:00 9:30 Camera Email PSP XYZ 20 Calendar The amount of R$100.00 was blocked in your account, due to a MED dispute of a Pix of R$150.00 made by Nadir da Silva, on 08/23/2025, at 13:00:05. The amount may remain blocked for 11 days, until the conclusion of the complaint analysis. PSP XYZ - 13:45 9:30 Camera Email PSP XYZ 20 Calendar The amount of R$100.00 was made available in your account, associated with the block performed on 08/23/2025, at 13:45:07, linked to the Pix transaction made by Nadir da Silva on 08/23/2025, at 13:00:05, for the amount of R$150.00. PSP XYZ - 15:00 27 26 Recipient 28 28 The receiving user of the root transaction and other recipients involved in the suspected fraud must be immediately notified, if the blocked funds have been actually refunded to the paying user of the root transaction. The message to the receiving user must contain, at minimum, the following information:

Value of the transaction linked to the infraction notification;
Date/time/minute/second (Brasília time) of the transaction linked to the infraction
notification;
Refunded amount;
Name of the refund recipient, if it concerns a refund occurring from the
account that received the resources of the root transaction.
The name of the refund recipient, when it concerns a refund occurring from an account different from the one that received the resources of the root transaction, must not be displayed in the message. 27 The receiving user of the root transaction and other recipients involved in the suspected fraud must be immediately notified when the release, in their account, of funds until then blocked. The message to the receiving user must contain, in the minimum, the following information:
Name of the paying user of the transaction linked to the infraction notification;
Date/time/minute/second (Brasília time) of the transaction linked to the infraction
notification;
Value of the transaction linked to the infraction notification;
Amount made available;
Date/time/minute/second (Brasília time) of the block.
The message must be sent even in cases where a refund of
part of the previously blocked amount occurred.
26
The receiving user of the root transaction and other recipients involved in the suspected fraud must be immediately notified about the block, in their account, resulting from the receipt of an infraction notification. The message to the receiving user must contain, at minimum, the following information:
Name of the paying user of the transaction linked to the infraction notification;
Date/time/minute/second (Brasília time) of the transaction linked to the infraction
notification;
Value of the transaction linked to the infraction notification;
Reason for the block;
Blocked amount;
Maximum block deadline (11 days).
Mandatory

114
Version 7.3 MED Self-Service
RECIPIENT: PSP of the paying user
9:30
PSP ABCD Email
You received R$ 100.00 in your account, regarding the refund of a disputed Pix transaction. Access the Dispute Pix -> Consult disputes menu for more information. PSP ABCD - 15:00 29 29 Payer 9:30 PSP ABCD Email You received R$ 100.00 in your account, regarding the refund request of a Pix of R$ 150.00 made to Fernanda Costa, on 08/23/2025, at 13:00:05. PSP ABCD - 15:00 Payer 31 The PSP of the paying user may send notifications to inform changes in the status of the MED dispute record. 30 The provisions in items 26 to 29 apply to disputes within the MED opened by any service channel. 29 The paying user of the root transaction must be immediately notified about the credit in their account resulting from a refund of a disputed Pix transaction. The credit notification originating from the account of the recipient of the root transaction must contain, at minimum, the following information:

Amount credited;
Name of the refund sender;
Date/time/minute/second (Brasília time) of the root transaction;
Value of the root transaction.
If the credit comes from an account different from the one that received the root transaction, the notification must contain at minimum:
Amount credited;
Information about the dispute linked to this credit or a clear indication of where
the user can access this information, through the consultation functionality of the records within the MED. At the PSP's discretion, this indication may include a link that takes the user directly to the screen with dispute details, provided there is prior authentication in the account application. The name of the sender, when it concerns an account different from the one that received the root transaction, must not be displayed to the paying user. Recommended Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
17
This refers to the provision to the user of a service of initiation of payment transaction in Pix. Payment transaction initiation service in Pix

116
Version 7.3 Payment transaction initiation service in Pix RECIPIENT: Participant providing Payment Transaction Initiation Service 04 When there is a key sent to the DICT and the return is of a key not found or of a non-existent key linked to the QR Code, the paying user must be informed about the non-existence of this key by the PSI.

Mandatory message: It must highlight that the transaction was not completed and that the
key is non-existent.
Examples:
Transaction not completed. Non-existent key.
Key not located. Try again.
An error occurred. This key could not be found.
Error. Check if you entered the correct key.
Pix not completed. Check if the key is correct.
03
When the paying user enters a Pix key in a format incompatible with those accepted by Pix, the key must not be forwarded to the DICT and the user must be communicated about the format error by the PSI. Mandatory message: It must highlight that the transaction was not completed and that there is a problem with the key format. Examples:
Transaction not completed. Invalid key format;
There was a problem with the key format. Try again;
An error occurred. Check the format of this key;
Your Pix was not completed. Check the format of the key entered.
02
The paying user must be notified if the transaction is suspected of fraud, always when the PSP needs to use additional time for transaction analysis. During the period in which the payment order is being analyzed, the payment transaction initiation service provider must make available, for the paying user, the option to cancel the transaction. For this, the PSP must always notify the PSI in these cases. Mandatory message: It must highlight that the transaction requires additional time for analysis to be authorized and give the option to cancel the transaction. Examples:
We need an additional 30 minutes to analyze your transaction. Do you want to cancel the
Pix?
Your transaction needs approximately 60 minutes to be authorized. Do you want
to cancel the transaction?
01
It is mandatory for all payment transaction initiation service providers (PSIs) to use the nomenclatures "Pix", "Key" or "Pix Key", "My keys", “Portability”, “Claim”, “Random key”, “Copy and Paste Pix”, “My Pix Limits”, “Scheduled Pix” and “Automatic Pix”. Mandatory

117
Version 7.3 Payment transaction initiation service in Pix RECIPIENT: Participant providing Payment Transaction Initiation Service 08 If the document does not accept payment after the due date, attempts to send an order outside this deadline to the paying user's PSP must be refused and the user must be informed about this condition. The message must highlight that the transaction was not completed and specify the error. Examples:

Transaction not completed. Expired QR Code. This QR Code does not accept payment after
expiration.
Pix not performed. Expired QR Code.
07
If the QR Code expiration period has been exceeded, the paying user must be communicated about this. The message must highlight that the transaction was not completed and specify the error. Examples:
Transaction not completed. Invalid QR Code.
Error performing Pix. Invalid QR Code.
06
When the recipient's PSP is not available to consult the data of the dynamic QR Code payload, the paying user must be informed about this situation by the PSI. Mandatory message: It must highlight that the transaction was not completed and that there was a technical or communication problem. Examples:
Transaction not completed. Communication failure. Try again.
Your Pix was not finalized. We had a technical problem.
Sorry, we had a communication problem. Try again.
05
If there is a communication failure with the DICT, the paying user must be informed about this situation by the PSI. Mandatory message: It must highlight that the transaction was not completed and that there was a technical or communication problem. Examples:
Transaction not completed. Communication failure. Try again.
Your Pix was not finalized. We had a technical problem. Try again.
Sorry, we had a communication problem. Try again.
Mandatory

118
Version 7.3 Payment transaction initiation service in Pix RECIPIENT: Participant providing Payment Transaction Initiation Service 14 If the payment transaction initiation service provider offers single and/or recurring Pix transaction scheduling, it must comply with the obligations provided in the chapter "Scheduled Pix". 13 In cases where the payment transaction initiation service provider has all the information of the receiving user, before payment confirmation, the following data must be informed to the paying user, at minimum:

Name and CPF (masked) / CNPJ (unmasked) of the recipient. In the case of CNPJ, the
name informed must be the Company's Trade Name, if it exists. If it does not exist, the name informed must be the Company Name/Legal Name. The agency number and the recipient's account number must not return to the paying user. The return of the recipient's PSP name information is optional and is at the participant's discretion;
Transaction value.
These data must also be informed to the payer by the participant holding the transactional account, at the moment of payment confirmation. 12 The payment transaction initiation service provider must comply with the obligations regarding the set of data that must be informed to the paying user before payment confirmation, according to the initiation method used by the paying user and its requirements provided in the chapters "Pix with Pix Key", "Pix with manual entry of transactional account data", "Payment through static QR Code" and "Immediate payment or with due date through dynamic QR Code". 11 When applicable to the payment transaction initiation service provider, the display of the CPF of a receiving user must always occur in a masked format (e.g., *.777.888-). 10 The payment transaction initiation service provider cannot save the transactional account data nor must it provide an option to save the transactional account data when the txId is filled. 09 The payment transaction initiation service provider cannot save the Pix Key nor must it provide an option to save the Pix Key when the txId is filled. Mandatory

119
Version 7.3 Payment transaction initiation service in Pix RECIPIENT: Participant providing Payment Transaction Initiation Service 19 The payment transaction initiation service provider may provide integration with the user's contact list, with identification next to the names that have a Pix Key. 18 PSIs offering Automatic Pix may provide the functionality to consult the history of all authorizations, corresponding to the consent stage. 17 Automatic Pix may be made available to the paying user for recurring transactions automatically, with prior authorization, through the payment transaction initiation service. 16 Scheduled Pix may be made available to the paying user for single and/or recurring Pix transaction scheduling through the payment transaction initiation service. 15 If the payment transaction initiation service provider offers Automatic Pix, it must comply with the obligations provided in the chapter "Automatic Pix" regarding the provision:

Of information about the main rules of the service, its advantages and
operation, in a location at the PSI's discretion;
Of the consultation, editing, and cancellation functionalities of active authorizations,
corresponding to the consent stage in the journey offered by the PSI;
Of the consultation and cancellation functionalities of scheduled payments;
Of the payment receipt;
Of error messages;
Of the notifications applicable within the payment transaction initiation service.
Recommended
Mandatory

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
18
Functionality that allows the user to easily identify people in the contact list of their smartphone who have Pix keys. Contact List Integration

121
Version 7.3 Contact List Integration
RECIPIENT: PSP of the paying user and PSP of the receiving user 9:30 João da Silva Fernanda Costa Email PSP XYZ 9:30 Favorite History More 61 98888 5555 MessageApp Pix - PSP XYZ Pix - PSP ABCD VideoApp Fernanda Costa fcosta@email.com www.meusite.com 9:30 Recipient / Value Balance: R$ 1,000.00 Continue Enter agency and account Key random Cell Phone CPF Email Select key type ? If you do not have a key for addressing the recipient, use the "Enter agency and account" button to perform a Manual Pix. Description (optional) Small transaction description 0 of 140 characters Value R$ 0,00 Fernanda Costa 61 98888-5555 Guilherme Souza 61 99555-5555 Henrique Oliveira 61 98666-6666 João da Silva 61 99222-2222 +55 (61) 9 03 02 01 01 03 Shortcut creation via smartphone widgets, requiring prior user consent. 02 Direct shortcut creation in the smartphone contact list, requiring prior user consent. 01 Make available in the PSP application integration with the user's contact list, with identification next to the names that have a Pix Key. Access to the contact list via PSP application requires prior user consent. Recommended

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
19
Provision of an option to the paying user, in the internet banking interface, to paste code. Pix in Internet Banking

123
Version 7.3 Pix in Internet Banking
RECIPIENT: PSP of the paying user and PSP of the receiving user LOJAZYXW SUMMER PROMO 20 Click here % DISCOUNT Bag R$ 55.00 Shirt R$ 59.00 Shoe R$ 65.00 Other products HOME PRODUCTS SUPPORT PAYMENT METHODS Choose the desired payment method and proceed to the next step NEXT FINALIZE YOUR PURCHASE PIX CREDIT CARD PAY IN STORE BOLETO Polo shirt R$ 50.00 01 Order summary Qty Exclude Size: M Shipping: R$ 5.00 Total: R$ 55.00 01 When selecting the payment method Pix the user may have access to the QR-code or code for payment. 01 In the PSP's internet banking, there may be a quick and easy access option for the user to perform payments of transactions from websites, through the option to paste Pix code obtained on websites. Recommended

124
Version 7.3 Pix in Internet Banking
RECIPIENT: PSP of the paying user and PSP of the receiving user LOJAZYXW PIX SUMMER PROMO 20 Click here % DISCOUNT Bag R$ 55.00 Shirt R$ 59.00 Shoe R$ 65.00 Other products HOME PRODUCTS SUPPORT FINALIZE YOUR PURCHASE Point your phone camera at the QR-code/image below or copy the code and pay in your Internet Banking. PREVIOUS NEXT PAYMENT METHODS QR-code Code Copy 00020101021226720014br.gov.bcb.pix2550bx.com.br/pix/8b3- da2f3-9a41-40d1- a91abd93113bd4415204000053039865406123.455802BR5913Fulano de Tal6008BRASILIA62190515RP12345678-2019630445C8 Polo shirt R$ 50.00 01 Order summary Qty Exclude Size: M Shipping: R$ 5.00 Total: R$ 55.00 01 There may be options for the user to share the QR Code or code on social networks. The user can scan the QR Code or copy the code to perform the payment. 01 In the PSP's internet banking, there may be a quick and easy access option for the user to perform payments of transactions from websites, through the option to paste Pix code obtained on websites. Recommended

125
Version 7.3 Pix in Internet Banking
RECIPIENT: PSP of the paying user and PSP of the receiving user LIMIT / Pix R$3,000 Lorem ipsum dolor sit amet, consectetuer adipiscing elit, BALANCE / ACCOUNT R$1,000 Lorem ipsum dolor sit amet, consectetuer adipiscing elit, LIMIT USED 1.486 Lorem ipsum dolor sit amet, consectetuer adipiscing elit, Pix / PIX VIA CODE M T W T F S S 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 OCTOBER R$ 3,500 R$ 1,200 LIMIT BALANCE PSP XYZ Name Surname Name Surname PSP XYZ 60% 50 Purchases 40 Fuel 30 Restaurant 20 Health Main expenses PSP XYZ Search Enter the CODE generated in the field below to perform the payment PAYMENT VIA CODE code CONTINUE OTHERS LOAN OTHER PRODUCTS SUPPORT HOME Pix MY KEYS PIX VIA KEY PIX VIA QR-CODE PIX VIA CODE STATEMENT PIX VIA MANUAL CHECKING ACCOUNT TRANSFER CARDS INVESTMENTS Forgot password? Login CPF

Access your account through App XYZ!
PSP XYZ
01
After login, the user has access to their specific area of Pix within Internet Banking. Specific field to insert the Pix code for payment. 01 In the PSP's internet banking, there may be a quick and easy access option for the user to perform payments of transactions from websites, through the option to paste Pix code obtained on websites. Recommended

126
Version 7.3 Pix in Internet Banking
RECIPIENT: PSP of the paying user and PSP of the receiving user M T W T F S S 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 OCTOBER Bank XYZ Name Surname Bank XYZ Name Surname R$ 3,500 R$ 1,200 LIMIT BALANCE PAYMENT VIA CODE Enter the code generated in the field below to perform the payment CONTINUE 0 2 0 1 0 1 0 2 1 2 2 6 7 2 0 0 1 4 b r . g o v . b c b . p i x 2 5 5 0 b x . c o m . b r / p i x / 8 b 3 d a 2 f 3 - 9 a 4 1 - 4 0 ... Purchases Fuel Restaurant Health Main expenses 50 40 30 20 60% LIMIT / PIX R$3,000 Lorem ipsum dolor sit amet, consectetuer adipiscing elit, BALANCE / ACCOUNT R$1,000 Lorem ipsum dolor sit amet, consectetuer adipiscing elit, LIMIT USED 1.486 Lorem ipsum dolor sit amet, consectetuer adipiscing elit, PIX / PIX VIA CODE PSP XYZ Search PAY TODAY
SCHEDULE
Name: polo shirt
Original value: R$50.00
Identifier: product1234
Interest: 1%
Interest/Period: Per month
Fine: 2%
Fine/Period: After 01/21/2020
Due date: 01/21/2020
Final value:
R$55.00 Institution: PSP XYZ avenue abc - street 03 - store 25

São Paulo/sp
Recipient Data GENERAL DATA
ADDITIONAL DATA
Name: LOJA ZYXW
DEBTOR Data
Name: NADIR da Silva
CPF: *.993.555-
CPF/CNPJ: 12.345.678/0001-90
Address:
NO
DUE DATE
OTHERS
LOAN
OTHER PRODUCTS
SUPPORT
HOME
PIX
MY KEYS
PIX VIA KEY
PIX VIA QR-CODE
PIX VIA CODE
STATEMENT
PIX VIA MANUAL
CHECKING ACCOUNT
TRANSFER
CARDS
INVESTMENTS
01
After inserting the code and continuing, the data will be loaded and the user will have access to the button to finalize the purchase. 01 In the PSP's internet banking, there may be a quick and easy access option for the user to perform payments of transactions from websites, through the option to paste Pix code obtained on websites. Recommended

127
Version 7.3 Pix in Internet Banking
RECIPIENT: PSP of the payer user and PSP of the payee user PAY TODAY
SCHEDULE
Name: polo shirt
Original Value: R$50.00
Identifier: product1234
Interest: 1%
Interest/Period: Per month
Fine: 2%
Fine/Period: After 21/01/2020
Due Date: 21/01/2020
Final Value:
Institution: PSP XYZ R$55.00 avenida abc - rua 03 - loja 25 - São Paulo/sp Payee Data GENERAL Data ADDITIONAL Data Debtor Data Name: LOJA ZYXW Name: NADIR da Silva CPF: *.993.555- CPF/CNPJ: 12.345.678/0001-90 Address:
NO
DUE DATE
02
Before confirmation of the payment with due date, the following data must be returned to the payer user, using the DICT data on the payee user in the applicable fields:

Due date field;
Option for the payer, if desired, to inform the Intended Payment Date (DPP), defined in the Manual of Standards for Pix Initiation, for the same day or for the due date or for a scheduled date;
Values: original, discount, interest, fine (if informed) and final value;
Name and CPF (masked) / CNPJ (unmasked) of the payee. In the case of CNPJ, the name informed must be the Company's Trade Name, if it exists. If it does not exist, the name informed must be the Company Name/Legal Name. The agency number and the account number of the payee must not be returned to the payer user. The return of the information of the name of the payee's PSP is optional and is at the discretion of the participant;
The debtor's data (CPF/CNPJ and Name);
The "InfoAdicionais" field, if informed, as defined in the Manual of Standards for Pix Initiation;
The “infoAdicionais” field must contain only characters or HTML without any dynamic content, such as scripts (javascript, php, cgi, among others);
The "Request to Payer" field, if informed: description and text box for the payer user to fill in;
Payee address fields: State; City; Street and ZIP code (this information may be available to the user through another object, such as an icon or button).
Recommended

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
20
Making accessibility tools available to the user, integrated into the Pix environment. Accessibility in Pix

129
Version 7.3 Accessibility in Pix
RECIPIENT: PSP of the payer user and PSP of the payee user 9:30 Pix Pix with Key / Manual Pix Copy and Paste Pix with QR Code Receive Pix My limits Pix Pix Automatic Statement / Return My keys R$10.00 Payment Value via Key Roberto da Silva R$30.00 Value João da Silva LAST TRANSACTIONS Cellphone CPF Key Random E-mail Balance: R$ 1,000.00 Nadir da Silva Dark theme Explanatory video in Libras about Pix Increase font Video 9:30 Pix Pix with Key / Manual Pix Copy and Paste Pix with QR Code Receive Pix My limits Pix Pix Automatic Statement / Return My keys R$10.00 Payment Value via Key Roberto da Silva R$30.00 Value João da Silva LAST TRANSACTIONS Cellphone CPF Key Random E-mail Balance: R$ 1,000.00 Nadir da Silva To access the accessibility options, the user simply needs to press the button indicated on the main screen and choose the desired option. 02 It is recommended that, regarding visual impairment, accessible development practices and techniques be used, integrated with the accessibility tools offered by smartphones, being non-exhaustive examples:

Increase the size of the touch areas of buttons or icons ("touch");
Active description in screen elements and functionalities;
Selection of priorities of information to be read;
Use of short and direct descriptions, to speed up and facilitate user navigation in the Pix environment.
01
It is recommended that, regarding hearing impairment, accessibility tools be made available, being a non-exhaustive example:
Short explanatory videos about Pix directed at people with hearing impairment (in Libras and subtitled), to address main doubts, in the form of Frequently Asked Questions (FAQ);
Possibility of using a Libras interpreter.
Recommended

December 2025
Version: 7.3
Recommendations and OBLIGATIONS
21
Items to be evaluated in the process of verifying the adherence of solutions to end users.
Annex I

The items contained in the process of verifying the adherence of solutions to end users, as well as the

respective screens of the application design project, must be

identified and arranged according to the order presented

in the table contained in this annex.

Compliance with the other items contained in the

document “Minimum Requirements for User

Experience” is mandatory, there being no need to present the screens within the scope of the project of solution to end users. Observations:

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 131 An informative message must be made available in the Pix environment, next to the shortcut to the participant's service channel, so that the user can register a complaint on the Central Bank's website if the occurrence is not resolved by the PSP.

“https://www.bcb.gov.br/acessoinformacao/registrar_reclamacao”.
Page 8, item 11
11
A shortcut must be made available on the Pix environment's home screen that the user can easily access and identify as the path to the service channel made available by the PSP for handling complaints involving Pix, including those related to the Special Return Mechanism and fraud. When clicking on this shortcut, the user must be immediately directed to said channel, without having to go through intermediate steps.
Page 8, item 10
10
The following payment initiation forms must be offered to the user:
Insertion of Pix key.
QR Code reading.
Insertion of PSP, agency, transactional account and CPF/CNPJ of the payee user.
Insertion of Pix Copy and Paste.
Page 6, item 05
05
If the participant makes the Pix environment available on the login screen, it must adopt one of the following actions:
Make access to the dedicated Pix environment available on the screen immediately after login;
Insert the Pix option in all menus and submenus of the application related to payments or transfers, with no less prominence than the other payment methods.
Page 6, item 03
03
If the participant's application has payment and/or receipt functionalities on the login screen, it must necessarily make access to the Pix environment available on that screen.
Page 6, item 02
02
The Pix environment must be accessible at any time in the main application of each participant. Whenever applicable, its access must be on the login screen or on the screen immediately after login, with no less prominence than any other payment or transfer functionality.
Page 6, item 01
01
General Obligations and
Recommendations

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 132 Make payment receipt available to payer and payee users during the period established in the regulation in force, containing, at minimum, the information of the name, CPF (masked or not) / CNPJ and name of the PSP, of the payer and payee users, the “Description” field (whenever filled in), in addition to value and transaction ID, and hour/minute/second (Brasília time) of settlement. When the transaction involves a PSI, the name of the PSI must appear on the receipt. The message and the minimum fields that must be presented to the user are represented on the screen to the side.

The ID/transaction refers to the "EndtoEndID" present in pacs.008;
The “Description” field refers to “informacoesEntreUsuarios” of pacs.008;
The “Description” field must not contain HTML tags. The payer user's application must display the characters of this field literally and, therefore, must not render links or any dynamic content.
Page 16, item 13
13
The key selection must return the payee user's data for verification: full name, masked CPF (e.g., *.777.888-) /CNPJ, Pix key, in addition to value and option to cancel the transaction before payment confirmation. The agency number and the payee's account number must not be returned to the payer user. The return of the information of the name of the payee's PSP is optional and is at the discretion of the participant.
Full name, hidden CPF (e.g., *.777.888-) /CNPJ;
Pix Key;
Value field;
Cancel option. This option is not necessarily a “Cancel” button. It is simply the cancellation functionality available before the conclusion of the transaction. Its implementation aims to reduce the number of returns of erroneous transactions;
In the case of CNPJ, the name informed must be the Company's Trade Name, if it exists. If it does not exist, the name informed must be the Company Name/Legal Name.
Page 14, item 07
07
The “Description” field, optional for the user to fill in, must be presented for filling in.
In the formation of pacs.008, the text of the “Description” field must be inserted in the “informacoesEntreUsuarios” field.
The “Description” field must not contain HTML tags. The payer user's application must display the characters of this field literally and, therefore, must not render links or any dynamic content.
Page 12, item 03
03
For payments with manual key insertion, at minimum, the following key types must be accepted:
CPF/CNPJ, cell phone number, e-mail.
Page 12, item 01
01
Pix with Pix Key

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 133 Provide a Copy QR Code option to enable the Pix Copy and Paste functionality.
Page 25, item 07 07
Optional fields (identifier and value) must be presented, emphasizing to the user that they are not mandatory to fill in.

Identifier and value;
The Identifier field refers to the “TxId” field of pacs.008 and is used, by the payee, to reconcile its receipts.
Page 24, item 03
03
The payee user must be given the possibility to generate the static QR Code from the four keys:
Cell phone number, e-mail, CPF/CNPJ or random key.
Page 23, item 02
02
The Receive Pix option must be highlighted and easily accessible to the user.
Page 23, item 01 01
Make payment receipt available to payer and payee users during the period established in the regulation in force, containing, at minimum, the information of the name, CPF (masked or not) / CNPJ and name of the PSP, of the payer and payee users, the “Description” field (whenever filled in), in addition to value and transaction ID, and hour/minute/second (Brasília time) of settlement. When the transaction involves a PSI, the name of the PSI must appear on the receipt. The message and the minimum fields that must be presented to the user are represented on the screen to the side.
The ID/transaction refers to the "EndtoEndID" present in pacs.008;
The “Description” field refers to “informacoesEntreUsuarios” of pacs.008;
The “Description” field must not contain HTML tags. The payer user's application must display the characters of this field literally and, therefore, must not render links or any dynamic content.
Page 21, item 08
08
The fields referring to the transactional account, the CPF/CNPJ and the “Description” field (optional filling by the user) must be presented for filling in.
Fields referring to the transactional account, CPF/CNPJ, “Description” field.
The number associated with each PSP, only for the purpose of searching for PSPs by its users, can be either the PSP's code number or its ISPB, at the discretion of each participant. Special clearing participants cannot appear in the list of participating institutions.
Page 19, item 01
01
Generation of QR
Static Code
Pix with Manual Insertion of Transactional Account Data

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 134 The My Keys functionality must be offered through quick and clear access for the user. The options for registration, deletion and portability must be offered to the user.
Page 48, item 06
06
Obligatory present, whenever there is key registration, a consent message that informs, at minimum, that payer users who have knowledge of the key will view the following data of the payee user when sending payments:

Full name;
CPF with mask (e.g., .777.888-).
The name of the payment service provider to which the key is linked, in the case of Pix initiated by QR Code, may be displayed, at the discretion of the payer's PSP. In addition, the consent message must inform that all other Pix users who have the information of the user's e-mail or cell phone number will be able to know that he registered this email and/or this cell phone number as a Pix key.
Page 47, item 02
02
To be able to select the return, the user must, at minimum, view the payer's name, the value of the original transaction and the date of payment of the original transaction.
Page 42, item 02
02
There must be functionality for the user to return any receipt occurred in the last 90 days.
Page 42, item 01 01
Pix transactions (payments, receipts, withdrawals, including the amount of cash made available in a Pix Troco and returns) must be present in the transactional account statement, so that these transactions can be easily differentiated from transactions that are not Pix.
Page 40, item 01
01
Make payment receipt available to payer and payee users during the period established in the regulation in force, containing, at minimum, the information, of the name, CPF (masked or not)/CNPJ and name of the PSP, of the payer and payee users, message of the “Identifier” field (TxId), whenever filled in, in addition to value and transaction ID, and hour/minute/second (Brasília time) of settlement. When the transaction involves a PSI, the name of the PSI must appear on the receipt. The message and the minimum fields that must be presented to the user are represented on the screen to the side.
The ID/transaction refers to the "EndtoEndID" present in pacs.008.
Page 31, item 13
13
My Keys
Return
Statement
Payment through
Static QR Code

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 135 As soon as the authorization of the recurring payment through Pix Automatic (journeys 1, 2 and 4) is concluded, the payer user must be immediately informed that:

Notifications will be sent when payments are scheduled;
The receipt of scheduling notifications and the use of credit limit for payments through Pix Automatic can be disabled;
The cancellation of the authorization can be done at any time;
The maximum value of payments can be changed (if established);
Payments are conditioned to the availability of balance and Pix Automatic limit.
The authorization ID information must be made available.
Page 89, item 17
17
In the Pix environment, the “Pix Automatic” menu must be made available with, at minimum, the following functionalities:
QR Code reading for the purpose of Pix Automatic authorization;
Consultation and management of pending authorizations;
Consultation and management of active authorizations;
Consultation and management of scheduled payments;
Consultation of authorization history;
Learn More.
Page 83, item 01
01
Pix Copy and Paste must be made available on the first screen of the Pix environment.
Page 71, item 01 01
The payer user must be made available the option to schedule Pix transactions, including for non-business days.
Page 64, item 01 01
Functionalities must be made available that allow the user to consult and manage Pix limits per transaction and per type of beneficiary, including for Pix Withdrawal/Pix Troco, Scheduled Pix and Pix Automatic, and register accounts and/or beneficiaries with differentiated limits.
Page 54, item 01
01
Pix Automatic
Pix Copy and Paste
Scheduled Pix
My Pix limits

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 136 Make recurring payment receipt available to payer and payee users during the period established in the regulation in force, containing, at minimum:

Identification that the transaction is a Pix Automatic;
Name and CNPJ of the payee;
Name of the payee's PSP;
Name and CPF (masked or not)/CNPJ of the payer;
Object of payment (if informed);
Identifier of the billing object (contract number, customer code, etc);
ID; of the transaction ("EndtoEndID" present in pacs.008)
Hour/minute/second (Brasília time) of settlement;
Value.
When the transaction involves a PSI, the name of the PSI must appear on the receipt. The message and the minimum fields that must be presented to the user are represented on the screen to the side.
Page 99, item 40
40
The payer user must be made available functionality to consult and cancel scheduled payments.
Page 96, item 32 32
Functionality for consultation, editing and cancellation of active authorizations must be made available.
Page 93, item 25 25
As soon as the immediate payment and the authorization of the Pix Automatic of journey 3 are concluded, the user must be immediately informed that:
The immediate payment was effected;
Notifications will be sent when the next payments made through Pix Automatic are scheduled;
The receipt of scheduling notifications and/or the use of credit limit for payments through Pix Automatic can be disabled;
The cancellation of the authorization can be done at any time;
The maximum value of payments can be changed (if established);
Payments are conditioned to the availability of balance and Pix Automatic limit.
The authorization ID information must be made available.
Page 92, item 21
21
Pix Automatic

RECIPIENT: PSP of the payer user and PSP of the payee user Version 7.3 Annex I 137 If the user selects a response that specifically identifies the scam, fraud or crime, the PSP must register the demand and immediately open the value recovery in the DICT. The communication of the registration of the demand must address, at minimum, the following information:

Number of the protocol of the registration of the return request, with date and time of registration;
Maximum deadline for the PSP's response to the user regarding the acceptance or refusal of the dispute;
Necessity of existence of balance in the receiving account of the root transaction or in other accounts involved in the suspicion of fraud to enable the partial or total return of the value;
Information that the payee's institution will be notified of the suspicion of fraud.

Page 107, item 08
08
When activating the Pix transaction dispute function for scam, fraud or crime or irregularities in Pix Automatic transactions, the user must be directed to the account statement or to the Pix statement (if made available) to select the transaction object of the dispute. The option to register the dispute by directly accessing the transaction, through the account statement or the Pix statement (if made available), must also be made available to the user, with the rules of the mechanism being informed, at least on the first access.
Page 107, item 05
05
When disputing a Pix, the user must be informed, at least on the first access, about the main rules of the MED, addressing, at minimum, in which cases it can be activated, which situations are not covered, the steps of the process and the maximum deadline to request the return. See examples presented in said item.
Page 106, item 04
04
The menu of the Pix transaction dispute functionality must make available the options to dispute Pix and to consult records of disputes.
Page 106, item 02 02
There must be functionality, in the Pix environment, for the user to dispute a Pix or Pix Automatic transaction in cases of scam, fraud or crime or a Pix Automatic transaction in case of operational failure of the payer PSP. The functionality must also make available consultation to registered disputes. The shortcut made available in the Pix environment to access the PSP's service channel for handling complaints must also allow access to this functionality.
Page 105, item 01
01
Self-service
MED

138
10/2020 2.0 • Inclusion of Chapter 13

-"Pix Copy and Paste" and adjustment of the numbering of subsequent chapters.

Chapters 3 and 4 (item 3):
-Inclusion of information regarding the free field -Formation of pacs.008.
Chapter 3 (item 13):
-Inclusion of information regarding the Transaction ID – EndtoEndID of pacs.008.
Chapter 4 (item 09):
-Inclusion of information regarding the Transaction ID – EndtoEndID of pacs.008.
Chapter 6 (item 13):
-Inclusion of information regarding the Transaction ID – EndtoEndID of pacs.008.
Chapter 7 (item 4 and 6):
-Inclusion of information regarding the Transaction ID – EndtoEndID of pacs.008.
Chapter 11 (item 14):
-Inclusion of information regarding the Transaction ID – EndtoEndID of pacs.008.
New Chapter 13:
-Pix Copy and Paste: Making available an option to the payer user, in the mobile banking interface, to paste shortcut.
Chapter 14:
-Pix in Internet Banking: Change of chapter title and numbering. 08/2020 1.0 • Index:
-Correction of the title of Chapter 11 from "Receipt through Dynamic QR Code" to "Payment through Dynamic QR Code".
Chapter 2:
-Insertion of obligation 9.
Chapters 3 (item 13), 4 (item 9), 6 (item 13) and 11 (item 14):
-Exclusion of the obligation to mention the service channel on the payment receipt.
Chapter 13:
-Substitution of references to "link" by "code", with corresponding alteration in the illustrations.
Small form adjustments throughout the text.
22 Revision History
Date Version Description of Changes

139
12/2020 3.0 • Index:

Inclusion of Chapter 10 – “My Pix Limits” and adjustment of the numbering of subsequent chapters;
Change of the title of Chapter 11 to Immediate Payment or Payment with Maturity via Dynamic QR Code.
General Obligations:
Page 7: item 09 – Text alteration; Exclusion of the term “Free Field” present in the illustrative figure; Change of the character quantity of the Description field (0 to 140 characters);
Creation of items 10, 11, and 12, which are mandatory.
Chapters 2, 6, 10, 11, and 13 (Pix environment home screen)
Inclusion of the “My Pix Limits” icon.
Chapter 02: (item 07):
Inclusion of the mandatory nomenclature “My Pix Limits”.
11/2020 2.1 • Index:
Correction of the chapter title from “Receipt” to “Payment” via Dynamic QR Code;
Insertion of Annex I – Items to be evaluated in the process of verifying the adherence of solutions to end users.
General Obligations (Page 6, item 01):
Alteration of the wording of the item to “The Pix environment must be accessible at any time in the main application of each participant. Its access must be on the login screen or on the screen immediately after login, with no less prominence than any other payment or transfer functionality.”
. Chapter 5 (item 02):
Exclusion from the application screen of the mention of the character quantity in the “Description” field.
Chapter 5 (item 03):
Inclusion of information regarding the “Identifier” field;
Inclusion of information regarding the “Description” field; Exclusion from application screens of the mention of the character quantity in the “Description” field.
Chapter 05 (page 21):
Alteration of the expression “copy link” to “copy code”.
Chapter 13 (pages 52, 53, 54, and 55):
Alteration of the word “shortcut” by the word “code”.
Chapter 13 (page 54):
Alteration of the expression “copy link” to “copy code”.
Chapter 14 (pages 56, 58, and 59):
Alteration of the word “shortcut” by the word “code”.
Chapter 14 (page 58):
Alteration of the expression “copy the link” to “copy the code”.
Annex I: Items to be evaluated in the process of verifying the adherence of solutions to end users.
Revision History: Insertion of a table with the history of versions and revisions of the content.
Date Version Description of Changes

140
12/2020 3.0 • Chapter 03:

Pages 10, 11, and 12 - Exclusion of the “Free Field” present in the illustrative figures. Alteration of the terms “free field” to the terms “Description field”.
Page 10 – alteration of the text of item 03;
Page 12 - alteration of the text of item 06; exclusion of the “Institution” field;
Page 14 – new item 12 with new wording; inclusion of recommended item 14, regarding Random Keys.
Chapter 04:
Page 16 - items 01 and 03: alteration of the terms “free field” to the terms “Description field”;
Page 18 - alteration of the text of item 07; exclusion of the text of item 08, original. Renumbering of item 09 to 08, accompanied by new text;
Chapter 05:
Page 20 - inclusion on the application screen of the mention of the character quantity in the “Identifier” field (0 to 25 characters);
Pages 20, 21, and 22 - exclusion of the “Description” field;
Page 20 - Inclusion on the application screen of the mention of the character quantity in the “Identifier” field (0 to 25 characters);
Page 22 - item 07 becomes mandatory. Insertion of item 08, recommended; Adjustment of the figure, with the alteration of the term “Copy Code” to “Copy QR Code”; exclusion of the “Description” field. Alteration of the text of item 03.
Chapter 06:
Pages 24, 25, and 27 - exclusion of the “Description” field;
Page 24 – adjustment of the text of item 01;
Page 25 - alteration of the word “Institution” to “PSP” in the two figures on the page;
Page 28 – exclusion of original item 12 and renumbering of item 13 (previous) to item 12.
Chapter 08:
Page 32 - alteration of the text from “Free Field” to “Description”;
Page 33 – creation of new item 06;
Page 33: alteration of the text of the now item 07.
Exclusion of Chapter 10 – Generation of Dynamic QR Code.
New Chapter 10:
My Limits - Functionality that allows Pix users to consult, reduce, as well as request an increase in the value of the transactional limits made available.
Chapter 11:
Page 46 - Alteration of the title and content to Immediate Payment or Payment with Maturity via Dynamic QR Code - This refers to a payment initiated by the payer user through the reading of a dynamic QR Code;
Pages 47, 48, 49, 50, and 51 – alteration of items and screens in order to represent the experience of immediate and mature dynamic QR Code payments.
Minor formatting adjustments.
Date Version Description of Changes

141
01/2021 3.1 -Pages 8, 10, 14, 16, 18, and 33: inclusion of obligation regarding the “Description” field - “The “Description” field must be sanitized so as to neutralize unsafe HTML tags.”

Adjustments to the references of the pages of the items to be evaluated in the process of verifying the adherence of solutions to end users.
Adjustment to the text of the revision history regarding version 3.0 of 24.12.2020.
Minor formatting adjustments.
Date Version Description of Changes

142
03/2021 4.0 • Index:

Inclusion of Chapter 14 - “Integration with Contact List” and adjustment of the numbering of subsequent chapters.
Introduction:
Page 04 - new wording in the second paragraph of the Introduction with the objective of informing that the Pix Brand Usage Manual must be respected regarding the application of the Pix brand.
Chapter 2:
Page 06 - alterations to the text of item 01.
Page 08 - alterations to the text of items 10 and 11.
Chapter 4:
Page 18 - alteration in the exemplary screens.
Chapter 5:
Page 22 - alteration in the exemplary screens.
Chapter 6:
Pages 24, 25, 26, 27, and 28 - alteration in the exemplary screens.
Page 28 - inclusion of new item number 13 – “The PSP cannot save the Pix key nor should it make available the option to save the Pix key linked to the payment of the static QR Code when the TxId is filled.”
Chapter 7:
Page 30 - alteration in the exemplary screen.
Chapter 8:
Page 32 - alterations to the text of item 02.
Page 32 - alterations in the exemplary screens.
Chapter 9:
Page 37 - alterations to the text of item 02.
Chapter 11:
Page 47 - alteration in the exemplary screens with the inclusion of the “Additional Info” field.
Page 47 - alterations to the text of items 02 and 03.
Page 49 – renumbering of the items present in the chapter together with the exclusion of item 08 present in version 3.1.
Pages 49 and 50 - alteration in the exemplary screens with the inclusion of the “Additional Info” field.
Page 51 – inclusion of new item number 14 – “The PSP cannot save the Pix key nor should it make available the option to save the Pix key linked to the payment of the dynamic QR Code.”
Page 51 - alteration in the exemplary screens.
Chapter 12:
Pages 53 - alteration in the exemplary screens
Chapter 13:
Page 57 - alteration in the exemplary screens with the inclusion of the “Additional Info” field.
New Chapter 14: Integration with Contact List - Functionality that allows the user to easily identify people in the contact list of their smartphone who have Pix keys.
Annex 1:
Page 66: alteration to the text present in item 1 (Pix with Pix Key).
Page 69: alteration to the text present in item 2 (Refund).
Minor formatting adjustments.
Date Version Description of Changes

143
03/2021 4.1 • Chapter 11:

Page 47: alteration to the text of item 01 - The value (If the receiving user informs that the value can be altered using the “Value alteration modality” field, as defined in the Pix Initiation Standards Manual, the payer user must be allowed to edit the value. Otherwise, the value cannot be editable).
Page 47: alteration to the text of item 02 - Payer user can cancel the payment, but cannot edit the QR Code data, except for the value (if allowed by the receiving user) and the field requesting information from the payer (if any).
Minor formatting adjustments.
Date Version Description of Changes

144
04/2021 4.2 • Chapter 2:

Page 8 – Insertion of new item 10 regarding the participant’s obligation to make available, in the Pix environment, a shortcut (icon, button, or text with hyperlink) through which the user can, upon clicking, be directed to the service channel made available by the PSP for handling complaints involving Pix;
Page 8 - Insertion of new item 11 regarding the participant’s obligation to make available, in the Pix environment, a shortcut (icon, button, or text with hyperlink) through which the user can, upon clicking, be directed to the Central Bank of Brazil’s Internet page to register a complaint (https://www.bcb.gov.br/acessoinformacao/registrar_reclamacao);
Page 8 – Insertion of new item 12 regarding the recommendation to the participant to make it clear to the user that, before making a complaint to the Central Bank of Brazil, they should try to resolve the problem with their own PSP;
Page 8 – Inclusion of figures representing mobile phone screens containing the insertion of an icon that, when activated, directs the user to register a complaint;
Page 9 – Item 13 (item 10 in version 4.1) – insertion of the obligation to include, in the transaction completion notification, information regarding the fee charged, if permitted under current regulation;
Page 9 – Item 14 (item 11 in version 4.1) – insertion of the obligation to include, in the transaction completion notification, information regarding the fee charged, if permitted under current regulation.
Chapter 11:
Page 52 – item 15 – mandatory – insertion of the obligation that when the payer user schedules the payment of a Dynamic QR Code with maturity, the PSP must make available to them the scheduling receipt as well as consultation of scheduled transactions;
Page 52 – item 16 – mandatory – insertion of the obligation that the user must be offered the functionality to cancel the scheduled transaction;
Page 52 – item 17 – mandatory – insertion of the obligation that if the scheduled transaction is cancelled due to insufficient balance in the user’s account, the user must receive a notification of the cancellation. The method of sending the notification is at the free choice of the PSP. If the notification is via push, part of the information, at the PSP’s choice, may be detailed when the user clicks on the notification.
Chapter 12:
Page 54 – Item 02 – recommended – recommendation to the PSP to send a notification one day before the date of the debit of the Scheduled Pix informing the user regarding the need for account balance;
Page 54 – item 05 – mandatory – insertion of the obligation that if the scheduled transaction is cancelled due to insufficient balance in the user’s account, the user must receive a notification of the cancellation. The method of sending the notification is at the free choice of the PSP. If the notification is via push, part of the information, at the PSP’s choice, may be detailed when the user clicks on the notification;
Page 54 – item 06 – mandatory – insertion of the obligation that the user must be offered the functionality to cancel the scheduled transaction.
Annex I:
Page 67 – Annex I – Insertion of items 05 and 06, regarding the items to be evaluated in the process of verifying the adherence of solutions to end users.
Minor formatting and reference adjustments to the items contained in the Manual.
Date Version Description of Changes

145
05/2021 4.3 • Chapter 02:

Page 08 – consolidation of items 11 and 12 into a new mandatory item 11, which states that “It must be made available, in the Pix environment, next to the shortcut to the participant’s service channel, an informative message to the user so that they can register a complaint on the Central Bank of Brazil’s website (https://www.bcb.gov.br/acessoinformacao/registrar_reclamacao) if the occurrence is not resolved by the PSP.
Page 08 – Alteration of the screens representing the user experience when forwarding to register a complaint.
Chapter 12:
Page 54 – Alteration of the screens representing the user experience when scheduling a Pix.
Page 54 - insertion of new item 02: “The option to schedule recurring payments may be made available to the payer user.”
Annex I:
Page 67 - Alteration of Annex I (item 06) due to the alterations promoted in Chapter 02 - General Obligations and Recommendations
Minor formatting and reference adjustments to the items contained in the Manual.
Date Version Description of Changes

146
07/2021 4.4 • Chapter 2:

Page 09 – item 12: insertion of information regarding the notification of settlement of a scheduled transaction. “In Scheduled Pix transactions, the receiving user must receive notification of the transaction settlement, with the method of sending the notification at the free choice of the PSP. The notification must contain the same information specified for Pix transactions with key or manual data entry, and preferably be sent during daytime hours.”
Page 09 – item 13: insertion of information regarding the notification of settlement of a scheduled transaction. “In Pix Collection transactions for payment with maturity where there is scheduling, the receiving user must receive notification of the transaction settlement, with the method of sending the notification at the free choice of the PSP. The notification must contain the same information specified for Pix transactions with QR Code, and preferably be sent during daytime hours.”
Chapter 3:
Page 16 – item 11: insertion of information regarding the notification of settlement of a scheduled transaction. “In Scheduled Pix transactions, the payer user must receive notification of the transaction settlement, with the method of sending the notification at the free choice of the PSP. The notification must contain the same information specified above, and preferably be sent during daytime hours.”
Chapter 4:
Page 21 – item 07: insertion of information regarding the time of notification of settlement of a scheduled transaction. “In Scheduled Pix transactions, the payer user must receive notification of the transaction settlement, with the method of sending the notification at the free choice of the PSP. The notification must contain the same information specified above, and preferably be sent during daytime hours.”
Chapter 11:
Page 54 – item 12: insertion of information regarding the notification of settlement of a scheduled transaction. “In Pix Collection transactions for payment with maturity where there is scheduling, the payer user must receive notification of the transaction settlement, with the method of sending the notification at the free choice of the PSP. The notification must contain the same information specified above, and preferably be sent during daytime hours.”
Minor formatting adjustments.
Date Version Description of Changes

147
08/2021 5.0 • Index:

Inclusion of Chapter 15 – “Payment Transaction Initiation Services in Pix” and adjustments of the numbering of subsequent chapters;
Inclusion of Chapter 17 – “Accessibility in Pix” and adjustments of the numbering of subsequent chapters;
Inclusion of Annex II – “Current implementation deadlines regarding the mandatory functionalities of the Minimum Requirements for User Experience.”;
Chapter 1:
Page 04: new fourth paragraph dedicated to Payment Transaction Initiation Service Providers (PSIs) and new fifth paragraph regarding non-discriminatory treatment of users regarding accessibility;
Chapter 2:
Page 07 – item 07: correction of indications in the exemplary screens;
Page 10 – item 14: new wording (insertion of PSI as participant);
Chapter 3:
Page 16 – item 12: exclusion of the indication of the item on the exemplary screen;
Chapter 7:
Page 32 - item 05: new recommended item (transactions initiated by PSI);
Chapter 9:
Page 40 - item 05: exclusion of the indications of the item on the exemplary screen;
Chapter 12:
Page 55 – item 01: new mandatory item (scheduling option);
Page 55 – item 03: new wording for the item (consultation of schedules);
Page 55 – items 02, 04, and 05: renumbering of mandatory items;
Page 55 – items 06 and 07: renumbering of recommended items;
Inclusion of Chapter 15
Pages 62 to 65 – “Payment Transaction Initiation Service in Pix” and adjustment of the numbering of subsequent chapters;
Inclusion of Chapter 17
Pages 71 and 72 - “Accessibility in Pix” and adjustments of the numbering of subsequent chapters;
Annex I:
Page 77 – new mandatory item (Scheduled Pix);
Alterations to the interfaces of the exemplary screens.
Minor formatting adjustments.
Date Version Description of Changes

148
09/2021 6.0 • Index:

Inclusion of new Chapter 14 - “Pix Cash and Pix Change” and adjustments of the numbering of subsequent chapters;
Repositioning of the chapter “Integration with Contact List”, which now takes place after Chapter 15 - “Payment Transaction Initiation Services in Pix”;
Chapter 02:
Page 07 - item 07: inclusion of the nomenclatures “Pix Cash” and “Pix Change”;
Page 08 - item 11: exclusion of the URL and link of the Central Bank page on the exemplary screen, and repositioning of the informative message about registering complaints on the Central Bank’s website, after the shortcut to the participant’s service channel;
Chapter 03:
Page 12 - item 02: inclusion of the DDI code +55 as the standard for the mobile phone number key;
Chapter 07:
Page 32 - item 01: inclusion of withdrawals in the list of Pix transactions;
Chapter 13:
Page 57 - item 02: inclusion of cash withdrawals as an option for quick and easy access to the user in the PSP’s mobile banking application;
Inclusion of the new Chapter 14:
Pages 60 to 67: adjustment of the numbering of subsequent chapters and pages;
Adjustment of the numbering of subsequent chapters and pages;
Page 85: alteration to the text of item 01 (chapter Statement), including withdrawals among Pix transactions;
Alterations to the interfaces of the exemplary screens.
Minor formatting adjustments.
Date Version Description of Changes

149
12/2021 6.2 • Chapter 07:

Page 32 - inclusion of new item 02: obligation regarding the form of posting Pix Change transactions in statements and renumbering of subsequent items.
Page 32 - alteration of the exemplary screen associated with item 01, which also becomes associated with the new item 02.
Chapter 10:
Page 46 - items 01 and 02: inclusion of limit management by type of beneficiary.
Page 46 - item 02: change of the start of the nighttime period that can be altered by the user.
Page 51 - item 08: change of the start of the nighttime period that can be altered by the user.
Page 51 - Alteration of the exemplary screen associated with item 8.
Chapter 14:
Page 66 - alteration of the term “offer” to “make available”;
Page 67 - item 01: adjustments to the wording (inclusion of banking correspondents);
Page 67 - alteration of the exemplary screens associated with item 01;
Page 68 - item 03: adjustments to the wording (information regarding the locations where Pix Cash and Pix Change are made available);
Page 68 - item 04: adjustments to the wording (substitution of “service” by “Pix Cash and/or Pix Change”);
Page 69 - item 05: adjustments to the wording (substitution of “service” by “Pix Cash and/or Pix Change”);
Page 69 - adjustment of the screen associated with item 05;
Page 70 - item 11: adjustments to the wording (substitution of “service” by “Pix Cash and/or Pix Change”) and exclusion of the “final transaction value”;
Page 71 - item 14: adjustments to the wording (substitution of “service” by “Pix Cash and/or Pix Change”), inclusion of the term “name” as information associated with the receiving PSP, and exclusion of the “final transaction value”; and
Page 72 - item 16: adjustments to the wording (inclusion of the term “name” as information associated with the receiving PSP).
Annex I:
Page 91 - alteration of item 01 of the Chapter “My Pix Limits”
Alterations to the interfaces of the exemplary screens.
Minor formatting adjustments.
10/2021 6.1 • Index:
Renumbering of the pages from Chapter 10 - My Limits, due to alterations and insertion of new content.
Chapter 10:
Pages 45 to 53 - inclusion of new functionalities that allow the user to consult and manage Pix limits by period and by transaction, including for Pix Cash and Pix Change, and to register accounts with differentiated limits.
Annex I:
Page 91 - inclusion of item 01, page 46, of Chapter 10 - My Limits.
Alterations to the interfaces of the exemplary screens.
Minor formatting adjustments.
Date Version Description of Changes

150
10/2022 6.3 • Index:

Renumbering of pages starting from Chapter 3 - Pix with Pix Key, due to alterations and insertion of new content.
Exclusion of Annex II (Chapter 20), given that the implementation deadlines for mandatory functionalities will be regulated by an Instruction Normative, published with each update of the minimum requirements for User Experience.
Chapter 02:
Page 8 - item 10: inclusion of reference to the Special Return Mechanism, which must be activated through the customer service channel made available by the PSP;
Page 9 - item 12: exclusion of the payer's PSP name as minimum information in notifications to the receiver of Pix transactions initiated with a key or manual data entry;
Page 9 - item 12: alterations regarding the sanitization of the "Description" field;
Page 9 - item 13: exclusion of the payer's PSP name as minimum information in notifications to the receiver of Pix transactions initiated with a key or manual data entry;
Page 10 - item 15 (new): prohibition of displaying the Pix Key among the data returned by the DICT, nor saving or making available the option to save, when the txId is filled in.
Chapter 03:
Page 12 - item 03: alterations regarding the sanitization of the "Description" field;
Page 14 - item 06: return of the receiver's PSP name information becomes optional in transactions initiated by key;
Page 14 - item 06: return of the Pix Key information becomes mandatory in transactions initiated by key;
Page 15 - item 09: adjustment in the text so that, in error messages during settlement, the actual reason for the non-processing of the transaction is highlighted;
Page 16 - item 11: receiver's PSP name ceases to be minimum information in notifications; and
Page 16 - item 12: inclusion of the receiver's CPF (masked or not) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side on the receipt, which must be made available to the payer and receiver users.
Chapter 04
Page 19 - item 01: prohibition of displaying the names of special liquidating participants in the list of participating institutions and clarifications regarding the number associated with each PSP;
Page 19 - exemplary screen of item 01: inclusion of the account type "payment account";
Page 19 - item 03: alterations regarding the sanitization of the "Description" field;
Page 20 - item 05: adjustment in the text so that, in error messages during settlement, the actual reason for the non-processing of the transaction is highlighted;
Page 21 - item 07: obligation to provide the receiver's CPF (masked)/CNPJ, in notifications of transactions initiated by manual entry;
Page 21 - item 07: receiver's PSP name ceases to be minimum information in notifications;
Page 21 - item 08: inclusion of the receiver's CPF (masked or not) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side on the receipt, which must be made available to the payer and receiver users; and
Page 21 - item 08: alterations regarding the sanitization of the "Description" field.
Data Version Description of Changes

151
10/2022 6.3 • Chapter 05:

Page 25 - item 07 (item 08 of the previous version): provision of the Copy QR Code option to enable the Pix Copy and Paste functionality ceases to be a recommendation and becomes a mandatory requirement.
Chapter 06:
Page 27 - item 01: return of the receiver's PSP name information becomes optional and is at the discretion of the participant;
Page 27 - item 01: inclusion of the mandatory "Cancel" option, before confirming the transaction (already present in the exemplary screen associated with the item);
Page 27 - item 01: prohibition of making the "Description" field ("informacoesEntreUsuarios" of pacs.008) available for the payer user to fill in during transactions initiated by static QR Code;
Page 29 - item 07: adjustments in the text regarding errors of non-existent key in the static QR Code;
Page 30 - item 09: adjustment in the text so that, in error messages during settlement, the actual reason for the non-processing of the transaction is highlighted;
Page 31 - item 12: receiver's PSP name ceases to be minimum information in notifications; and
Page 31 - item 12: inclusion of the receiver's CPF (masked or not) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side, and the "Identifier" field (TxId), whenever filled in, as minimum receipt information, which must be made available to the payer and receiver users.
Chapter 07:
Page 33 - item 05: adjustments in the text regarding the retrieval of receipts, excluding the minimum information, which are specified in the items about receipts for each initiation method.
Chapter 08:
Page 35 - item 02: inclusion of the transaction value among the minimum information that the user must view to be able to select the return option;
Page 35 - item 03: item ceases to be recommended and becomes mandatory;
Page 36 - item 07: adjustments in the text to include the recipient's CPF (masked or not) / CNPJ information and the return transaction ID on the receipt, in adherence to the exemplary screen of the item;
Page 36 - item 07: alterations regarding the sanitization of the "Description" field;
Page 37 - item 09: adjustments in the text, incorporating part of the content of the old item 11 of the previous version, consolidating all guidelines regarding error messages in settlement of return transactions;
Page 38 - item 11 (new): obligation that, in the case of precautionary block, the receiver's PSP must make available the possibility of returning the full amount of resources by the receiver user;
Page 38 - item 12 (new): obligation for the receiver user of the original transaction to be immediately notified about the precautionary block, and minimum information of the notification;
Page 38 - item 13 (new): obligation for the receiver user of the original transaction to be immediately notified about the block resulting from the opening of an infraction notification associated with a return request, and minimum information of the notification;
Page 38 - item 14 (new): obligation for the receiver user of the original transaction to be immediately notified about the release of resources in their account after a block has been carried out, and minimum information of the notification;
Page 38 - item 15 (new): obligation for the receiver user of the original transaction to be immediately notified, if the blocked resources have been effectively returned, and minimum information of the notification; and
Data Version Description of Changes

152
10/2022 6.3 - Page 38 - item 16 (new): obligation for the payer user of the original transaction to be immediately notified about the credit in their account resulting from a return, and minimum information of the notification;

Chapter 09:
Page 40 - item 02: the information of the PSP to which the key is linked ceases to be minimum information viewed by the payer user who has knowledge of the key, and adjustments in the text;
Page 42 - item 08: alteration of the deadline for finalizing the possession claim process from 14 to 30 days;
Page 43 - item 10: adjustments regarding the communication of the start of the portability process and in the exemplary screen; and
Page 45 - item 12: adjustments in the text regarding messages in case of communication failure with the DICT for registration, deletion, alteration, portability request or key claim.
Chapter 11:
Page 56 - item 01: prohibition of returning the receiver's branch number and account number information to the payer user, as already occurs for payment transactions via static QR code;
Page 56 - item 01: return of the receiver's PSP name information before confirming the immediate payment becomes optional and is at the discretion of the participant;
Page 56 - item 01: prohibition of making the "Description" field ("informacoesEntreUsuarios" of pacs.008) available for the payer user to fill in, in immediate payment transactions initiated by dynamic QR Code;
Page 57 - item 03: insertion of the "due date" field on the screen returned after reading a Pix Cobrança for payment with due date and alterations regarding the indication of the intended payment date;
Page 57 - item 03: prohibition of returning the receiver's branch number and account number information to the payer user, as already occurs for payment transactions via static QR code;
Page 57 - item 03: return of the receiver's PSP name information before confirming the payment with due date becomes optional and is at the discretion of the participant;
Page 57 - item 03: adjustments in the text regarding the "infoAdicionais" field;
Page 57 - item 03: prohibition of making the "Description" field ("informacoesEntreUsuarios" of pacs.008) available for the payer user to fill in, in payment transactions with due date initiated by dynamic QR Code;
Page 58 - item 06: item ceases to be recommended and becomes mandatory;
Page 59 - item 09: adjustment in the text of the message in case of expiration of the dynamic QR Code;
Page 60 - item 11: adjustment in the text so that, in error messages during settlement, the actual reason for the non-processing of the transaction is highlighted;
Page 61 - item 12: receiver's PSP name ceases to be minimum information in notifications;
Page 61 - item 13: inclusion of the receiver's CPF (masked or not) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side, and the "Identifier" field (TxId), whenever filled in on the receipt, which must be made available to the payer and receiver users; and
Page 61 - item 17: adjustments in the text regarding the non-effectuation of scheduled transaction, due to insufficient balance in the user's account.
Data Version Description of Changes

153
10/2022 6.3 Chapter 12:

Page 63 - item 01: adjustment in the text, clarifying that payments can be scheduled for non-business days;
Page 63 - item 02: adjustments in the text and exemplary screen, so that the receipt explicitly highlights that it refers to a Pix transaction scheduling.
Page 63 - item 05: adjustments in the text regarding the non-effectuation of scheduled transaction, due to insufficient balance in the user's account.
Page 63 - item 05: adjustments in the text regarding the non-effectuation of scheduled transaction, due to insufficient balance in the user's account.
Chapter 14:
Page 71 - item 06: alterations regarding the sanitization of the "Conditions for making the withdrawal service available" field;
Page 72 - item 11: alterations regarding the sanitization of the "infoAdicionais" field;
Page 73 - item 14: alterations regarding the sanitization of the "infoAdicionais" field;
Page 74 - item 16: alterations regarding the sanitization of the "infoAdicionais" field; and
Page 75 - item 19: alterations in the minimum information of the receipts of Pix Withdrawal and Pix Change transactions.
Chapter 15:
Page 81 - item 15 (new): obligation for the payment transaction initiation service provider to comply with the requirements regarding the set of data that must be informed to the payer user before confirming the payment, for each initiation method;
Page 82 - item 16 (new): standardization of the set of data that must be informed to the payer user by the payment transaction initiation service provider and by the participant holding the transactional account, in cases where the payment transaction initiation service provider has all the receiver user information.
Chapter 17:
Page 87: adjustments of the payload information on the exemplary screen; and
Page 88 - item 02 (new): obligation to display the dynamic QR code payload information, for payments with due date in Internet Banking.
Annex I
Page 8: adjustments in item 10 - inclusion of reference to the Special Return Mechanism;
Page 12: alteration of item 3 - sanitization of the "Description" field;
Page 14: alteration of item 6 - return of the receiver's PSP name information becomes optional in transactions initiated by key;
Page 16: alteration of item 12 - obligation of the receiver's CPF (masked or not) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side on the receipt, which must be made available to the payer and receiver users, and alterations regarding the sanitization of the "Description" field;
Page 19: alteration of item 1 - prohibition of displaying the names of special liquidating participants in the list of participating institutions and clarifications regarding the number associated with each PSP;
Page 21: alteration of item 8 - obligation of the receiver's CPF (masked) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side on the receipt, which must be made available to the payer and receiver users, and alterations regarding the sanitization of the "Description" field;
Data Version Description of Changes

154
10/2022 6.3 - Page 25: alteration of item 7 (item 08 of the previous version) - provision of the Copy QR Code option to enable the Pix Copy and Paste functionality ceases to be a recommendation and becomes a mandatory requirement;

Page 31 - item 12: inclusion of the receiver's CPF (masked or not) / CNPJ information and the information (name, CPF (masked or not) / CNPJ and PSP name) of the payer side on the receipt, which must be made available to the payer and receiver users;
Page 31 - item 12: inclusion of the "Identifier" field (TxId) message information on the receipt, which must be made available to the payer and receiver users;
Page 35: alteration of item 2 - inclusion of the transaction value among the minimum information that the user must view to select the return option;
Page 40: alteration of item 2 - the information of the PSP to which the key is linked ceases to be minimum information viewed by the payer user who has knowledge of the key; and
Page 63: adjustment in item 1 - scheduling must also be made available for payments on non-business days.
Alterations in the interfaces of the exemplary screens.
Minor formatting adjustments.
07/2023 6.4 • Chapter 9:
Page 45: alterations in item 14 - obligation to inform the user, in attempts to register, delete, alter, portability or claim keys during hours when the participant does not make these functionalities available, about the deadline for effectuation or the hour when the functionality will be available.
Chapter 10:
Page 47: adjustments in item 1 - end of limits per transaction and new functionality for registering beneficiaries with differentiated limits; obligation to make the "My Pix Limits" menu available in the Pix environment and at least one of the specific limit registration functionalities (accounts and beneficiaries);
Page 47: adjustments in item 2 - "My Pix Limits" menu must contain information about limits per period in transactions for individuals and companies, and about beneficiary registration, if this functionality is made available by the PSP; obligation to make available at least one of the specific limit registration functionalities (accounts and beneficiaries)
Page 47: alterations in item 2 - Pix Withdrawal and Pix Change limits were changed from R$ 500.00 to R$ 3,000.00 in the daytime period and from R$ 100.00 to R$ 1,000.00 in the nighttime period;
Page 47: alteration in item 2 - the schedule management functionality ceases to be mandatory;
Page 48: item 3 - adjustment in the exemplary screen; exclusion of the inquiry and editing of limits per transaction;
Page 48: adjustments in item 4 - greater clarity regarding the need for PSP approval in requests for limits higher than those made available for alterations;
Page 49: adjustments in item 5 - greater clarity regarding the information of the processing deadline for any request for limit increase and the eventual need for PSP approval, in cases where the requested limit is higher than the value of the parameter regulated by the BCB, according to period (daytime or nighttime) and receiver user (individual or legal entity);
Data Version Description of Changes

155
07/2023 6.4 - Page 51: alterations in item 7 - greater clarity regarding the impossibility of the user requesting an increase in Pix Withdrawal Pix Change limits to values higher than those regulated by the BCB; Pix Withdrawal and Pix Change limits were changed from R$ 500.00 to R$ 3,000.00 in the daytime period and from R$ 100.00 to R$ 1,000.00 in the nighttime period;

Page 52: alteration in item 8 (old item 9) - the account registration functionality no longer allows differentiated limit per transaction;
Page 52: adjustments in item 8 (old item 9) - greater clarity regarding the option to make available the account registration functionality with differentiated limits and possibility of using a limit applicable to all registered accounts; and alteration in the exemplary screen, considering a single daily limit for each registered account.
Page 52: adjustments in item 10 (old item 11) - the account registration functionality must allow easy alteration of the registered limits;
Page 53: inclusion of items 11, 12 and 13 - requirements for the beneficiary registration functionality, if made available by the PSP;
Page 54: new item 14: obligation to inform the user about eventual impossibilities of registering specific limits for accounts and beneficiaries, if there is incompatibility with pre-registered limits, if the PSP makes available both limit registration functionalities (accounts and beneficiaries)
Page 55: New item 15 (old item 8)
Page 55: New item 16 - obligation to inform the user about the deadline for altering the start of the nighttime period, if the PSP makes available this functionality.
Annex I:
Page 47: adjustments in item 1 - end of limits per transaction and new functionality for registering beneficiaries with differentiated limits; obligation to make the "My Pix Limits" menu available in the Pix environment and at least one of the specific limit registration functionalities (accounts and beneficiaries);
Alterations in the interfaces of the exemplary screens.
Minor formatting adjustments.
Data Version Description of Changes

156
08/2024 7.0 • Index:

Repositioning of the chapter "Immediate or Due Payment via Dynamic QR Code" from chapter 11 to chapter 07 and adjustments of the numbering of subsequent chapters;
Inclusion of the new chapter 15 – "Automatic Pix" and adjustments of the numbering of subsequent chapters.
Chapter 01:
Page 04 - Introduction: alteration in the mention of the chapter number that deals with the payment transaction initiation service (from chapter 15 to chapter 16).
Chapter 02:
Page 07 – item 07: inclusion of Scheduled Pix and Automatic Pix in the mandatory nomenclatures;
Page 08 – item 10: adjustments in the wording to highlight the obligation of easy and direct access to the customer service channel for the purpose of registering complaints within the scope of Pix;
Page 09 – items 12 and 13: alteration of the recipient of the requirements (from the payer user's PSP to the receiver user's PSP);
Page 10 – item 16 (new): inclusion of the obligation to present a "check" type icon on payment receipts;
Page 10 – item 17 (new): inclusion of the obligation to present the information and icons ("check" or "calendar clock") present on the payment and scheduling completion screens on their respective receipts.
Chapter 03:
Page 16 – item 11: adjustments in the wording (presentation of information in a more summarized way, with migration of part of the text to chapter 12 – "Scheduled Pix", with alterations).
Chapter 04:
Page 19 – item 02: adjustments in the wording (exclusion of "if the PSP has this information (for example, if the receiver user is their client");
Page 21 – item 07: adjustments in the wording (presentation of information in a more summarized way, with migration of part of the text to chapter 12 – "Scheduled Pix", with alterations, and replacement of CPF/CNPJ by the receiver's name).
Chapter 07:
Page 38 – item 12: adjustments in the wording (presentation of information in a more summarized way, with migration of part of the text to chapter 12 – "Scheduled Pix", with alterations);
Page 38 – item 13: adjustments in the wording (references to the dynamic QR Code payload and the screen with illustrative example);
Migration of items 15, 16 and 17 to chapter 12 – "Scheduled Pix" (with alterations).
Chapter 08:
Page 40 – item 03 (new): inclusion of the obligation to identify Scheduled Pix on the account statement and, if made available, on the Pix statement;
Page 40 – item 04 (new): inclusion of the obligation to identify Automatic Pix on the account statement and, if made available, on the Pix statement, and adjustments of the numbering of subsequent items;
Page 40 – item 07: inclusion of recommendation to retrieve scheduling receipts in the statement functionality;
Page 40: inclusion of examples of Scheduled Pix, Recurring Scheduled Pix and Automatic Pix transactions on the illustrative screens.
Chapter 11:
Page 53 – exclusion of "per period" and inclusion of mention to Scheduled Pix and Automatic Pix in the chapter subtitle;
Page 54 – item 01: exclusion of "per period" and inclusion of mention to Scheduled Pix and Automatic Pix;
Page 54 – Item 02: exclusion of "per period (daytime and nighttime)" in the topic "Pix for companies" and inclusion of information relating to Scheduled Pix and Automatic Pix. Addition of the term "daily" to the limits and inclusion of phrase to refer to the option of differentiated global daily limit in the information about beneficiary registration and account registration;
Page 55 – Item 03: inclusion of Scheduled Pix and Automatic Pix in the inquiry and alteration of limits;
Page 55 – Item 04: inclusion of Scheduled Pix and Automatic Pix in the permission to request limit increase;
Page 56 – Item 05: inclusion of exception in the 24 to 48 hours deadline for processing limit increase request in the case of Automatic Pix.
Data Version Description of Changes

157
08/2024 7.0 • Chapter 11:

Page 56 - Item 06 (new): inclusion of the obligation to communicate to the payer user the 8-hour processing period for the limit increase request for Automatic Pix, subject to PSP approval, and adjustments to the numbering of subsequent items;
Page 57 – Item 08 (new): inclusion of the obligation to communicate to the payer user if scheduled limit reduction requests for Scheduled Pix result in the impossibility of settling already scheduled transactions, inclusion of an illustrative screen, and adjustments to the numbering of subsequent items;
Page 59 – Item 10: insertion of the term “daily” in the reference to the differentiated limit applicable to all registered accounts;
Page 60 – Item 13: insertion of the term “daily” in the reference to the differentiated limit applicable to all registered beneficiaries;
Pages 54, 55, 59, 60 and 62: adjustments to screens to include Scheduled Pix and Automatic Pix.
Chapter 12:
Pages 64 to 69: general reformulation of the chapter, with wording adjustments and inclusion of new items to address recurring Scheduled Pix, the specific limit for scheduled transactions, and improvements made to scheduling receipts, as well as to consider information regarding the sending of notification after the settlement of the scheduled transaction previously existing in Chapter 03 – “Pix with Pix Key”, Chapter 04 – “Pix with manual insertion of transactional account data”, and Chapter 07 – “Immediate payment or with maturity through dynamic QR Code”.
Chapter 15 (new):
– Inclusion of the new chapter “Automatic Pix” and adjustments to the numbering of subsequent chapters and pages.
Chapter 16:
Standardization of the term “payment transaction initiation service provider (PSI)” throughout the chapter;
Exclusion of items 11, 13, 17 and 18 from version 6.4;
Renumbering of items 12, 14, 15, 16, from version 6.4, to 14, 11, 12, 13, in version 7.0, respectively;
Page 105 – Item 01: inclusion of Scheduled Pix and Automatic Pix in the mandatory nomenclatures of PSIs;
Page 107 – Item 14: wording adjustments (need to comply with the obligations provided in the “Scheduled Pix” chapter, if the PSI offers single and/or recurring scheduling);
Page 108 – Item 15 (new): inclusion of the obligation to make Automatic Pix functionalities available, if the PSI offers the product;
Page 108 – Item 16 (new): inclusion of recommendation regarding the offer of Scheduled Pix by the PSI;
Page 108 – Item 17 (new): inclusion of recommendation regarding the offer of Automatic Pix by the PSI;
Page 108 – Item 18 (new): inclusion of recommendation regarding the availability of the functionality to query the history of Automatic Pix authorizations.
Chapter 20 (Annex I):
Adjustments to page and item numbering cited;
Page 120: Changes in Item 10 of the chapter “General Obligations and Recommendations” – wording adjustments to highlight the obligation of easy and direct access to the service channel for the purpose of registering complaints within the scope of Pix;
Page 124: Changes in Item 01 of the chapter “My Pix Limits” – exclusion of “by period” and inclusion of reference to Scheduled Pix and Automatic Pix;
Page 124: Change in Item 01 of the chapter “Scheduled Pix” – replacement of the word “payments” with “Pix transactions”;
Pages 124 and 125: Inclusion of the items to be evaluated in the compliance verification process regarding the chapter “Automatic Pix”.
Changes in the interfaces of the illustrative screens.
Minor formatting adjustments.
Data Version Description of Changes

158
02/2025 7.1 • Index:

Inclusion of the new Chapter 16 – “MED Self-Service” and adjustments to the numbering of subsequent chapters.
Chapter 01:
Page 04 – Introduction: change in the applicability of the obligations contained in this document from applications intended for physical persons to natural persons;
Page 04 – Introduction: change in the reference to the chapter number dealing with the payment transaction initiation service (from Chapter 16 to Chapter 17).
Chapter 02:
Page 06 – Item 04: change of the term physical person to natural person in the reference to the cost of Pix.
Chapter 03:
Page 13 – Item 05: inclusion of the return of blocked key when there is a key query in the DICT and the term key unavailability as a message to be informed to the user;
Page 14 – Item 06: exclusion of the word “hidden” in the reference to the “masked CPF” as data of the receiving user to be presented for verification. Insertion of a phrase to make it clear that there shall be no masking of the Pix key in the DICT query return, in order to allow the verification of the key data by the payer user before confirming the payment;
Page 16 – Item 12: formatting adjustment of the text regarding minimum data to be presented on the payment receipt, which is now presented in topics. Inclusion of the settlement date as minimum information to be presented.
Chapter 04:
Page 21 – Item 08: formatting adjustment of the text regarding minimum data to be presented on the payment receipt, which is now presented in topics. Inclusion of the settlement date as minimum information to be presented.
Chapter 06:
Page 29 – Item 07: text adjustment and inclusion of the QR Code reading error due to blocked key and the term key unavailable as a message to be informed to the user;
Page 31 – Item 12: formatting adjustment of the text regarding minimum data to be presented on the payment receipt, which is now presented in topics. Inclusion of the settlement date as minimum information to be presented. Inclusion of a phrase regarding the prohibition of displaying the Pix key linked to the static QR Code and the bank data (branch and account) of the recipient on the payment receipt, when the “Identifier” (TxId) field is filled.
Chapter 07:
Page 36 – exclusion of one of the illustrative screens;
Page 36 – Item 08: inclusion of the QR Code reading error due to blocked key;
Page 38 – Item 13: formatting adjustment of the text regarding minimum data to be presented on the payment receipt, which is now presented in topics. Inclusion of the settlement date as minimum information to be presented. Exclusion of the phrase “whenever it is filled” associated with the message of the “Identifier” (TxId) field. Inclusion of a phrase regarding the prohibition of displaying the Pix key linked to the dynamic QR Code and the bank data (branch and account) of the recipient on the payment receipt.
Chapter 08:
Page 40 – Item 03: inclusion of the specification “future postings” in the account statement or Pix statement, where Scheduled Pix transactions will be made available. Insertion of the possibility to identify Scheduled Pix in a specific query menu for schedules.
Chapter 10:
Page 47 – Item 02: exclusion of the phrase “in case of Pix initiated by QR Code” in a sentence that allows, at the discretion of the payer PSP, the display of the name of the payment service provider to which the key is linked.
Data Version Description of Changes

159
02/2025 7.1 • Chapter 12:

Page 64 – Item 04: inclusion of the specification “with maturity” in the phrase “for single schedules made through the dynamic QR code”. Exclusion of the phrases “whenever it is filled” and “according to the type of payment”;
Page 64 – Item 05: inclusion of “Scheduled Pix” in the reference to the daily limit. Replacement of scheduled date with date expected for payment;
Page 65 – Item 07: replacement of the quantity of repetitions with quantity of payments;
Page 65 – Item 08: replacement of the quantity of repetitions with quantity of payments;
Page 65 – Item 09: replacement of the quantity of repetitions with quantity of payments;
Page 65 – Item 10: exclusion of the phrase “at any time” and inclusion of the information “deadline for cancellation” of schedule;
Page 66 – Item 12: replacement of the quantity of repetitions with quantity of payments;
Page 67 – Item 16: wording adjustments and inclusion of the phrase “for recurring schedules, the verification of the available limit must be done at least for the nearest scheduled date”;
Page 68 – Item 20: replacement of the quantity of repetitions with quantity of payments;
Page 69 – Item 23: inclusion of “Scheduled” to specify the type of Pix transactions.
Chapter 15:
Page 85 – Item 08: change of Item 15 to Item 16 in the reference to the continuation of the authorization journey;
Page 86 – Item 10: change of Items 15 and 18 to Items 16 and 19 in the reference to the screens with authorization information;
Page 87 – Item 12: change of Item 15 to Item 16 in the reference to the continuation of the authorization journey;
Page 87 – Item 13 (new): inclusion of the obligation to allow the user to complete the payment journey, without advancing to the step of offering Automatic Pix for future payments, in case of error in reading only the part of the QR Code related to recurrence;
Page 88 – Item 15: change of Item 15 to Item 16 in the reference to the continuation of the authorization journey;
Page 91 – Item 19: inclusion of information to clarify that “the value of the immediate payment is not subject to the maximum value established by the user”. Exclusion of a paragraph that was transferred to the new Item 20, on page 92;
Page 92 – Item 20 (new): relocation of paragraph from Item 19 citing the need to state the information that the first payment is immediate and inclusion of the obligation of a check box field for the user to attest knowledge that they are authorizing future recurring payments;
Page 95 – Item 31: wording adjustment to replace “of” with “of a”;
Page 98 – Item 39: inclusion of information to recommend that “if the maximum value is changed to a value lower than that of an already scheduled payment, the payer PSP may inform the payer user and offer the possibility of canceling the scheduled payment”;
Page 99 – Item 40: inclusion of the settlement date as minimum information to be presented;
Page 102 – Item 48: inclusion of information to establish that “when settlement occurs between midnight and 6:00 AM, the notification should be sent, preferably, after this time”;
Page 103 – Item 53: inclusion of the obligation to send notification about the result of the authorization processing in the situation where the maximum time limit that the payer PSP must wait for the completion of the authorization process by the recipient PSP has been exceeded;
Page 103 – Item 57 (new): inclusion of recommendation to send notification about the possibility of changing the maximum value up to two days before the expected settlement date and the need to contact the recipient, in order to enable payment in the same cycle, in cases where a schedule was not executed due to exceeding the maximum value established for the authorization.
Chapter 16 (new):
– Inclusion of the new chapter “MED Self-Service” and adjustments to the numbering of subsequent chapters and pages.
Chapter 21 (Annex I):
Adjustments to page and item numbering cited;
Page 136: Inclusion of the items to be evaluated in the compliance verification process regarding the chapter “MED Self-Service”.
Changes in the interfaces of the illustrative screens.
Minor formatting adjustments.
Data Version Description of Changes

160
10/2025 7.2 • Chapter 03:

Page 13 – Item 06 (new): inclusion of the obligation to send an error message in cases where the return of the key submission to the DICT is of an account or user with a restriction for receiving Pix transactions due to involvement in fraud.
Adjustments to item numbering due to the inclusion of a new item in the chapter.
Chapter 06:
Page 29 – Item 08 (new): inclusion of the obligation to inform the user about an error resulting from reading a QR Code with a key linked to an account or user with a restriction for receiving Pix transactions due to involvement in fraud.
Adjustments to item numbering due to the inclusion of a new item in the chapter.
Chapter 07:
Page 36 – Item 10 (new): inclusion of the obligation to inform the user about an error resulting from reading a QR Code with a key linked to an account or user with a restriction for receiving Pix transactions due to involvement in fraud.
Page 38 – Item 16 (new): inclusion of recommendation to display the debtor's data on the payment receipt for payer and recipient users, if provided.
Adjustments to item numbering due to the inclusion of new items in the chapter.
Chapter 08:
Page 40 – Item 03: exclusion of permission to supplement the Scheduled Pix name to inform the user that it is a recurring schedule;
Page 40 – Item 04: inclusion of the phrase “the immediate payment of authorization journeys 3 and 4 constitutes an exception to this rule, and should not be identified with the nomenclature Automatic Pix in the account statement or Pix statement, but rather as a Pix transaction”;
Page 40 – Item 05 (new): inclusion of the obligation to identify the return of Pix transactions disputed within the scope of MED in the account statement and, if available, in the Pix statement. Inclusion of prohibition of displaying the sender's name if the returned resources come from an account different from the recipient account of the root transaction.
Adjustments to item numbering due to the inclusion of a new item in the chapter.
Chapter 10:
Page 48 – Item 07: replacement of “must” with “may”.
Chapter 12:
Pages 66 and 68 – Items 13 and 18: replacement of “recurring Scheduled Pix” with “Scheduled Pix” on the illustrative screens.
Chapter 15:
Page 85 – Item 05: inclusion of the authorization journey number to which the item applies and explanatory text about the “payment object” field;
Page 85 – Item 06: inclusion of the authorization journey number to which the item applies;
Page 85 – Item 07: inclusion of the authorization journey number to which the item applies;
Page 85 – Item 08: inclusion of reference to the “Pending Authorizations” menu and the authorization journey number to which the item applies. Replacement of “from this journey” with “of the journey”;
Page 86 – Item 09: inclusion of the authorization journey number to which the item applies, the phrase “of confirmation” and wording adjustments;
Page 87 – Item 11: inclusion of the authorization journey number to which the item applies;
Page 87 – Item 12: inclusion of the authorization journey number to which the item applies. Replacement of “from this journey” with “of the journey”;
Page 87 – Item 13: inclusion of the authorization journey number to which the item applies;
Page 88 – Item 14: inclusion of the authorization journey number to which the item applies;
Page 88 – Item 15: inclusion of the authorization journey number to which the item applies. Replacement of “from this journey” with “of the journey”;
Page 89 – Item 16: inclusion of the authorization journey numbers to which the item applies. Inclusion of “(if provided)” after “payment object” and replacement of “charge identifier” with “identifier of the payment object”. Inclusion of explanatory text about the fields “payment object” and “identifier of the payment object”;
Page 89 – Item 17: inclusion of the authorization journey numbers to which the item applies;
Data Version Description of Changes

161
10/2025 7.2 • Chapter 15:

Page 90 – Item 18: exclusion of “first” before “immediate payment”. Inclusion of the authorization journey number to which the item applies;
Page 91 – Item 19: exclusion of “first” before “immediate payment”. Inclusion of the authorization journey number to which the item applies. Inclusion of “(if provided)” after “payment object” and replacement of “charge identifier” with “identifier of the payment object”;
Page 92 – Item 20: inclusion of the authorization journey number to which the item applies. Replacement of “highlight that the first payment is immediate” with “highlight that there will be an immediate payment”;
Page 92 – Item 21: exclusion of “first” before “immediate payment”. Inclusion of the authorization journey number to which the item applies;
Page 92 – Item 22: inclusion of the authorization journey number to which the item applies;
Page 92 – Item 23: replacement of “first payment” with “immediate payment related to journey 3”;
Page 92 – Item 24: inclusion of the authorization journey numbers to which the item applies. Replacement of “time required by regulation to allow the completion of the process” with “time established for the payer user experience in granting the Automatic Pix authorization”. Inclusion of “payer” after “message to the user”;
Page 93 – Item 26: inclusion of “(if provided)” after “payment object” and replacement of “charge identifier” with “identifier of the payment object”;
Page 95 – Item 28: inclusion of “(if offered by the PSP)” after “use of credit line”. Inclusion of button for option to receive schedule notifications on the top right corner of the screen;
Page 95 – Item 29: inclusion of “(if offered by the PSP)” after “use of credit line”;
Page 96 – Item 33: inclusion of “(if provided)” after “payment object” and replacement of “charge identifier” with “identifier of the payment object”;
Page 97 – Item 35: inclusion of the obligation to include in the history query both authorizations granted directly to the PSP and consents effected through a PSI, with standardization of the nomenclature used to indicate the status of the authorizations;
Page 99 – Item 40: Inclusion of “recurring” after “payment receipt” and “(if provided)” after “payment object”. Inclusion of payer information on the first illustrative screen;
Page 99 – Item 41 (new): Inclusion of prohibition of identifying the immediate payment receipt of journeys 3 and 4 or the charge with maturity of journey 4 as Automatic Pix and inclusion of the obligation to follow the requirements set forth in the chapters “Payment through Static QR Code” and “Immediate Payment or with Maturity through Dynamic QR Code”;
Page 99 – Item 42 (new): Inclusion of recommendation to include the debtor's data on the recurring payment receipt.
Page 101 – Item 44: replacement of “scheduled payment notifications” with “schedule notifications”;
Page 102 – Item 52 (new numbering): Inclusion of “(if provided)” after “payment object”;
Page 102 – Item 52: excluded, due to revocation by Instruction Normative BCB No. 625, of 05/29/2025;
Page 103 – Item 55: inclusion of the authorization journey number to which the item applies. Replacement of “suspension” with “exclusion”;
Page 103 – Item 58: exclusion of “up to two days before the expected settlement date” and inclusion of “try” before “enable payment in the same cycle”;
Page 103 – exclusion of the reference to the deadline for changing the maximum value on the illustrative screen regarding Items 53 and 58;
Adjustments to item numbering due to the inclusion of new items in the chapter.
Chapter 16:
Page 106 – Item 03: replacement of “must be provided” with “must be provided” and “deadline for resolution of transaction disputes” with “maximum time limit for the PSP to complete the analysis of the transaction dispute”;
Page 106 – Item 04: adjustment resulting from MED 2.0 – text completion to inform that the return may occur from accounts different from the recipient account of the root (original) transaction that are involved in the fraud. Exclusion of phrase mentioning the 90-day monitoring period for complementary returns;
Page 107 – Item 07: adjustment resulting from MED 2.0 – replacement of the term “infraction notification” with “value recovery”;
Page 107 – Item 08: adjustments resulting from MED 2.0 – replacement of the term “infraction notification” with “value recovery” and text completion to inform about the need for sufficient balance in the recipient account of the root transaction or in other accounts involved in the suspicion of fraud to enable partial or total return;
Data Version Description of Changes

162
10/2025 7.2 • Chapter 16:

Page 108 – item 09: adjustments resulting from MED 2.0 – substitution of the term “infraction notification” with “value recovery” and completion of text to inform about the necessity of having a balance in the receiver account of the root transaction or in other accounts involved in the suspicion of fraud to enable partial or total refund;
Page 108 – item 10: adjustment resulting from MED 2.0 – substitution of the term “infraction notification” with “value recovery”. Inclusion of information to establish that “the request for the fraud report should preferably occur before the completion of the self-service journey, immediately after the recording of the value recovery, in order to guarantee the timeliness of information collection”;
Page 108 – item 11: adjustment resulting from MED 2.0 – substitution of the term “infraction notification” with “value recovery”;
Page 110 – item 14: adjustment resulting from MED 2.0 – substitution of the term “infraction notification” with “value recovery”;
Page 111 – item 17: adjustments resulting from MED 2.0 – substitution of the term “infraction notification” with “value recovery” and completion of text to inform about the necessity of having a balance in the receiver account of the root transaction or in other accounts involved in the suspicion of fraud to enable partial or total refund;
Page 112 – item 23: adjustment resulting from MED 2.0 – substitution of “receiver name” with “name of the receiver of the root transaction”. Inclusion of the effectively refunded amount in the set of minimum information to be presented for approved disputes. Substitution of “amount” with “contested amount” in the exemplified screens and inclusion of “refunded amount” in the example of an approved dispute;
Page 112 – item 24: substitution of “receiver name” with “name of the receiver of the contested transaction”. Substitution of “amount effectively refunded regarding approved disputes” with “amount effectively refunded, in the case of an approved dispute”. Adjustment resulting from MED 2.0 – rewriting of the sentence dealing with the 90-day deadline for carrying out refunds, with inclusion of mention of other accounts involved in the fraud beyond the receiver account of the root transaction;
Page 113 – item 26: adjustments resulting from MED 2.0 – substitution of the term “original transaction” with “root transaction”, inclusion of mention of other receivers involved in the suspicion of fraud and substitution of “infraction notification associated with a refund request” with “value recovery”;
Page 113 – item 27: adjustments resulting from MED 2.0 – substitution of the term “original transaction” with “root transaction” and inclusion of mention of other receivers involved in the suspicion of fraud;
Page 113 – item 28: adjustments resulting from MED 2.0 – substitution of the term “original transaction” with “root transaction” and inclusion of mention of other receivers involved in the suspicion of fraud.
Page 113 – exclusion of the term “PSP of the paying user” from the footer recipient.
Page 114 – item 29: adjustments resulting from MED 2.0 – inclusion of minimum information of the credit notification originating from the account of the receiver of the root transaction and of the notification in the case of credit to an account different from that which received the root transaction. Prohibition of displaying the sender's name when it concerns an account different from that which received the root transaction;
Page 114 – Inclusion of second exemplified screen for item 29 and exclusion of the term “PSP of the receiving user” from the footer recipient.
Chapter 21 (Annex I):
Adjustments of page and item numbers cited.

Data Version Description of Changes

163
12/2025 7.3 • Chapter 16:

Page 113 – item 26: adjustments to the text to make clear that, in the context of MED 2.0, the message sent to the involved receiving user regarding the suspicion of fraud communicating the blocking of resources in their account must mention the information of the transaction linked to the infraction notification received, which may be the root transaction or a transaction from the second layer. In the corresponding exemplified screen, inclusion of the value of the transaction linked to the infraction notification, different from the blocked value, and alteration of the notification receipt time to align with the information about the blocking time shown in the screen example of item 27.
Page 113 – item 27: adjustments to the text to make clear that, in the context of MED 2.0, the message sent to the involved receiving user regarding the suspicion of fraud communicating the release of blocked resources in their account must mention the information of the transaction linked to the infraction notification received, which may be the root transaction or a transaction from the second layer. Completion of text to inform about the necessity of sending the message even in cases where a partial refund of the previously blocked amount has occurred. In the corresponding exemplified screen, substitution of “blocked” with “associated with the blocking performed” and of “regarding the Pix transaction” with “linked to the Pix transaction”.
Page 113 – item 28: completion of text to clarify that the refund is destined for the paying user of the root transaction. Adjustments to the text to make clear that, in the context of MED 2.0, the message sent to the involved receiving user regarding the suspicion of fraud communicating the refund of resources blocked in their account must mention the information of the transaction linked to the infraction notification received, which may be the root transaction or a transaction from the second layer. Exclusion of the “Date/time/minute/second (Brasília time) of the blocking” from the list of mandatory minimum information in the message. Prohibition of displaying the name of the refund recipient when it concerns a refund originating from an account different from that which received the root transaction. In the corresponding exemplified screen, exclusion of the name of the refund recipient and the date/time/minute/second of the blocking, and inclusion of “via MED”.
Page 114 – item 29: substitution of the term “original transaction” with “root transaction”. Substitution of “should not be displayed in the notification” with “should not be displayed to the paying user”.
Page 114 – item 30 (new): inclusion of the obligation to apply the provisions of items 26 to 29 of Chapter 16 to disputes within the scope of MED opened through any service channel.
Page 114 – item 31: adjustment of item numbering.

Data Version Description of Changes

for the user experience version 7.3
MINIMUM REQUIREMENTS
Access version 7.4 here, effective from 01/03/2027.

Instruction Normative BCB No. 689 — Publishes Version 7.3 of the "Minimum Requirements for User Experience" Document, which Comprises the Pix Regulation

Version 7.3 Pix with Pix Key

Version 7.3 Pix with Pix Key

Version 7.3 Pix with Pix Key

Version 7.3 Pix with manual insertion of transaction account data

Version 7.3 Pix with manual insertion of transaction account data

Version 7.3 Pix with manual insertion of transaction account data

Version 7.3 Generation of static QR Code

Version 7.3 Generation of static QR Code

Version 7.3 Generation of static QR Code

Version 7.3 Payment through static QR Code

Version 7.3 Payment through static QR Code

Lineage: Superseded

Timeline