Card network retry program
The retry limit for a denied purchase on the same card, per card brand.
What are retries?
When a customer tries to make a card purchase in your store, the transaction may be declined for several reasons. Subsequent attempts to complete the transaction with the same card are called retries.
Card purchase transactions (card present or card not present) and Zero Auth transactions (card validation) are subject to the card networks' retry rules.
Fees and limits by network
Each card network sets specific fees for retries, and the number of attempts allowed before fees apply also varies by network.
Card present and card not present
The networks define distinct rules for card present and card not present transactions, such as online sales.
Penalties for exceeding the limits
E-commerce merchants that do not follow the retry rules may be penalized with additional fees for exceeded transactions, according to each network's program.
Reversible and irreversible declines
Aiming to improve the purchase experience, the payments industry, in partnership with ABECS, standardized the response codes for declined card transactions. Retry attempts were classified into two types, irreversible and reversible.
Irreversible: never retry
This type of decline indicates that the card is canceled, was lost or stolen, there is confirmed fraud, or the transaction is not allowed for the specific product. In any of these situations, the issuer will never grant an approval. If an authorization attempt occurs after an irreversible decline, without changing any data in the request, the transaction will continue to be declined.
Reversible: retry allowed
In this case, the issuer may eventually approve the transaction, but does not do so at that moment due to temporary problems such as a system failure, insufficient available limit, suspected fraud, or an excessive number of incorrect PIN entry attempts. These declines are temporary and may change over time, allowing approval on a new attempt.
Visa, Mastercard and Elo adjusted their rules to limit the number of authorization attempts on declined transactions. These changes establish fees when the number of attempts exceeds the allowed limit. See below the specific rules for each network.
Mastercard
Mastercard has the Transaction Processing Excellence (TPE) program, which covers two categories:
- Excessive Attempts: monitors retries of declined transactions in card present and card not present environments. Valid for both reversible and irreversible decline codes.
- Merchant Advice Code Transaction Excellence (MAC): monitors retries of declined transactions in card not present environments that are irreversible. Fees apply only to MAC 03 and 21.
Excessive Attempts
These are charges applied when the merchant exceeds the transaction retry rules.
The network also monitors any nominal-amount authorization, approved, with a subsequent refund, for transactions below 1 whole currency unit or the equivalent of US$ 1.
Monitoring applies to retries of declined and approved purchase transactions, made in card present and card not present environments.
Excessive Attempts table:
| Categories | Codes | Effective period | Domestic fee | International fee | When it occurs | Retry allowed |
|---|---|---|---|---|---|---|
| Card present and card not present | Any decline code not assigned to MAC 03 and 21. Also the MAC codes if the "Excessive Attempts" limits are not respected | Until 31/01/2023 | R$ 2.00 | * | From the 11th retry onward | Retry allowed after 24h. |
| Card present and card not present | Any decline code not assigned to MAC 03 and 21. Also the MAC codes if the "Excessive Attempts" limits are not respected | In effect since 01/02/2023 | R$ 2.00 | * | From the 8th retry onward | Retry allowed after 24h. |
- All payment transactions on the same card and same merchant number are considered retries;
- Mastercard postponed the effective date of the new Excessive Attempts program rules to 01/02/2023, previously scheduled to start on 01/11/2022. Here are the changes:
- The excess considered in the program will start from the eighth retry within the assessment month; the amounts charged were changed.
- Mastercard is also introducing a limit of 35 declined attempts on the same card and same merchant number over a continuous 30-day period. Even if the store does not exceed the limit of seven retries within 24h, but exceeds the monthly limit, the fee will be applied.
The current Excessive Attempts program rule has been in effect since 01/02/2023 (Excessive Attempts table): the fee applies from the 8th retry of the same transaction (same card and same merchant number), and retrying is allowed after 24 hours. Until 31/01/2023 the previous rule applied, allowing 10 attempts before the fee.
Merchant Advice Code Transaction Excellence (MAC)
These are charges applied when the merchant retries an authorization request for irreversible response codes with the same card, valid for card not present.
Within this retry program, there are programs specifically targeted at the "Do not retry this transaction" scenario. For those cases, Mastercard identifies the transactions with the values MAC 03 and MAC 21, for example.
The MAC program includes several values, but only MAC 03 and 21 carry a specific fee. The other MACs do not fall under this fee.
The other MAC codes (01, 02, 04, 24, 25, 26, 27, 28, 29, 30, 40 and 41) are not part of the MAC fee program, but they do count toward the Excessive Attempts program fee if the limits are exceeded.
Since 14/10/2022 Mastercard introduced new MAC codes (24, 25, 26, 27, 28, 29 and 30) when an issuer declines a transaction with response code 51 (insufficient funds) followed by one of the MACs in the table below, so the merchant can take the best action.
Table with the full list of MACs:
| MAC | Description | Note |
|---|---|---|
| 01 | New account information available (ABU) | The account data used in the transaction needs to be updated, using ABU, for example. |
| 02 | Cannot approve at this time, try later | Retry the transaction after 72 hours or try the transaction with a different payment method. |
| 03 | Retry not allowed | Find another way to secure the payment, avoiding unnecessary costs from multiple authorization requests that will continue to result in declines. |
| 04 | Token requirements not met for this token model | The token requirements need to be reviewed, as they were not met for the token model sent in the transaction. |
| 21 | Plan canceled | The buyer cancels a plan and, even after the cancellation, the merchant keeps sending purchase authorization requests. |
| 24 | Retry after 1 hour | Valid only for response code 51 (insufficient funds). |
| 25 | Retry after 24 hours | Valid only for response code 51 (insufficient funds). |
| 26 | Retry after 2 days | Valid only for response code 51 (insufficient funds). |
| 27 | Retry after 4 days | Valid only for response code 51 (insufficient funds). |
| 28 | Retry after 6 days | Valid only for response code 51 (insufficient funds). |
| 29 | Retry after 8 days | Valid only for response code 51 (insufficient funds). |
| 30 | Retry after 10 days | Valid only for response code 51 (insufficient funds). |
| 40 | Retry not allowed | Non-reloadable prepaid card for consumption. |
| 41 | Retry not allowed | Consumer single-use virtual card. |
In addition, some return codes will no longer be sent:
- 04 (Capture card)
- 14 (Invalid card number)
- 43 (Stolen card)
- 54 (Expired card)
- 57 (Transaction not permitted)
- 62 (Restricted card)
- 63 (Security violation)
Mastercard return categorization
Mastercard may consolidate some issuer response codes, which often do not tell the merchant whether a retry is allowed, into three Mastercard-exclusive codes:
- 79 (Lifecycle);
- 82 (Policy);
- 83 (Fraud/Security).
The original codes will be replaced by the Merchant Advice Code (MAC), which will accompany codes 79, 82 and 83 to determine whether the transaction can be retried.
For example:
| When | Then | And the response code |
|---|---|---|
| The issuer declines the transaction using response code 54 (Expired card) | Mastercard will replace code 54 with code 79 (lifecycle decline) | Accompanied by the corresponding Merchant Advice Code (MAC) |
MAC 03 and MAC 21 retry program
Assessment method:
- Card not present transactions are considered;
- All payment transactions on the same card and same merchant number are considered retries;
- Retries in the MAC program with values MAC 03 and MAC 21 are counted;
- Valid for any response code;
- The excess counted in the program starts from the 1st retry within the assessment month;
- The counter resets after the 30-day period;
- Retries can be charged under MAC 03/21 and under Excessive Attempts if the limit of each program is exceeded;
- The fee was R$ 1.25 and, starting January 1, 2023, the amount listed below took effect.
Fee table:
| Retry number | Rule |
|---|---|
| From the 1st retry onward | R$ 2.50 (two reais and fifty cents) per retry, starting from the 1st retry. |
Visa
The retry program established by Visa generates charges when the merchant exceeds the retry rules.
The goal is to create balance in the transaction ecosystem to ensure that acquirers and merchants provide accurate information about retries and reduce unnecessary new attempts.
The network requires issuers to use correct, non-generic response codes to make it easier to identify the reason a transaction was declined.
Visa splits these codes into reversible and irreversible, valid for both card present and card not present transactions:
- Reversible codes: up to 20 attempts to approve the same transaction are allowed (with the same card, transaction, expiration date, amount and merchant) within a 30-day period. After 30 days, counted from the first attempt, any retry will be charged. Once the 30-day period has passed, if a retry of the same transaction is sent, the fee will already be applied. Thus, the 20-attempt rule no longer applies and the 30 consecutive-day period takes effect.
- Irreversible codes: only the 1st attempt to approve the transaction is allowed (with the same card, transaction, expiration date, amount and merchant). On the second attempt, the transaction will already be charged, regardless of when it occurs.
Fees: when the attempt limits set by the network are exceeded, a fee is charged for each exceeding transaction.
- Domestic: USD 0.10 + 13.83% tax;
- Foreign: USD 0.25 + 13.83% tax.
Fees have applied since April 2021.
Visa grouped the return codes into four categories:
- Category 1: issuer will never approve. Indicates that the card was canceled or never existed, or that the decline is the result of a permanent restriction or error condition that will prevent a future approval.
- Category 2: issuer cannot approve at this time. Indicates that the decline is the result of a temporary condition such as credit risk, issuer velocity controls or other card restrictions that may allow a retried transaction to be approved. In some cases, the decline requires an action from the cardholder or issuer to remove the restriction before an approval can be obtained.
- Category 3: data quality. When a data error is identified by the issuer, the transaction is declined as a consequence. Merchants must revalidate payment data before retrying. Merchants and acquirers must monitor these decline codes due to the potential fraud exposure. Note: category 3 has, in addition to the limits considered in category 2, a different limit that is cumulative. A merchant can perform up to 25,000 transactions in a 30-day period (in this case considering only the merchant number and decline codes). If the limit is exceeded, all transactions declined under category 3 will be charged.
- Category 4: generic response codes. Category 4 includes all other decline response codes not in categories 1, 2 and 3, since there may be circumstances where no response code value exists for a specific decline condition. Issuers may use other response code values defined in the VisaNet Technical Specifications; however, their use must remain minimal.
Issuers must use response codes that most accurately reflect the reason for the declines. That is, focus on categories 1 (the issuer will never approve), 2 (the issuer cannot approve at this time) and 3 (data quality) and avoid using 4 (generic response code). Issuers must limit this category as much as possible. The Category 4 fee is charged to ensure that no more than the regionally approved percentage of the issuer's total declines are categorized as Category 4. Issuers that exceed the regionally defined limit will receive the Generic Response Code Fee on a per-transaction basis for each decline in excess of the defined limit.
Table with the rules and decline codes. The rules in the table below are valid for both purchase transactions and Zero Auth transactions:
| Category | Type | Codes | Rules |
|---|---|---|---|
| Category 1 Issuer will not approve new attempts | Irreversible | 04 - Pick up card 07 - Pick up card, special conditions 12 - Invalid transaction 14* - Invalid account number 15 - Issuer does not exist 41 - Pick up card (lost card) 43 - Pick up card (stolen card) 46 - Closed account 57 - Transaction not permitted to cardholder R0 - Stop payment order R1 - Revocation of authorization order R3 - Revocation of all authorization orders | Fee charged from the 2nd attempt onward. |
| Category 2 Issuer will not approve at this time; new attempts are allowed | Reversible | 03 - Invalid merchant 19 - Re-enter the transaction 39** - No credit account 51 - Insufficient funds 52** - No checking account 53** - No savings account 59 - Suspected fraud 61 - Exceeds withdrawal amount limits 62 - Restricted card (card invalid in the region or country) 65 - Exceeds withdrawal frequency 75 - Allowed number of PIN entry attempts exceeded 78 - Blocked, first use or special condition (the account is temporarily blocked) 86 - ATM malfunction 91 - Issuer or switch inoperative 93 - The transaction cannot be completed (violation of law) 96 - System malfunction N3 - Cash withdrawal service unavailable N4 - Cash request exceeds issuer limit Z5*** - Valid account, but amount not supported 5C**** - Transaction not supported/blocked by the issuer 9G**** - Blocked by the cardholder (contact the cardholder). | Fee charged from the 16th attempt onward: the merchant may retry the same transaction 15 times. From the 16th attempt (with the same card, transaction, expiration date, amount and merchant) within a period of 30 consecutive days from the 1st attempt, the transaction will be charged. Once the 30-day period has passed, Visa does not allow any new attempt. So, if an attempt for that same transaction is sent, the fee will already be applied to that retry (at which point the 15-attempt rule no longer applies and the 30 consecutive-day period takes effect). |
| Category 3 Data quality | Reversible | 54 - Expired card 55 - Incorrect PIN 70 - PIN data required (Europe region only) 82 - Negative CAM, dCVV, iCVV or online CVV results 1A - Additional customer authentication required (Europe region only) 6P - Verification failure (cardholder identification does not match issuer records) N7 - Decline due to CVV2 failure (Visa) | Fee charged from the 16th attempt onward: the merchant may retry the same transaction 15 times. From the 16th attempt (with the same card, transaction, expiration date, amount and merchant) within a period of 30 consecutive days from the 1st attempt, the transaction will be charged. Once the 30-day period has passed, Visa does not allow any new attempt. So, if an attempt for that same transaction is sent, the fee will already be applied to that retry (at which point the 15-attempt rule no longer applies and the 30 consecutive-day period takes effect). |
| Category 4 Generic response codes | Reversible | Generic response codes not listed in categories 1, 2, 3 | Fee charged from the 16th attempt onward: the merchant may retry the same transaction 15 times. From the 16th attempt (with the same card, transaction, expiration date, amount and merchant) within a period of 30 consecutive days from the 1st attempt, the transaction will be charged. Once the 30-day period has passed, Visa does not allow any new attempt. So, if an attempt for that same transaction is sent, the fee will already be applied to that retry (at which point the 15-attempt rule no longer applies and the 30 consecutive-day period takes effect). |
Since April 2023, the allowed total decline count limit for category 3 went from 10,000 to 25,000 declines in a 30-day billing cycle.
Elo
The rules presented below took effect in January 2025.
The goal of the change is to ensure that merchants and acquirers reduce unnecessary new approval attempts.
Transactions are assessed monthly, counted from the 1st to the last calendar day of the violation month.
Fee amounts:
| Fee |
|---|
| R$ 0.80 (eighty cents) for each exceeded attempt |
Charging rules by group
The network will consider reversible and irreversible codes according to groups split into three categories. Below are the changes that took effect:
| Group | Description | Fee |
|---|---|---|
| Group 1 | Card not present transactions declined with irreversible codes, considering the same card number, same merchant CNPJ and same amount. | The fee applies from the 2nd retry within the assessment month. |
| Group 2 | Card not present transactions declined with reversible codes. | The fee applies from the 16th retry within the assessment month. |
| Group 3 | Card not present transactions declined with Brute Force Attack characteristics, considering transactions with the same merchant root CNPJ. | Applies from 10,001 declined transactions (within the code category) that exceed 5% of total declines, depending on the payment transaction volume of the CNP involved. |
Group classification:
| Group 1 Issuer will never approve (IRREVERSIBLE) | Group 2 Issuer cannot approve at this time (REVERSIBLE) | Group 3 Data quality, revalidate information (*) |
|---|---|---|
| 57 - Not allowed | 51 - Insufficient limit | 54 - Expired card |
| 14 or 56 - Invalid card (*) | 59 - Suspected fraud | 55 - Invalid PIN |
| 58 - Invalid merchant | 04 - Redo the transaction | 82 - Invalid card cryptogram |
| 46 - Closed account | 06 - Contact acquirer | 63 - CVE invalid or not present |
| FM - Use the chip | 38 - Purchase PIN attempts exceeded | |
| 19 - Contact acquirer | 61 - Withdrawal amount exceeded | |
| 12 - Card error | 62 - Temporary delinquency block | |
| 30 - Messaging format error | 65 - Withdrawal count exceeded | |
| 13 - Invalid transaction amount | 75 - PIN attempts exceeded / withdrawal | |
| 23 - Invalid installment amount | 78 - New card not unblocked or blocked by the customer APP/NFC/E-COM | |
| 41 - Lost card | 91 - Issuer offline | |
| 43 - Stolen card | ||
| 64 - Invalid minimum transaction amount | ||
| 83 - PIN encryption error | ||
| 76 - Invalid destination account | ||
| 77 - Invalid source account |
Other networks
- Reversible codes: new retries will be allowed for the same customer and card. There is no pre-established limit or period. Important: before making a new attempt, follow the guidance received in the declined transaction response.
- Irreversible codes: no authorizations will be allowed for the same card or merchant after receiving the 1st decline response from the issuer.
Retry by return code
The table below maps the codes returned in returnCode to their meaning, the recommended action, and whether a retry is allowed.
| Response code | Definition | Meaning | Action | Allows retry |
|---|---|---|---|---|
| 0 | Transaction successfully authorized. | Transaction successfully authorized. | Transaction successfully authorized. | No |
| 002 | Invalid credentials | There is a block on the terminal at PayZu | Contact PayZu e-commerce support | Yes |
| 2 | Transaction not authorized. Referred transaction. | Transaction not authorized. Referred (suspected fraud) by the issuing bank. | Transaction not authorized. Contact your issuing bank. | No |
| 9 | Transaction partially canceled successfully. | Transaction partially canceled successfully | Transaction partially canceled successfully | No |
| 11 | Transaction successfully authorized for a card issued abroad | Transaction successfully authorized. | Transaction successfully authorized. | No |
| 21 | Cancellation not performed. Transaction not found. | Could not process the cancellation. If the error persists, contact PayZu. | Could not process the cancellation. Try again later. If the error persists, contact the online store. | No |
| 22 | Invalid installment plan. Invalid number of installments. | Could not process the transaction. Invalid number of installments. If the error persists, contact PayZu. | Could not process the transaction. Invalid amount. Redo the transaction confirming the data provided. If the error persists, contact the online store. | No |
| 24 | Invalid number of installments. | Could not process the transaction. Invalid number of installments. If the error persists, contact PayZu. | Could not process the transaction. Invalid number of installments. Redo the transaction confirming the data provided. If the error persists, contact the online store. | No |
| 60 | Transaction not authorized. | Transaction not authorized. Try again. If the error persists, the cardholder should contact the issuing bank. | Could not process the transaction. Try again later. If the error persists, contact your issuing bank. | Only 4 times within 16 days. |
| 67 | Transaction not authorized. Card blocked for purchases today. | Transaction not authorized. Card blocked for purchases today. The block may have been caused by too many invalid attempts. The card will be automatically unblocked at midnight. | Transaction not authorized. Card temporarily blocked. Contact your issuing bank. | From the next day on, only 4 times within 16 days. |
| 70 | Transaction not authorized. Limit exceeded/no balance. | Transaction not authorized. Limit exceeded/no balance. | Transaction not authorized. Contact your issuing bank. | From the next day on, only 4 times within 16 days. |
| 72 | Cancellation not performed. Insufficient balance available for the cancellation. | Cancellation not performed. Insufficient balance available for the cancellation. If the error persists, contact PayZu. | Cancellation not performed. Try again later. If the error persists, contact the online store. | No |
| 79 | Mastercard transaction not allowed for this card | Transaction not authorized. Cannot process the transaction due to an error related to the cardholder's card. Ask the cardholder to contact the issuing bank. | Contact your bank | No |
| 80 | Transaction not authorized. Mismatch in the transaction/payment date. | Transaction not authorized. Invalid transaction date or first payment date. | Transaction not authorized. Redo the transaction confirming the data. | No |
| 82 | Mastercard transaction not authorized. Call the issuer | Transaction not authorized due to issuer rules. Advise the cardholder to contact the issuing bank. | Contact your bank | No |
| 83 | Mastercard transaction suspected of fraud | Transaction not authorized. Suspected fraud by the issuing bank. | Contact your bank | No |
| 85 | Transaction not allowed. Operation failure. | Transaction not allowed. There was a processing error. Ask the cardholder to enter the card data again; if the error persists there may be a problem with the merchant terminal, in which case the merchant should contact PayZu. | Transaction not allowed. Enter the card data again. If the error persists, contact the online store. | No |
| 89 | Transaction error. | Transaction not authorized. Transaction error. The cardholder should try again and, if the error persists, contact the issuing bank. | Transaction not authorized. Transaction error. Try again and, if the error persists, contact your issuing bank. | Only 4 times within 16 days. |
| 90 | Transaction not allowed. Operation failure. | Transaction not allowed. There was a processing error. Ask the cardholder to enter the card data again; if the error persists there may be a problem with the merchant terminal, in which case the merchant should contact PayZu. | Transaction not allowed. Enter the card data again. If the error persists, contact the online store. | No |
| 97 | Amount not allowed for this transaction. | Transaction not authorized. Amount not allowed for this transaction. | Transaction not authorized. Amount not allowed for this transaction. | No |
| 98 | System/communication unavailable. | Transaction not authorized. Issuer system out of communication. If it is widespread, check SITEF, GATEWAY and/or connectivity. | Your transaction cannot be processed. Try again later. If the error persists, contact the online store. | Only 4 times within 16 days. |
| 475 | Cancellation timeout | The application did not respond within the expected time. | Try again after a few seconds. If it persists, contact Support. | No |
| 999 | System/communication unavailable. | Transaction not authorized. Issuer system out of communication. Try again later. It may be a SITEF error, please check! | Your transaction cannot be processed. Try again later. If the error persists, contact the online store. | From the next day on, only 4 times within 16 days. |
| AA | Time exceeded | Time exceeded in the communication with the issuing bank. Advise the cardholder to try again; if the error persists the cardholder will need to contact the issuing bank. | Time exceeded in the communication with the issuing bank. Try again later. If the error persists, contact your bank. | Only 4 times within 16 days. |
| AF | Transaction not allowed. Operation failure. | Transaction not allowed. There was a processing error. Ask the cardholder to enter the card data again; if the error persists there may be a problem with the merchant terminal, in which case the merchant should contact PayZu. | Transaction not allowed. Enter the card data again. If the error persists, contact the online store. | No |
| AG | Transaction not allowed. Operation failure. | Transaction not allowed. There was a processing error. Ask the cardholder to enter the card data again; if the error persists there may be a problem with the merchant terminal, in which case the merchant should contact PayZu. | Transaction not allowed. Enter the card data again. If the error persists, contact the online store. | No |
| AH | Transaction not allowed. Credit card being used as debit. Use the credit function. | Transaction not allowed. Credit card being used as debit. Ask the cardholder to select the Credit Card payment option. | Transaction not authorized. Try again selecting the credit card payment option. | No |
| AI | Transaction not authorized. Authentication was not performed. | Transaction not authorized. Authentication was not performed. The cardholder did not complete the authentication. Ask the cardholder to review the data and try again. If the error persists, contact PayZu providing the BIN (first 6 digits of the card) | Transaction not authorized. Authentication was not completed successfully. Try again and enter the requested data correctly. If the error persists, contact the merchant. | No |
| AJ | Transaction not allowed. Credit or debit transaction in an operation that only allows Private Label. Try again selecting the Private Label option. | Transaction not allowed. Credit or debit transaction in an operation that only allows Private Label. Ask the cardholder to try again selecting the Private Label option. If the Private Label option is not available, check with PayZu whether your merchant account allows this operation. | Transaction not allowed. Credit or debit transaction in an operation that only allows Private Label. Try again and select the Private Label option. If a new error occurs, contact the online store. | No |
| AV | Transaction not authorized. Invalid data | Failure validating the transaction data. Advise the cardholder to review the data and try again. | Data validation failure. Review the data provided and try again. | Only 4 times within 16 days. |
| BD | Transaction not allowed. Operation failure. | Transaction not allowed. There was a processing error. Ask the cardholder to enter the card data again; if the error persists there may be a problem with the merchant terminal, in which case the merchant should contact PayZu. | Transaction not allowed. Enter the card data again. If the error persists, contact the online store. | No |
| BL | Transaction not authorized. Daily limit exceeded. | Transaction not authorized. Daily limit exceeded. Ask the cardholder to contact the issuing bank. | Transaction not authorized. Daily limit exceeded. Contact your issuing bank. | From the next day on, only 4 times within 16 days. |
| BM | Transaction not authorized. Invalid card | Transaction not authorized. Invalid card. It may be a card block at the issuing bank or incorrect data. Try using the Luhn algorithm (Mod 10) to avoid transactions declined for this reason. | Transaction not authorized. Invalid card. Redo the transaction confirming the data provided. | No |
| BN | Transaction not authorized. Card or account blocked. | Transaction not authorized. The cardholder's card or account is blocked. Ask the cardholder to contact the issuing bank. | Transaction not authorized. The cardholder's card or account is blocked. Contact your issuing bank. | No |
| BO | Transaction not allowed. Operation failure. | Transaction not allowed. There was a processing error. Ask the cardholder to enter the card data again; if the error persists, contact the issuing bank. | Transaction not allowed. There was a processing error. Enter the card data again; if the error persists, contact the issuing bank. | Only 4 times within 16 days. |
| BP | Transaction not authorized. Nonexistent checking account. | Transaction not authorized. Cannot process the transaction due to an error related to the cardholder's card or account. Ask the cardholder to contact the issuing bank. | Transaction not authorized. Cannot process the transaction due to an error related to the cardholder's card or account. Contact the issuing bank. | No |
| BP171 | Rejected due to fraud risk (Velocity). | Related to Velocity rules | Try again after 1 hour. | Yes |
| BP176 | Transaction not allowed. | The partner should check whether the integration process was completed successfully. | The partner should check whether the integration process was completed successfully. | N/A |
| BP900 | Operation failure. | Related to a failure in the operation (request submission process). | Try again in 5 minutes. We recommend checking the transaction status before making a new authorization attempt. | Yes |
| BP901 | Operation failure. | Related to a failure in the authorization. | Try again in 5 minutes. We recommend checking the transaction status before making a new authorization attempt. | Yes |
| BP902 | Wait for the response of the previous operation. | Related to a failure in the capture. | Try again. | Yes |
| BP903 | Cancellation failure. | Related to a failure in the cancellation. | Try again. | Yes |
| BP904 | Query failure. | Related to a failure in the query. | Try again. | Yes |
| BR | Transaction not authorized. Account closed | The cardholder's account is closed. Ask the cardholder to contact the issuing bank. | The cardholder's account is closed. Ask the cardholder to contact the issuing bank. | No |
| C1 | Transaction not allowed. Card cannot process debit transactions. | Change the payment method or the card used. | Change the payment method or the card used. | No |
| C2 | Transaction not allowed. | Incorrect data. Please review the data filled in on the payment screen. | Incorrect data. Please review the data filled in on the payment screen. | No |
| C3 | Transaction not allowed. | Invalid period for this type of transaction. | Invalid period for this type of transaction. | No |
| CF | Transaction not authorized. Data validation failure. | Transaction not authorized. Data validation failure. Ask the cardholder to contact the issuing bank. | Transaction not authorized. Data validation failure. Contact the issuing bank. | No |
| CG | Transaction not authorized. Data validation failure. | Transaction not authorized. Data validation failure. Ask the cardholder to contact the issuing bank. | Transaction not authorized. Data validation failure. Contact the issuing bank. | No |
| DF | Transaction not allowed. Card failure or invalid card. | Transaction not allowed. Card failure or invalid card. Ask the cardholder to enter the card data again; if the error persists, contact the bank | Transaction not allowed. Card failure or invalid card. Enter the card data again; if the error persists, contact the bank | Only 4 times within 16 days. |
| DM | Transaction not authorized. Limit exceeded/no balance. | Transaction not authorized. Limit exceeded/no balance. | Transaction not authorized. Contact your issuing bank. | From the next day on, only 4 times within 16 days. |
| DQ | Transaction not authorized. Data validation failure. | Transaction not authorized. Data validation failure. Ask the cardholder to contact the issuing bank. | Transaction not authorized. Data validation failure. Contact the issuing bank. | No |
| DS | Transaction not allowed for this card | Transaction not authorized. Transaction not allowed for this card. | Transaction not authorized. Contact your issuing bank. | Only 4 times within 16 days. |
| EB | Number of installments higher than allowed. | Transaction not authorized. Contact PayZu and check whether your account has installments enabled. | Transaction not authorized. Contact PayZu and check whether your account has installments enabled. | Yes |
| EE | Transaction not allowed. Installment amount below the allowed minimum. | Transaction not allowed. Installment amount below the allowed minimum. Installments below R$ 5.00 are not allowed. The installment calculation needs to be reviewed. | Transaction not allowed. The installment amount is below the allowed minimum. Contact the online store. | No |
| EK | Transaction not allowed for this card | Transaction not authorized. Transaction not allowed for this card. | Transaction not authorized. Contact your issuing bank. | Only 4 times within 16 days. |
| FC | Transaction not authorized. Call the issuer | Transaction not authorized. Advise the cardholder to contact the issuing bank. | Transaction not authorized. Contact your issuing bank. | No |
| FE | Transaction not authorized. Mismatch in the transaction/payment date. | Transaction not authorized. Invalid transaction date or first payment date. | Transaction not authorized. Redo the transaction confirming the data. | No |
| FF | Cancellation OK | Cancellation transaction authorized successfully. ATTENTION: this return applies to cancellations, not to authorizations. | Cancellation transaction authorized successfully | No |
| FG | Transaction not authorized. Call AmEx 08007285090. | Transaction not authorized. Advise the cardholder to contact the AmEx service center. | Transaction not authorized. Contact the AmEx service center at 08007285090 | No |
| GA | Wait for contact | Transaction not authorized. Referred by Lynx Online as a preventive measure. | Transaction not authorized. The merchant should wait for contact from PayZu | No |
| GF | Transaction denied. | Transaction not authorized. Check whether the provided IP is allowed to process the transaction | Transaction not allowed. Contact PayZu. | No |
| GD | Transaction not allowed. | Transaction not allowed. Contact PayZu. | Transaction not allowed. Contact PayZu. | N/A |
| GT | Transaction denied. | Brute force attack. | Transaction not allowed. Contact PayZu. | No |
| GK | Transaction denied. | Temporary block due to a brute force attack. | Transaction not allowed. Contact PayZu. | No |
| HJ | Transaction not allowed. Invalid operation code. | Transaction not allowed. Invalid Coban operation code. | Transaction not allowed. Invalid Coban operation code. Contact the merchant. | No |
| IA | Transaction not allowed. Invalid operation indicator. | Transaction not allowed. Invalid Coban operation indicator. | Transaction not allowed. Invalid Coban operation indicator. Contact the merchant. | No |
| KA | Transaction not allowed. Data validation failure. | Transaction not allowed. There was a data validation failure. Ask the cardholder to review the data and try again. If the error persists, check the communication between the online store and PayZu. | Transaction not allowed. There was a data validation failure. Review the data provided and try again. If the error persists, contact the online store. | No |
| KB | Transaction not allowed. Incorrect option selected. | Transaction not allowed. Incorrect option selected. Ask the cardholder to review the data and try again. If the error persists, check the communication between the online store and PayZu. | Transaction not allowed. Incorrect option selected. Try again. If the error persists, contact the online store. | No |
| KE | Transaction not authorized. Data validation failure. | Transaction not authorized. Data validation failure. The selected option is not enabled. Check the options available for the cardholder. | Transaction not authorized. Data validation failure. The selected option is not enabled. Contact the online store. | No |
| NR | Transaction not allowed. | Transaction not allowed. | Transaction not allowed. Retry the transaction after 30 days | Retry the transaction after 30 days. |
| RP | Transaction not allowed. | Transaction not allowed. | Transaction not allowed. Retry the transaction after 72h | Retry the transaction after 72 hours. |
| SC | Transaction not allowed. | Transaction not allowed. Recurring payment, service canceled. Do not retry. | Transaction not allowed. Recurring payment, service canceled. Do not retry. | No. |
| U3 | Transaction not allowed. Data validation failure. | Transaction not allowed. There was a data validation failure. Ask the cardholder to review the data and try again. If the error persists, check the communication between the online store and PayZu. | Transaction not allowed. There was a data validation failure. Review the data provided and try again. If the error persists, contact the online store. | No |
| 6P | Transaction not authorized. Invalid data | Failure validating the transaction data. Advise the cardholder to review the data and try again. | Data validation failure. Review the data provided and try again. | Only 4 times within 16 days |