1 • Pix Time Manual – Version 7.0

Pix Time Manual

Version 7.0

2 • Pix Time Manual – Version 7.0

MAXIMUM TIME FOR PAYMENT TRANSACTIONS WITHIN THE SCOPE OF PIX ...................................... 3
1.1. PAYMENT ORDERS SENT TO THE PRIMARY MESSAGE TRANSMISSION CHANNEL OF THE SPI ..................... 3
1.2. PAYMENT ORDERS SENT TO THE SECONDARY MESSAGE TRANSMISSION CHANNEL OF THE SPI ................. 3
1.3. PAYMENT ORDERS SETTLED OUTSIDE THE SPI .......................................................................................... 4
1.4. SUBMISSION OF TRANSACTIONS SETTLED OUTSIDE THE SPI TO THE BC.................................................................................. 4
MAXIMUM TIME FOR AUTHORIZATION OF TRANSACTION INITIATION BY THE PARTICIPANT PROVIDING PAYMENT SERVICES TO THE PAYER USER..................................................................................... 5
MAXIMUM TIMES FOR PIX AUTOMATIC........................................................................................ 5
3.1. CONFIRMATION OF RECEIPT OF THE PERMISSION REQUEST BY THE PAYER'S PSP....................................... 5
3.2. CONFIRMATION OF AUTHORIZATION BY THE RECIPIENT'S PSP ............................................................................... 6
3.3. CONFIRMATION OF RECEIPT OF THE CANCELLATION INFORMATION OF THE AUTHORIZATION ....................................... 6
3.4. CONFIRMATION OF RECEIPT OF THE CANCELLATION INFORMATION OF THE SCHEDULED DEBIT OR A CHARGE. 7
INDICATORS FOR CALCULATING SERVICE LEVEL AGREEMENTS (SLAs) OF PARTICIPANTS............ 7
4.1. SLA OF THE SETTLEMENT CYCLE OF A PIX....................................................................................................... 7
4.1.1. Indicators calculated by the SPI .................................................................................................. 10
4.1.2. Indicators reported by Pix participants .................................................................... 11
4.2. SLA OF THE DICT ......................................................................................................................................... 12
4.2.1. Indicators calculated by the DICT................................................................................................ 12
4.2.2. Indicators reported by Pix participants .................................................................... 15
4.3. PARTICIPANTS' AVAILABILITY INDEX ............................................................................................. 18
4.4. SLA OF THE AUTHORIZATION GRANTING CYCLE OF PIX AUTOMATIC BY THE PAYER USER............................. 20
4.4.1. Indicators calculated by the SPI .................................................................................................. 22
4.4.2. Indicators reported by Pix participants .................................................................... 23
4.5. SLA OF THE SUBMISSION OF INFORMATION TO THE CENTRAL BANK.................................................................................... 23
4.5.1. Submission of Pix transactions settled at the participant to the CB ........................................................ 23
OBSERVANCE OF SERVICE LEVEL AGREEMENTS (SLAs) OF PARTICIPANTS.................................. 24
5.1. LEVEL 1 INDICATORS............................................................................................................................ 25
5.2. LEVEL 2 INDICATORS............................................................................................................................ 25
5.3. CATEGORIES, TARGETS, AND REFERENCES............................................................................................................ 26
SLA OF THE CENTRAL BANK OF BRAZIL ..................................................................................................... 26
6.1. SLA OF THE SPI............................................................................................................................................ 26
6.1.1. Time spent in the SPI ............................................................................................................ 26
6.1.2. SPI availability index.......................................................................................................... 27
6.2. SLA OF THE DICT ......................................................................................................................................... 27
6.2.1. Time spent in the DICT (query)......................................................................................... 27
6.2.2. Time spent in the DICT (update).................................................................................... 27
6.2.3. DICT availability index ............................................................................................... 28
REVISION HISTORY ......................................................................................................................... 29

3 • Pix Time Manual – Version 7.0

1. Maximum Time for Payment Transactions Within the Scope of Pix

1.1. Payment Orders Sent to the Primary Message Transmission Channel of the SPI

Rule:
The maximum time limit for a Pix sent to the primary message transmission channel of the Instant Payment System (SPI) is 40 seconds.

Transactions that are not settled within this time limit will be rejected. The rejection of Pix, after receipt of the order by the SPI (t1’), is always carried out by the SPI and communicated to participants, in accordance with the Regulation attached to BCB Resolution No. 195, of March 3, 2022.

Explanatory Note:
The counting of the maximum time limit begins when the Pix participant receives the payment order from the payer user and ends when the Pix settlement is effected. As per the figure illustrating the settlement cycle between two direct participants of the SPI, presented in section 4.1 of this Manual, the counting of the maximum time limit begins at t0’ and ends at t4.

In the case of transactions with suspected fraud, the counting of time begins when the SPI receives the payment order from the Pix participant (t1’) and ends when the Pix settlement is effected (t4).

In the case of a Pix initiated through a payment transaction initiation service, the counting of time begins when the transactional account provider receives the confirmation of sharing from the payment transaction initiation service provider of the payer user (t0’) and ends when the Pix settlement is effected (t4).

1.2. Payment Orders Sent to the Secondary Message Transmission Channel of the SPI

Rule:
The maximum time limit for a Pix sent to the secondary message transmission channel of the SPI is 45 minutes.

Explanatory Note:

4 • Pix Time Manual – Version 7.0

Only payment orders referring to Scheduled Pix or Pix Charge for payment with maturity that are scheduled must be sent to the secondary message transmission channel 1.

In these cases, the counting of time begins when the SPI receives the payment order from the Pix participant (t1’) and ends when the Pix settlement is effected (t4).

These rules are valid both for a Pix initiated by a transactional account provider and for a Pix initiated through a payment transaction initiation service.

1.3. Payment Orders Settled Outside the SPI

Rule:
The maximum time limit for payment orders in transactions that are not sent for settlement in the SPI, referring to Scheduled Pix or Pix Charge for payment with maturity that are scheduled, is 45 minutes.

The maximum time limit for all other payment orders, in transactions that are not sent for settlement in the SPI, is 40 seconds.

Transactions that are not settled within these time limits must be rejected. The participant responsible for settling the transaction must effect the rejection.

Explanatory Note:
In the case of Scheduled Pix and the scheduling of Pix Charge for payment with maturity, the counting of time begins when the participant responsible for settlement receives the payment order and ends when the Pix settlement is effected.

For other cases, the counting of time begins when the payer's PSP receives the order from the payer user (t0’) and ends when the Pix settlement is finalized (t4).

In the case of transactions with suspected fraud, the counting of time begins when the participant responsible for settlement authorizes the payment order and ends when the Pix settlement is effected.

1.4. Submission of Transactions Settled Outside the SPI to the BC

The maximum deadline for the submission of a transaction settled outside the SPI, in accordance with the terms of art. 2-A of BCB Instruction No. 32, of October 26, 2020, is 30 days after its settlement.

1 Correspond to pacs.008 messages filled with “NORM” in the “prioridadePagamento” field and with “PAGAGD” in the “tipoPrioridadePagamento” field.

5 • Pix Time Manual – Version 7.0

2. Maximum Time for Authorization of Transaction Initiation by the Participant Providing Payment Services to the Payer User

Rule:
The maximum time limit for authorization of transaction initiation by the participant providing payment services to the payer user is equivalent to the maximum time limit for validation, in accordance with the Regulation attached to BCB Resolution No. 195, of March 3, 2022. This maximum time limit is defined in art. 18 of BCB Instruction No. 243, of March 16, 2022.

Transactions with suspected fraud, with the exception of transactions for the purpose of withdrawal or change and Smart Transfers 2, are subject to a maximum time of 30 minutes for authorization of payment orders sent by the payer user from 8:00 a.m. to 8:00 p.m., Brasília time, on business days, and a maximum time of 60 minutes for other hours and days.

Explanatory Note:
The counting of the maximum time limit begins when the participant providing payment services to the payer user receives the payment order (t0’). In the case of a Pix initiated through a payment transaction initiation service, the counting of time begins when the transactional account provider receives the confirmation of sharing from the payment transaction initiation service provider of the payer user (also equivalent to t0’).

The payer user must be notified by their payment service provider if the transaction is suspected of fraud. 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.

3. Maximum Times for Pix Automatic

3.1. Confirmation of Receipt of the Permission Request by the Payer's PSP

Context:
In Journey 1 of Pix Automatic, the payer user informs the recipient user of the desire to use Pix Automatic as a form of payment. The recipient's PSP, after receiving information from its user for the creation of the recurrence, sends a pain.009 message requesting confirmation of the recurrence to the payer's PSP, which must confirm receipt through a pain.012 message.

Rule:

6 • Pix Time Manual – Version 7.0

The maximum time limit that the recipient's PSP must wait for the receipt of the pain.012 message confirming the receipt of the permission request by the payer's PSP is 1 minute.

If it does not receive a response from the payer's PSP within the stipulated time, the recipient's PSP must change the status of the recurrence to cancelled 3.

It is recommended that the recipient's PSP retry sending the pain.009 within the maximum stipulated time.

3.2. Confirmation of Authorization by the Recipient's PSP

Context:
In any authorization journey of Pix Automatic, the recipient's PSP, after receiving a pain.012 message from the payer's PSP confirming the granting of authorization by the payer user, must conclude the process by sending a new pain.012 message to the payer's PSP.

Rule:
The maximum time limit that the payer's PSP must wait for the receipt of the pain.012 message confirming the conclusion of the authorization process by the recipient's PSP is 1 hour.

If the recipient's PSP does not respond within the stipulated time, the payer's PSP must notify the payer user about the failure of the flow 4.

It is recommended that the payer's PSP retry sending the pain.012 within the maximum stipulated time.

3.3. Confirmation of Receipt of the Cancellation Information of the Authorization

Context:
The payer user may request the cancellation of the authorization to the payer's PSP or directly to the recipient user. In the first situation, the payer's PSP cancels the authorization and communicates the cancellation to the recipient's PSP through a pain.011 message. In the second situation, the recipient's PSP, after receiving the request from its user, cancels the recurrence of the charges and communicates the payer's PSP through a pain.011 message. In any of the situations, the PSP that receives the cancellation message must confirm receipt by sending a pain.012 message to the other PSP.

Rule:

7 • Pix Time Manual – Version 7.0

The maximum time limit that the PSP must wait for the receipt of the pain.012 message, after having sent the pain.011 informing about the cancellation of the authorization or recurrence, is 12 hours.

If the PSP issuing the message does not receive a response within the stipulated time, it must consider the flow as effected.

It is recommended that new attempts to send the pain.011 be made within the maximum stipulated time.

3.4. Confirmation of Receipt of the Cancellation Information of the Scheduled Debit or a Charge

Context:
After cancelling the scheduled payment at the request of the payer user, the payer's PSP sends the cancellation information to the recipient's PSP through a camt.055 message. Analogously, after cancelling a charge at the request of the recipient user, the recipient's PSP sends the cancellation information of the charge to the payer's PSP through a camt.055 message. The PSP that receives the cancellation message must confirm receipt by sending a camt.029 message to the other PSP.

Rule:
The maximum time limit that the PSP must wait for the receipt of the camt.029 message, after having sent the camt.055 informing about the cancellation of the scheduled debit or charge, is 12 hours.

If the PSP issuing the message does not receive a response within the stipulated time, it must consider it as an effected flow.

It is recommended that new attempts to send the camt.055 be made within the maximum stipulated time.

4. Indicators for Calculating Service Level Agreements (SLAs) of Participants

All SLA indicators must be calculated on a monthly basis. For the purposes of SLA accounting, all messages must be considered, including error messages and those referring to Pix initiated through a payment transaction initiation service.

4.1. SLA of the Settlement Cycle of a Pix

The SLAs of the settlement cycle of a Pix will be monitored through indicators calculated by the SPI and through indicators reported by Pix participants. The indicators calculated by the SPI will consider in their calculation operations involving transactions initiated by indirect participants of the SPI to whom the direct participant provides settlement services. The indicators reported by Pix participants must consider only transactions initiated by end users of the participant itself.

For the purposes of calculating the indicators, the following premises must be followed:
a. the clocks of servers of different institutions cannot be used in operations for calculating indicators, since the existence of small differences could distort, significantly, the indicators; and b. the clocks of servers within the same institution must be maintained at a level of synchronization that ensures there will be no distortion.

Each of the institutions participating in Pix is responsible for keeping the clocks of the servers involved in the process synchronized.

For the purposes of understanding the indicators, the settlement cycle can be illustrated by means of the figure below.

For the measurement of times, it is assumed that events can be measured on both sides of an interaction between two agents. Thus, given any event, for example, the sending of the pacs.008 message from the SPI to the payment service provider (PSP) of the recipient, there is a designation for the time measured from the SPI's perspective (t2) and another designation for the time measured from the recipient's PSP's perspective (t2’). In this way, the difference between any time (tx) and its mirror in the other actor (tx’) will result from the difference in the clocks of the two agents themselves, as well as from the technological solution adopted in communication, which determines points of measurement where measurement is possible.

The timeline indicated in the figure represents the times used in the calculation of SLAs, which are detailed below:
a. t0’ – PSP of the payer receives request: the moment at which the PSP of the payer receives the confirmation from the payer user to send the payment order. Equivalent to the value of the AcceptanceDateTime field of the pacs.008 message that will be sent to the SPI. For transactions in which the payer user is a legal entity, the moment at which the PSP of the payer accepts the request to send the payment order, after concluding the necessary security checks and blocking the value corresponding to the transaction, is considered. For transactions initiated by natural persons, the moment at which the PSP of the payer receives the confirmation from the payer user to send the payment order, before any security check and value blocking, is considered; b. t1 – PSP of the payer creates pacs.008: the moment at which the PSP of the payer creates the pacs.008 message, equivalent to the CreationDateTime field of the said message. This time must be measured before the signature of the message;
c. t1’ – SPI receives pacs.008: the moment at which the SPI receives the HTTP request with the pacs.008 message from the PSP of the payer;
d. t2 – SPI makes pacs.008 available: the moment at which the pacs.008 message is made available for consumption by the PSP of the recipient; e. t3’ – SPI receives pacs.002: the moment at which the SPI receives the HTTP request with the pacs.002 message from the PSP of the recipient; f. t4 – finality: the moment at which the SPI performs the balance exchange in the Instant Payment Account of the PSP of the payer and the PSP of the recipient 5; g. t5a – SPI makes pacs.002 available: the moment at which the pacs.002 message is made available for consumption by the PSP of the payer; and h. t6a – PSP of the payer informs payment: the moment at which the PSP of the payer sends the notification of the transaction result to the payer user.

The figure below facilitates understanding for cases involving transactions between indirect participants of the SPI:

The figure below facilitates understanding for cases involving transactions settled within the same institution:

5 There is no SLA for this time. Included in the timeline only for illustrative purposes.

10 • Pix Time Manual – Version 7.0

4.1.1. Indicators Calculated by the SPI

4.1.1.1. Time spent by the PSP of the payer and by the liquidator of the PSP of the payer in the initiation of Pix

Indicator of the direct participant of the SPI, considering percentiles, as per the table below:

Indicator	Percentile	Time
Time spent by the PSP of the payer and by the liquidator of the PSP of the payer in the initiation of Pix (t1 – t0’)	50%	0.9 second
	95%	1.5 second

In the calculation, operations in which the direct participant of the SPI acts as liquidator of an indirect participant of the SPI will also be accounted for.

The indicator will not account for Scheduled Pix transactions, transactions referring to the scheduling of Pix Charge for payment with maturity, transactions in which the maximum time for authorization of transaction initiation by the participant of the payer user is extended, in cases of transactions with suspected fraud, and return transactions. That is, the indicator accounts only for transactions whose payment orders have the pacs.008 field prioridadePagamento filled with HIGH.

4.1.1.2. Time spent by the PSP of the recipient or by the liquidator of the PSP of the recipient in the authorization of Pix

Indicator of the direct participant of the SPI, considering percentiles, as per the table below:

Indicator	Percentile	Time
Time spent by the PSP of the recipient or by the liquidator of the PSP of the recipient in the authorization of Pix (t3’ – t2)	50%	1.4 second
	95%	2.3 seconds

2 As defined in the Open Finance Data and Services Scope Manual, attached to BCB Instruction No. 587, of January 31, 2025.

3 As described in the Pix Initiation Standards Manual, available at https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf

4 As described in the Minimum Requirements for User Experience, available at https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/IV_RequisitosMinimosparaExperienciadoUsuario.pdf

11 • Pix Times Manual – Version 7.0

In the calculation, operations in which the direct participant of the SPI acts as a clearing agent for an indirect participant of the SPI will also be accounted for.
The indicator will not account for operations whose settlement is interrupted due to a timeout in the SPI.
The indicator will not account for Scheduled Pix transactions and transactions related to the scheduling of Pix Collection for payment with maturity. That is, the indicator does not account for transactions whose payment orders are sent to the secondary message transmission channel of the SPI.

4.1.2. Indicators reported by Pix participants

4.1.2.1. Payer user experience
The calculation must be performed by the payer's PSP, considering percentiles, according to the table below:

Indicator	Percentile	Time
Payer user experience (t6a – t0’)	50%	6.0 seconds
	99%	10.0 seconds

The calculation of this indicator must be performed by all Pix participants, both direct participants of the SPI and indirect participants. Transactions settled outside the SPI must not be included. The indicator must not account for Scheduled Pix transactions, transactions related to the scheduling of Pix Collection for payment with maturity, transactions in which the maximum time for authorization of transaction initiation by the payer's user participant is extended, in cases of transactions suspected of fraud, and return transactions. That is, the indicator must only account for transactions whose payment orders have the prioridadePagamento field of the pacs.008 message filled with HIGH. The indicator must also not account for operations whose settlement is interrupted due to a timeout of the receiver's PSP in the SPI. The indicator must account for Pix transactions initiated through a payment transaction initiation service. In these cases, to measure the times t6a and t0’, the figure of the payer's user payment initiation service provider must be considered equivalent to the payer user.

4.1.2.2. Payer user experience in transactions settled outside the SPI
The calculation must be performed by the payer's PSP, considering percentiles, according to the table below:

Indicator	Percentile	Time
Payer user experience in transactions settled outside the SPI (t6a – t0’)	50%	6.0 seconds
	99%	10.0 seconds

The calculation of this indicator must be performed by all Pix participants, both direct participants of the SPI and indirect participants. Only transactions settled outside the SPI must be included, understood within this concept as: (i) situations where the debited and credited transactional accounts are in the same PSP; (ii) situations where the transactional accounts are in two indirect PSPs that use a clearing service of the same direct PSP; or (iii) situations where one of the accounts (credited or debited) is in an indirect PSP and the transaction is settled in the same PSP that holds the other account. The indicator must not account for Scheduled Pix transactions and transactions related to the scheduling of Pix Collection for payment with maturity. The indicator must not account for transactions subject to the maximum time limits for authorization of transaction initiation with suspected fraud, as set forth in section 2 of this Manual. The indicator must not account for return transactions. The indicator must account for Pix transactions initiated through a payment transaction initiation service. In these cases, to measure the times t6a and t0’, the figure of the payer's user payment initiation service provider must be considered equivalent to the payer user.

4.2. ANS of DICT
The ANS of DICT will be monitored through indicators calculated by the DICT itself and through indicators reported by Pix participants. The indicators calculated by the DICT will consider in their calculation operations involving keys registered by participants with indirect access to the DICT to which the participant with direct access provides service. The indicators reported by Pix participants must consider only operations involving keys registered in the participant itself. In the tables with the indicators reported by Pix participants, the columns for flow and flow steps refer to the flows detailed in the DICT Operational Manual.

4.2.1. Indicators calculated by the DICT

4.2.1.1. Receive new portability, claim of possession, or notification of infraction
Indicator of the donor PSP (receiver's PSP, in the case of notification of infraction), with direct access to the DICT, considering percentiles, according to the table below:

Indicator	Percentile	Time
Time elapsed between the creation of a portability or claim of possession or notification of infraction and its receipt (acknowledge) by the donor (receiver's PSP, in the case of notification of infraction)	95%	180 seconds

4.2.1.2. Complete portability
Indicator of the claiming PSP, with direct access to the DICT, considering percentiles, according to the table below:

Indicator	Percentile	Time
Time elapsed between the status changes of a portability process, from “Confirmed”, by the donor PSP, to “Completed”, by the claiming PSP	95%	180 seconds

4.2.1.3. Cancel portability due to lapse of time
Indicator of the donor PSP, with direct access to the DICT, in the portability process, considering percentiles, according to the table below:

Indicator	Percentile	Time
Cancellation of portability due to lapse of time	95%	60 minutes after the deadline established for the end of the resolution period of a portability (seven days)

4.2.1.4. Confirm claim of possession due to lapse of time
Indicator of the donor PSP, with direct access to the DICT, in the claim of possession process, considering percentiles, according to the table below:

Indicator	Percentile	Time
Confirmation of claim of possession due to lapse of time	95%	60 minutes after the deadline established for the end of the resolution period of a claim of possession (seven days)

4.2.1.5. Cancel claim of possession due to lapse of time

14 • Pix Times Manual – Version 7.0

Indicator of the claiming PSP, with direct access to the DICT, in the claim of possession process, considering percentiles, according to the table below:

Indicator	Percentile	Time
Cancellation of claim of possession due to lack of active validation of the key by the user	95%	60 minutes after the deadline established for the end of the period for cancellation of a claim of possession (thirty days)

4.2.1.6. Send result of the analysis of a notification of infraction
Indicator of the PSP that receives the notification of infraction, with direct access to the DICT, in the notification of infraction process, considering percentiles, according to the table below:

Indicator	Percentile	Time
Sending of the result of the analysis in a notification of infraction process	95%	7 days after the notification is made available with status “Open” in the DICT

4.2.1.7. Perform synchronization verification
Indicator of the PSP with direct access to the DICT, according to the table below:

Indicator	Percentile	Time
Time elapsed since the last successful synchronization verification for each type of key	95%	36 hours

4.2.1.8. Conclude request for return due to well-founded suspicion of fraud
Indicator of the receiver's PSP, with direct access to the DICT, in the request for return process (includes the reasons fraud and refund_cancelled), considering percentiles, according to the table below:

15 • Pix Times Manual – Version 7.0

Indicator	Percentile	Time
Time elapsed between the opening of a request for return in the DICT due to well-founded suspicion of fraud and its respective conclusion	99%	6 hours

4.2.1.9. Conclude request for return due to operational failure of the payer's PSP
Indicator of the receiver's PSP, with direct access to the DICT, in the request for return process (includes the reasons operational_flaw and pix_automatico), considering percentiles, according to the table below:

Indicator	Percentile	Time
Time elapsed between the opening of a request for return in the DICT due to operational failure and its respective conclusion	95%	48 hours

4.2.2. Indicators reported by Pix participants
The flows referenced in the tables are detailed in the DICT Operational Manual.

4.2.2.1. Payer user experience in the consultation to the DICT
The calculation must be performed by the payer's PSP, considering percentiles, according to the table below. The indicator must not account for transactions initiated through a payment transaction initiation service.

Indicator	Percentile	Time	Flow Steps	Flow
Payer user experience in the consultation to the DICT	99%	2 seconds	4 to 15	PSP with direct access
			4 to 19	PSP with indirect access

4.2.2.2. Sending of the code to the user's email or cell phone number
The indicator must consider only experiences that occurred during the hours in which the registration and portability functionalities are available to end users. The calculation must be performed by the donor PSP, in the case of portability, considering percentiles, according to the table below:

Indicator	Percentile	Time	Flow Steps	Flow
Time to send the code to email or cell phone number in key registration (or in portability, if it is initiated directly by the end user, from a specific functionality offered by their PSP)	95%	30 seconds	4 to 5	6 PSP with direct access and with indirect access

4.2.2.3. User experience in key registration
The indicator refers to the case in which the operation is initiated by request of the end user. In addition, the indicator must consider only experiences that occurred during the hours in which the registration functionality is available to end users. The calculation must be performed by the PSP, considering percentiles, according to the table below:

Indicator	Percentile	Time	Flow Steps	Flow
User experience in key registration (after completion of the active validation process 7)	95%	20 seconds	6 to 15	PSP with direct access
			6 to 19	PSP with indirect access

4.2.2.4. User experience in key deletion
The indicator refers to the case in which the operation is initiated by request of the end user. In addition, the indicator must consider only experiences that occurred during the hours in which the deletion functionality is available to end users. The calculation must be performed by the PSP, considering percentiles, according to the table below:

6 In the case of registration.
7 Valid also for CPF, CNPJ and EVP registrations, which do not require active validation.

17 • Pix Times Manual – Version 7.0

Indicator	Percentile	Time	Flow Steps	Flow
User experience in key deletion	95%	20 seconds	4 to 13	PSP with direct access
			4 to 17	PSP with indirect access

4.2.2.5. Notification of portability or claim of possession to the donor user in an authenticated channel
The indicator must consider only experiences that occurred during the hours in which the portability and claim of possession functionalities are available to end users. The calculation must be performed by the donor PSP, considering percentiles, according to the table below:

Indicator	Percentile	Time	Flow Steps	Flow
Time elapsed between the receipt (acknowledge) in the DICT and the notification to the donor user in a logged-in environment (portability process or claim of possession process)	95%	600 seconds	1 to 2	Donor PSP with direct access
			1 to 6	Donor PSP with indirect access

4.2.2.6. Cancel or confirm portability or claim of possession at the user's request
The indicator must consider only experiences that occurred during the hours in which the portability and claim of possession functionalities are available to end users. The calculation must be performed by the donor PSP, considering percentiles, according to the table below:

Indicator	Percentile	Time	Flow Steps	Flow
Time elapsed between the user's action (confirmation or cancellation) and the sending of the information to the DICT (portability process or claim of possession process)	95%	60 seconds	8 to 12 (portability) and 8 to 19 (claim)	Donor PSP with direct access
			10 to 14 (portability) and 10 to 25 (claim)	Donor PSP with indirect access

4.2.2.7. Opening of the MED after the registration of the user's demand

18 • Pix Times Manual – Version 7.0

The calculation must be performed by the payer's user's PSP (with direct or indirect access), considering percentiles, according to the table below:

Indicator	Percentile	Time	Flow Steps	Flow
Time elapsed between the user's complaint in a customer service channel made available by the participant and the opening of the notification of infraction or the recovery of values	95%	1,800 seconds	2 to 8 (notification of infraction)	PSP with direct access and with indirect access
			1 to 9 (recovery of values)	Institution and request for blocking in the interactive process and in the automated process

4.3. Index of availability of participants
The availability index is defined as the index that expresses, in percentage terms, the degree of availability of the infrastructure necessary for the provision of the Pix service to end users. It is calculated as follows:
id = hf / hp, where:
id = availability index of the Pix participant; hf = number of hours or fraction of effective functioning of the service for end users, over the calculation period; hp = number of hours in which the service should be open for use by end users, over the calculation period, according to the normal operating hours of 24 (twenty-four) hours per day and on all days of the year.

For the calculation of their availability index, Pix participants must follow the following instructions:
a. consider only the transactional service (transfers, payments, and receipts) for the end user, whether payer or receiver. Thus, the only functionality in the DICT that must be considered is the consultation; b. the transactional service must consider transactions processed outside the SPI and by the SPI, both by the primary channel and by the secondary message transmission channel;
c. the index must reflect the joint effect of all parts that affect the availability of the service to the end user and that are the responsibility of the participant or its partners, including the eventual provider of information technology services (PSTI) and the eventual clearing agent in the SPI, regardless of the origin of the unavailability;
d. the unavailability of the service to the end user that results from unavailability or instability in the SPI, in the DICT, in the Network of the National Financial System (RSFN) or in any other component of the infrastructure that is the responsibility of the Central Bank of Brazil (BC) must not be considered in the calculation of the index; e. the unavailability of the service to the end user that results from the user's connectivity failures or failures in their device or in applications installed on it must not be considered in the calculation of the index; and f. only the technical aspects of the transactional service must be considered in the calculation of the index, and any transactions rejected due to the participant's lack of liquidity must not be taken into consideration.

Pix participants have different availability index targets, according to the following categories 8:
a. category A: participants with the quantity of Pix transactions greater than 2.0% of the sum of transactions settled in the SPI by all participants, in the last year, as payer or as receiver; b. category B: participants with the quantity of Pix transactions between 2.0% and 0.5% of the sum of transactions settled in the SPI by all participants, in the last year, as payer or as receiver;
c. category C: participants with the quantity of Pix transactions between 0.5% and 0.1% of the sum of transactions settled in the SPI by all participants, in the last year, as payer or as receiver; and
d. category D: other participants 9.

For the participant to know in which category they are allocated, they must sum the quantity of Pix transactions sent in the immediately preceding year and sum the quantity of Pix transactions received in the same period. The highest value between the two sums must be considered for the calculation of their participation in relation to the total of transactions settled in the SPI. Participants without transactions settled in the period will be allocated in category D.

In the calculation of the sum of transactions of the direct participant, the transactions of the indirect participant to whom service is provided must be included. The indirect participant must consider only their transactions for the purpose of calculation and allocation in the category.

In the first quarter of each year, the BC will publish the sum of Pix transactions settled in the SPI in the previous year, so that participants can calculate their participation and thus obtain their category. The participant will remain in their category between July of the current year and June of the following year. For example, in the 1st quarter of 2023 the BC will publish the sum of Pix transactions settled in the SPI in 2022. The participant must comply with the target of their category between July 2023 and June 2024. From July 2024, the participant's category may change, depending on their participation in the total of transactions settled in the SPI in 2023, which will be published in the 1st quarter of 2024.

The calculation period for the availability index is monthly. All Pix participants must calculate their own availability index, and the BC may request, at any time, additional information from participants to validate the reported index, as well as use mechanisms to validate this information through information available in the infrastructure operated by the BC.

The monthly availability index target for each category of participant is as follows:

Category	Availability
A	99.5%
B	99.0%
C	98.5%
D	95.0%

4.4. ANS of the cycle of granting authorization of Automatic Pix by the payer user
The ANS of the cycle of granting authorization of Automatic Pix by the payer user will be monitored through indicators calculated by the SPI and through indicators reported by Pix participants. The indicators calculated by the SPI are the responsibility of direct participants. Therefore, their calculation will also consider the authorizations granted by end users of the indirect participants of the SPI to whom the direct participant provides clearing service. The indicators reported by Pix participants must consider only the authorizations granted by end users of the participant itself.

The granting of authorization by the payer user can be operationalized through 4 distinct journeys:

Journey 1: Payer user informs the receiver user of Automatic Pix as a form of payment (interaction external to the ecosystem);
Journey 2: Payer user reads a QR Code containing the recurrence data;
Journey 3: Payer user makes a payment through QR Code at the same time as authorizing the payment of future charges with Automatic Pix;
Journey 4: Payer user makes a payment through QR Code and, upon confirmation of the scheduling or settlement of the payment, receives an offer to pay future charges with Automatic Pix.

For the understanding of the indicators, the cycle of granting authorization of Automatic Pix by the payer user can be illustrated through the figure below.

21 • Pix Times Manual – Version 7.0

Journeys 1, 2 and 4
The timeline indicated in the figure represents the times used in the calculation of the ANS, which are detailed below:
t0´ – PSP of the payer receives request: the moment at which the PSP of the payer receives the confirmation of the authorization of Automatic Pix by the payer user. It is equivalent to the value of the field ProcessingDateTime (dataHoraTipoSituacaoDaRecorrencia), associated with the field MandateProcessingType filled with UPDT in the message pain.012, whose field MandateStatus is equal to ‘CFDB’, which will be sent to the SPI; t1 – PSP of the payer creates pain.012: the moment at which the PSP of the payer creates the message pain.012, equivalent to the field CreationDateTime (dataHoraCriacaoParaEmissao) of the said message. This time must be measured before the signature of the message; t1´ – SPI/ICOM receives pain.012: the moment at which the SPI receives the HTTP request with the message pain.012 from the PSP of the payer; t2 – SPI/ICOM makes message pain.012 available for consumption by the PSP of the receiver; t3´ – SPI/ICOM receives the HTTP request with the message pain.012 from the PSP of the receiver; t4 – SPI/ICOM makes the pain.012 available: the moment at which the message pain.012 is made available for consumption by the PSP of the payer; t5 – PSP of the payer informs the result of the authorization: the moment at which the PSP of the payer sends the notification to the payer user. Journey 3 In journey 3, although the settlement flows of the immediate payment and of the confirmation of the recurrence happen simultaneously from the perspective of the payer user, the sending of the transactions for

22 • Manual de Tempos do Pix – Versão 7.0

processing by the SPI occurs consecutively, meaning the payer's PSP must wait for the settlement flow to conclude before initiating the authorization flow.

Journey 3 is subject to the same SLAs as the settlement cycle regarding immediate payment, as well as the same SLAs as the authorization cycle described in this section.
The assessment of times in Journey 3 is similar to that of other journeys, with the following difference:
t0’ – Payer's PSP receives settlement confirmation: the moment at which the payer's PSP receives the pacs.002 message confirming the settlement of the payment order in the SPI. It is equivalent to the value of the ProcessingDateTime field (dataHoraTipoSituacaoDaRecorrencia), associated with the MandateProcessingType field filled with UPDT in the pain.012 message, whose MandateStatus field is equal to ‘CFDB’, which will be sent to the SPI; Therefore, for the time spent in the settlement of the immediate payment to be disregarded in the calculation of the SLA, in Journey 3, the indicator t0’ is equivalent to the moment of receiving the pacs.002 by the payer's PSP, confirming the settlement of the payment via QR code, and not to the moment of receiving the payer user's confirmation, as in other journeys.

4.4.1. Indicators calculated by the SPI
4.4.1.1. Time spent by the payer's PSP and the payer's PSP's liquidator in initiating the Pix Automatic authorization cycle:
Direct participant indicator, according to the table below:

Indicator	Percentile	Time
Time spent by the payer's PSP and the payer's PSP liquidator in initiating the Pix Automatic authorization cycle (t1 – t0´)	95%	3 seconds

In the calculation, operations in which the direct participant of the SPI acts as a liquidator of an indirect participant of the SPI will also be counted.

4.4.1.2. Time spent by the payee's PSP and the payee's PSP liquidator in confirming the Pix Automatic authorization cycle:
Direct participant indicator, according to the table below:

Indicator	Percentile	Time
Time spent by the payee's PSP and the payee's PSP liquidator in confirming the Pix Automatic authorization cycle (t3’ – t2)	95%	4.6 seconds

23 • Manual de Tempos do Pix – Versão 7.0

In the calculation, operations in which the direct participant of the SPI acts as a liquidator of an indirect participant of the SPI will also be counted.
If the payee's PSP does not send the pain.012 response message, the SPI will attribute to the calculation t3’ – t2 the value of 3,600 seconds, equivalent to the maximum time of 1 hour, as established in section 3.2.

4.4.2. Indicators reported by Pix participants
4.4.2.1. Payer user experience in granting Pix Automatic authorization
The calculation must be performed by the payer's PSP, according to the table below:

Indicator	Percentile	Time
Payer user experience in granting Pix Automatic authorization (t5 – t0’)	95%	20 seconds

The calculation of this indicator must be performed by all Pix participants, both direct and indirect participants of the SPI, and must include both Pix Automatic authorizations operationalized via the SPI 10 and those operationalized outside the SPI. The indicator must count Pix Automatic authorizations initiated through a payment transaction initiation service. In these cases, to measure times t5 and t0’, the figure of the payer user's payment initiation service provider must be considered equivalent to the payer user.

4.5. SLAs for sending information to the Central Bank
4.5.1. Sending Pix transactions settled at the participant to the BC
Participants must send information regarding Pix transactions settled in their systems (outside the SPI), in accordance with the terms of Article 2-A of Normative Instruction BCB No. 32, of October 26, 2020. The calculation of this indicator will be performed by the Central Bank based on the difference between the values of the DataHoraDaTransacao and DataHoraCriacaoParaEmissao fields of the TRCK.002 message, contained in the SPI Message Catalog.

10 Authorizations operationalized outside the SPI comprise: (i) situations in which the transactional accounts of the payer user and the payee user are in the same PSP; (ii) situations in which the transactional accounts are in two indirect PSPs that use the liquidation service of the same direct PSP; (iii) situations in which one of the accounts (payee user or payer user) is in an indirect PSP and the other in the direct PSP that provides it with liquidation services.

24 • Manual de Tempos do Pix – Versão 7.0

Indicator	Percentile	Time
Time elapsed between the execution of the transaction and the creation of the TRCK.002 message	99%	300 seconds

Compliance with participants' Service Level Agreements (SLAs)
Compliance with participants' Service Level Agreements (SLAs) is performed based on the calculation of the Quarterly General SLA Index (IGAt) using the following methodology:
Quarterly General SLA Index (IGAt)* = (∑IGAm)/3 Simple average of the IGAm of the quarter. The quarters are:
Quarter 1: January, February, and March
Quarter 2: April, May, and June
Quarter 3: July, August, and September
Quarter 4: October, November, and December
Monthly General SLA Index (IGAm) = CA – DR
Where:
CA (SLA compliance) = (Quantity of level 1 indicators met x 2 + Quantity of level 2 indicators met) / (Total quantity of level 1 indicators x 2 + Total quantity of level 2 indicators) DR (decrease due to recurrence) = (Quantity of level 1 indicators not met recurrently x 1%) + (Quantity of level 2 indicators not met recurrently* x 0.5%) *An indicator is considered recurrent if it is not met in the month of the IGA calculation and in the immediately preceding month. For the calculation of the IGAm, different weights are assigned according to the criticality of the indicator, aggregating indicators into two groups, level 1 and level 2, with level 1 indicators having greater weight, as they are more relevant to the Pix user experience. The description of the indicators that make up each level is listed in Sections 5.1 and 5.2 of this manual. The quarterly IGA (IGAt) is used for the purpose of SLA compliance, and the monthly IGA (IGAm) is monitored for monitoring purposes.

25 • Manual de Tempos do Pix – Versão 7.0

The assessment of compliance with participants' Service Level Agreements, when applicable, in accordance with the Pix Penalties Manual, is calculated by comparing the IGAt result to the reference value, described in Section 5.3 of this Manual. Participants who obtain a result equal to or higher than the reference value, according to their respective category, are considered regular for the purpose of SLA compliance.

5.1. Level 1 indicators
The following indicators listed in section 4 of this manual are considered at level 1:

Level 1 Indicators	Scope
4.5.1. Sending Pix transactions settled at the participant to the BC	Direct participants
4.1.2.1. Payer user experience (P50)	Direct and indirect participants
4.1.2.1. Payer user experience (P99)
4.1.2.2. Payer user experience in transactions settled outside the SPI (P50)
4.1.2.2. Payer user experience in transactions settled outside the SPI (P99)
4.2.2.1. Payer user experience in querying the DICT
4.2.2.2. Sending code to user email or cell phone number
4.2.2.3. User experience in key registration
4.2.2.4. User experience in key deletion
4.2.2.7. Opening of the MED after registration of the user's request
4.3. Participant availability index

5.2. Level 2 indicators
The other indicators listed in section 4 of this manual are considered less critical:

Level 2 Indicators	Scope
4.1.1.1. Time spent by the payer's PSP in initiating Pix (P50)	Direct participants
4.1.1.1. Time spent by the payer's PSP in initiating Pix (P95)
4.1.1.2. Time spent by the payee's PSP in authorizing Pix (P50)
4.1.1.2. Time spent by the payee's PSP in authorizing Pix (P95)
4.2.1.1. Receive new portability, possession claim, or infraction notification
4.2.1.2. Complete portability
4.2.1.3. Cancel portability due to lapse of time
4.2.1.4. Confirm possession claim due to lapse of time
4.2.1.5. Cancel possession claim due to lapse of time
4.2.1.6. Send result of analysis of an infraction notification
4.2.1.7. Perform synchronism verification
4.2.1.8. Conclude return request due to well-founded suspicion of fraud
4.2.1.9. Conclude return request due to payer's PSP operational failure

26 • Manual de Tempos do Pix – Versão 7.0

Level 2 Indicators	Scope
4.4.1.1. Time spent by the payer's PSP in initiating the Pix Automatic authorization cycle
4.4.1.2. Time spent by the payee's PSP in confirming the Pix Automatic authorization cycle
4.2.2.5. Notification of portability or possession claim to the donor user in an authenticated channel	Direct and indirect participants
4.2.2.6. Cancel or confirm portability or possession claim at the user's request
4.4.2.1. Payer user experience in granting Pix Automatic authorization

Indicators 4.4.1.1, 4.4.1.2, and 4.4.2.1, referring to the Pix Automatic authorization cycle, began to be counted in the IGA calculation as of July 1, 2025.

5.3. Categories, Targets, and References
For the purpose of SLA compliance, participants are grouped by category, and each category is assigned a reference value. For direct participants, the categories described in Section 4.3 of this manual apply. A specific category has been created for indirect participants, regardless of the quantity of Pix transactions as payer or payee, since they are responsible for a lower quantity of SLA indicators. The reference value is important so that participants have sufficient conditions to make the necessary adjustments to their systems, converging towards the achievement of the target. In this sense, it is worth highlighting that the reference value may be reviewed over time.

Category	Target	Reference Value
A	100%	90%
B	100%	86%
C	100%	83%
D	100%	80%
Indirects	100%	65%

SLAs of the Central Bank of Brazil
Aiming to give participants visibility into the Service Level Agreements applied to the main BC systems that support Pix, this chapter details the performance indicators of the SPI and DICT. BC SLA indicators are calculated on a monthly basis.

6.1. SPI SLA
6.1.1. Time spent in the SPI

27 • Manual de Tempos do Pix – Versão 7.0

SPI indicator, considering percentiles, according to the table below:

Indicator	Percentile	Time
Time spent in the SPI (t2 – t1') + (t5a – t3’), for payment orders sent to the primary message transmission channel of the SPI	50%	2.8 seconds
	99%	4.6 seconds
Time spent in the SPI (t2 – t1') + (t5a – t3’), for payment orders sent to the secondary message transmission channel of the SPI	99%	15 minutes

6.1.2. SPI availability index
SPI indicator, calculated monthly, considering a moving window of the last three months. It reflects the proportional amount of time the service was in usable condition for participants with access to the SPI. Unavailability is considered any situation in which a percentage equal to or greater than 80% of settlement requests is responded to with errors caused by the SPI or its infrastructure and that persists for more than 36 seconds.

Indicator	Target
SPI availability index	99.9%

6.2. DICT SLA
6.2.1. Time spent in the DICT (query)
DICT indicator, considering percentiles, according to the table below:

Indicator	Percentile	Time
Key queries	99%	1 second

6.2.2. Time spent in the DICT (update)
DICT indicator, considering percentiles, according to the table below:

28 • Manual de Tempos do Pix – Versão 7.0

Indicator	Percentile	Time
Key updates (all DICT functionalities, except query)	99%	5 seconds

6.2.3. DICT availability index
DICT indicator, calculated monthly, considering a moving window of the last three months for query operations, or twelve months for other operations. It reflects the proportional amount of time the service was in usable condition for participants with access to the DICT. Unavailability is considered any situation in which a percentage equal to or greater than 80% of requests is responded to with errors caused by the DICT or its infrastructure and that persists for more than 30 seconds.

Indicator	Target
DICT availability index (query)	99.9%
DICT availability index (update)	99.8%

29 • Manual de Tempos do Pix – Versão 7.0

Revision History

Date	Version	Description of changes
11/8/2020	1.0
10/9/2020	1.1	Inclusion of new section (3.2.1.4), with new SLA for possession claim cancellation for the claiming PSP.
Section 1: correction of the reference to the section to which the illustrative figure refers.
Section 3.2.2.3: correction of the claim flow steps
12/11/2020	2.0	Structure: Insertion of section 4 “Participant availability index”.
Section 1: removal of mention of transactions with suspicion of violation of regulations against “money” laundering and terrorism financing.
Section 2: Insertion of reference to Normative Instruction No. 5, which defines the maximum time limits for validation and for settlement of payment orders that run in the SPI.
Section 2: Removal of the possibility of differentiated maximum time for authorization of transaction initiation by the payer user's payment service provider, in cases of transactions with suspicion of violation of regulations against “money” laundering and terrorism financing. The differentiated maximum time now applies only to transactions with suspicion of fraud.
Section 3: clarification that, for the purpose of counting SLAs, all messages must be considered, including error messages.
Section 3.1.2.1: removal of mention of transactions with suspicion of violation of regulations against “money” laundering and terrorism financing.
Section 3.1.2.2: removal of mention of transactions with suspicion of violation of regulations against “money” laundering and terrorism financing.
Section 3.2.2.1: insertion of text to make clear that indicators regarding registration, deletion, and portability must consider only experiences occurring during the hours in which the functionalities are available to end users.

30 • Manual de Tempos do Pix – Versão 7.0

Date	Version	Description of changes
12/11/2020	2.0	Section 3.2.2.3: insertion of text to make clear that the indicator must consider only experiences occurring during the hours in which portability and possession claim functionalities are available to end users.
1/12/2020	2.1	Section 3.1: adjustment to the definition of t0’ for transactions in which the payer user is a legal entity.
24/2/2021	2.2	Section 3.1: adjustment to the text to make the definition of t0’ clearer for transactions in which the payer user is a natural person.
Section 3.2.1.1: adjustment to the 1st indicator to correct that, in the infraction notification, the SLA must be fulfilled by the PSP that received the notification, and not only by the payee's PSP, as stated in the previous version.
Section 3.2.1.1: adjustment to the 2nd indicator. The DICT did not control the indicator stated in the previous version. The new indicator provides only for an SLA for changing the status from “Confirmed” to “Concluded” by the claiming PSP in the portability process.
Section 4: exclusion of mentions of the adaptation period, without changing the availability index targets.
8/6/2021	2.3	Structure: insertion of subsection 3.2.1.7 “Conclude return request”, which presents the new SLA derived from the new return request functionality in the DICT.
Section 3.2.1.5: indicator is from the PSP that receives the infraction notification and not only from the payee's PSP; and modification of the SLA time, which now becomes 180 minutes after the seven-day deadline for analysis of an infraction notification.
22/7/2021	3.0	Structure: exclusion of section 3.1.1.3. There will no longer be an SLA for the time to wait to read messages.
Structure: exclusion of section 3.1.1.4. Indicator relocated to section 5.
Structure: insertion of section 5 “SLAs of the Central Bank of Brazil”.
Section 1: mention of Pix Cobrança (Collection) schedules with maturity and Pix transactions initiated through a payment transaction initiation service.
Section 2: mention of Pix transactions initiated through a payment transaction initiation service.
Section 3: adjustment to the section title, to make clear that these are the SLAs of Pix participants; and mention of Pix transactions initiated through a payment transaction initiation service.

31 • Manual de Tempos do Pix – Versão 7.0

Date	Version	Description of changes
22/7/2021	3.0	Section 3.1: clarification that transactions initiated by SPI indirect participants must be considered by direct participants providing the liquidation service; and exclusion of message availability and reading times.
Section 3.1.1.1: adjustment to the section title; clarification that the indicator refers only to direct participants of the SPI; reduction of the percentile to 95%; clarification that transactions initiated by indirect participants must be counted by their liquidator; and clarification of which transactions should not be considered in the indicator calculation.
Section 3.1.1.2: clarification that the indicator refers only to direct participants of the SPI; reduction of the percentile to 95%; and clarification of which transactions should not be considered in the indicator calculation.
Section 3.1.2.1: clarification of which transactions should not be considered in the indicator calculation; and mention of Pix transactions initiated through a payment transaction initiation service.
Section 3.1.2.2: clarification of which transactions should not be considered in the indicator calculation; and mention of Pix transactions initiated through a payment transaction initiation service.
Section 3.2: clarification that there are indicators that must be reported by all Pix participants (not only those with direct access to the DICT).
Section 3.2.1.1: (i) adjustment to the section title. The section retained only the SLA related to receipt. The SLA to complete portability was removed to section 3.2.1.2; and (ii) reduction of the percentile to 95% and increase of the time to 180 seconds.
Section 3.2.1.2: now refers to the SLA to complete portability. Reduction of the percentile to 95% and increase of the time to 180 seconds.
Section 3.2.1.3: corresponded to section 3.2.1.2 in the previous version. Reduction of the percentile to 95% and increase of the time to 60 minutes.
Section 3.2.1.4: corresponded to section 3.2.1.3 in the previous version. Reduction of the percentile to 95% and increase of the time to 60 minutes.
Section 3.2.1.5: corresponded to section 3.2.1.4 in the previous version. Reduction of the percentile to 95% and increase of the time to 60 minutes.

32 • Manual de Tempos do Pix – Versão 7.0

Date	Version	Description of changes
22/7/2021	3.0	Section 3.2.1.6: corresponded to section 3.2.1.5 in the previous version. Reduction of the percentile to 95% and reduction of the time to 7 days. Clarification that the 7-day time now applies only as of November 16, 2021.
Section 3.2.1.7: corresponded to section 3.2.1.6 in the previous version. Clarification that the indicator is only for participants with direct access to the DICT.
Section 3.2.1.8: corresponded to section 3.2.1.7 in the previous version. Introduction of the 95% percentile.
Section 3.2.2.1: adjustment to the section title. Now corresponds only to the SLA of the payer user experience in querying the DICT. Mention of Pix transactions initiated through a payment transaction initiation service.
Section 3.2.2.2: now refers to the SLA of sending the code to the user. Reduction of the percentile to 95%.
Section 3.2.2.3: now refers to the SLA of the user experience in key registration. Reduction of the percentile to 95%.
Section 3.2.2.4: now refers to the SLA of the user experience in key deletion. Reduction of the percentile to 95%.
Section 3.2.2.5: corresponded to section 3.2.2.2 in the previous version. Reduction of the percentile to 95%.
Section 3.2.2.6: corresponded to section 3.2.2.3 in the previous version. Reduction of the percentile to 95%.
Section 4: alteration in the classification criteria of participants in categories; and reduction of the targets of all categories.
01/12/2021	3.1	Section 3.1.2.1: exclusion of operations interrupted by receiver timeout from payer user experience indicators.
Section 3.2.1.7: synchronism calculation now calculated monthly, with applied percentile of 95.
Section 3.2.2.5: indicator target now defined in seconds (600), in alignment with the instructions for filling out document 1201.
Section 4: clarification that transactions considered for the definition of the Availability Index category are only those run in the SPI.
23/12/2021	4.0	Structure: alteration of section of the Participant Availability Index, which moves from section 4. to section 3.3
Section 3: adjustment to the section title, which now becomes titled Indicators for calculating Participants' Service Level Agreements (SLAs)
Structure: insertion of section 4. Compliance with participants' Service Level Agreements (SLAs)
Section 3.1 and Section 3.2: editorial adjustments
Section 3.2.1.3, Section 3.2.1.4, Section 3.2.1.5, and Section 3.2.1.6: Adjustment to the indicator name
2/1/2023	4.1	Section 2: insertion of text to make clear that transactions for the purpose of withdrawal or change are not subject to prolonged time for authorization of transaction initiation by the payer's PSP, in the case of transactions with suspicion of fraud.
Section 3.3: insertion of text to make clear that participants without transactions settled between April and June 2021 have a target availability index of category D.
2/5/2023	5.0	Section 3.3: alteration in the calculation methodology for classifying participants in the target categories of the participant availability index.
---	---	---
29/10/2023		Structure: section 1 divided into three subsections: 1.1. Payment orders sent to the primary message transmission channel of the SPI; 1.2. Payment orders sent to the secondary message transmission channel of the SPI; and 1.3. Payment orders settled outside the SPI.
Section 2: update of the norm number.
Section 3.1.1.2: insertion of text to make clear that the indicator should not count transactions sent to the secondary channel.
Section 5.1.1: creation of indicator for the secondary channel.
01/01/2024	5.1	Section 3.2.2.7: new subsection, with insertion of new indicator of time to open infraction notification for return request after registration of the user's request.
---	---	---
01/11/2024	6.0	Section 2: alteration in the text to not allow time maximum rules for authorization of transactions with suspicion of fraud to be applied in transactions between accounts of the same ownership.

33 • Manual de Tempos do Pix – Versão 7.0

34 • Pix Timeliness Manual – Version 7.0

Section 4.1.2.2: Change of the indicator name from "Payer user experience in transactions settled within the same institution" to "Payer user experience in transactions settled outside the SPI".

Section 4.3: Insertion of item b to clarify that, in the calculation of the Availability Index, the participant must consider transactions settled outside the SPI and via the SPI, processed through both the primary and secondary message transmission channels.

16/06/2025 Structure: Inclusion of section 3. Maximum Times for Pix Automatic. As a consequence, the old sections 3, 4, and 5 now have an increased numbering, becoming 4, 5, and 6, respectively.

Structure: Insertion of subsection 4.4. ANS of the Pix Automatic authorization cycle by the payer user, subdivided into subsections 4.4.1 and 4.4.2.

Section 5.2: Inclusion of the three new ANS indicators for Pix Automatic in the list of level 2 indicators that make up the calculation of the IGA.

16/06/2025 6.1 Section 2: Change in the text to restrict, to Intelligent Transactions of Open Finance, the prohibition of using the maximum time of 30 minutes for authorization of transactions with suspicion of fraud, in addition to transactions for the purpose of withdrawal or change.

Section 5.2: Insertion of text to establish that the ANS indicators of the Pix Automatic authorization cycle will be incorporated into the IGA calculation of participants starting from July 1, 2025.

23/11/2025 7.0 Inclusion of new section 1.4, regarding the maximum time for sending transactions settled outside the SPI to the BC.

Section 4.2.2.7: Change of the indicator "Opening of infringement notification for request for return after registration of the user's demand" to "Opening of the MED after registration of the user's demand".

02/02/2026 Section 4.2.1.8: Change of the indicator "Complete return request" to "Complete return request due to well-founded suspicion of fraud".

Section 4.2.1.9: Creation of the indicator "Complete return request due to operational failure of the payer's PSP".

Section 4.4.1.2: Inclusion of passage to clarify that the SPI will assign the value of 3,600 seconds, equivalent to the maximum time of section 3.2, for the calculation of the indicator in situations where the receiver's PSP does not send the pain.012 response.

35 • Pix Timeliness Manual – Version 7.0

Inclusion of new section "4.5. ANS of sending information to the Central Bank", and creation of the new indicator "4.5.1. Sending of Pix transactions settled at the participant to the BC".

Section 5.2: Insertion of the new indicators 4.2.1.9 and 4.5 into the IGA calculation.

Pix Time Manual Version 7.0