Payments
Practical Guide to Payment Methods
With the evolution of payment systems, different methods have been developed to facilitate financial transactions, each with its own particularities and advantages. In this guide, we will explore three widely used methods: Copy and Paste Payment, PIX Key Payment, and Bank Details Payment.
Copy and Paste
Copy and Paste payment in the Pix system is a practical and quick way to make transactions. It works through the use of a QR code that is converted into text, allowing the payer to copy this text and paste it into the specific field of their bank or financial institution app to complete the payment. This method is especially useful in situations where the user cannot scan the QR code, such as in online purchases or when using a device that does not support a camera.
PIX Key
PIX Key payment is one of the most popular and convenient ways to make transfers using the Pix system. The PIX Key is a unique identifier that the user associates with their bank account to facilitate transfers and receipts. The user can simply provide the PIX Key, which can be one of the following identifiers:
- CPF/CNPJ: The CPF number (for individuals) or CNPJ (for companies).
- Email: An email address associated with the account.
- Phone number: The mobile number associated with the account.
- Random key: A randomly generated alphanumeric code that contains no personal information.
Bank Details
In bank details payment, the payer does not use a PIX key, but instead uses the full bank account information of the recipient to complete the transfer. These details include account number, branch, account holder’s name, and document number.
PIX Payment Error Codes
| Error Code | Error Name | Description | Error Origin |
|---|---|---|---|
| AB03 | AbortedSettlementTimeout | Transaction settlement aborted due to SPI timeout. | SPI |
| AB09 | ErrorCreditorAgent | Transaction aborted due to error in the recipient user’s participant. | Recipient participant |
| AB11 | TimeoutDebtorAgent | Timeout from the payment order issuer participant. | SPI |
| AC03 | InvalidCreditorAccountNumber | Nonexistent or invalid branch and/or account number of the recipient. | Recipient participant |
| AC06 | BlockedAccount | Recipient’s account is blocked. | Recipient participant |
| AC07 | ClosedCreditorAccountNumber | Recipient’s account is closed. | Recipient participant |
| AC14 | InvalidCreditorAccountType | Incorrect account type for the recipient. | Recipient participant |
| AG03 | TransactionNotSupported | Transaction type not supported/authorized for the recipient's account (e.g., transfer to a salary account). | Recipient participant |
| AG12 | NotAllowedBookTransfer | Payment/return orders in SPI between accounts of the same institution or using the same settlement participant are not allowed. | SPI |
| AG13 | ForbiddenReturnPayment | It is not allowed to return a return of an instant payment. | SPI |
| AGNT | IncorrectAgent | Direct participant is not the settlement agent of the payer’s institution. | SPI |
| AM01 | ZeroAmount | Instant payment order with a zero value. | SPI |
| AM02 | NotAllowedAmount | Payment/return order exceeds the allowed limit for the recipient’s account type. | Recipient participant |
| AM04 | InsufficientFunds | Insufficient balance in the payer participant’s PI account. | SPI |
| AM09 | WrongAmount | Returned payment exceeds the amount of the original instant payment order. | Recipient participant |
| AM12 | InvalidAmount | Mismatch between the sum of the valorDoDinheiroOuCompra block and the valor field. | SPI |
| AM18 | InvalidNumberOfTransactions | Invalid number of transactions. | SPI |
| BE01 | InconsistenWithEndCustomer | CPF/CNPJ of the recipient does not match the account holder. | Recipient participant |
| BE05 | UnrecognisedInitiatingParty | Payment initiator’s CNPJ is not registered in the Pix arrangement. | SPI |
| BE17 | InvalidCreditorIdentificationCode | QR Code rejected by the recipient’s institution. | Recipient participant |
| CH11 | CreditorIdentifierIncorrect | Incorrect CPF/CNPJ of the recipient. | Recipient participant |
| CH16 | ElementContentFormallyIncorrect | Incorrect or non-compliant message content. | SPI |
| DS04 | OrderRejected | Order rejected by the recipient’s participant. | Recipient participant |
| DS0G | NotAllowedPayment | Participant signing the message is not authorized to operate on the debited PI account. | SPI |
| DS24 | WaitingTimeExpired | Order rejected due to delay between the pain.013 and pacs.008 messages. | Recipient participant |
| DS27 | UserNotYetActivated | Participant is not registered or has not started operation in SPI. | SPI |
| DT02 | InvalidCreationDate | Invalid message date and time. | SPI |
| DT05 | InvalidCutOffDate | Transaction exceeds the maximum return period defined by Pix. | Recipient participant |
| ED05 | SettlementFailed | Error processing the instant payment (generic error). | SPI / Recipient participant |
| FF07 | InvalidPurpose | Inconsistency between transaction purpose and the Structured block. | SPI |
| FF08 | InvalidEndToEndId | Malformed operation identifier. | SPI |
| MD01 | NoMandate | ISPB of the Pix Withdrawal or Pix Change facilitator is nonexistent. | SPI |
| OZ01 | InsufficientBalance | Insufficient balance. | — |
| RC09 | InvalidDebtorClearingSystemMemberIdentifier | ISPB of the payer's participant is invalid or nonexistent. | SPI |
| RC10 | InvalidCreditorClearingSystemMemberIdentifier | ISPB of the recipient's participant is invalid or nonexistent. | SPI |
| RR04 | Regulatory Reason | Payment order where the payer is sanctioned by UN Security Council resolution. (If the recipient is sanctioned, the order should not be rejected.) | Recipient participant |
| SL02 | SpecificServiceOfferedByCreditorAgent | Original transaction not related to Pix Withdrawal or Pix Change services. | Recipient participant |
| OZ02 | Processing Error | Processing error. | — |
Updated 29 days ago