To encourage businesses to comply with certain processing standards, Visa charges system integrity fees. These fees are related to excessive retries of failed transactions, and excessive numbers of transactions that failed due to incorrect payment details. The Adyen risk engine helps to avoid such fees.
If you have built your own retry logic, in order to avoid Visa system integrity fees, you need to identify if you can or cannot retry a failed Visa transaction. To do this, you can use the raw response from your transaction responses. The raw response maps to categories that Visa uses to determine the fees.
Requirements
| Requirement | Description |
|---|---|
| Integration type | An online payments integration. |
| Setup steps | Before you begin, in your Customer Area enable receiving raw responses. |
Categories of system integrity fees
The Visa system integrity fees consist of two fee types:
- An excessive retry fee for failed transactions that are retried too many times.
- A data quality fee that is applied if the number of transactions that failed because you provided incorrect data exceeds a monthly threshold.
To calculate those fees, Visa divides failed transactions into four categories. Each category has specific rules for the type of fee that is applied and how many retries are allowed. The category that a failed transaction belongs to, is indicated using the raw response.
-
Category 1: Issuer will not approve
Transactions are declined with a raw response in category 1 if a retry will never succeed. This is the case, for example, when the card is blocked, lost, or stolen, or never existed.Do not retry the transaction. Visa charges an excessive retry fee if you retry the transaction.
-
Category 2: Issuer cannot approve at this time
Transactions are declined with a raw response in category 2 if it is possible that a retry will succeed later. This is the case, for example, if there was a system failure or if the cardholder had insufficient funds.You can retry the transaction up to 15 times in a 30-day period. Visa charges excessive retry fees if you exceed this limit.
-
Category 3: Issuer cannot approve with these details
Transactions are declined with a raw response in category 3 if there was something wrong with the provided card details. This is the case, for example, if the account number, CVV, or expiry date is incorrect.You can retry the transaction up to 15 times in a 30-day period. Visa charges excessive retry fees and data quality fees if you exceed this limit.
-
Category 4: Generic response codes
This category is for transactions that are declined with a raw response that does not belong to any of the other categories. The most frequent refusal reason, 05: Do not honor, falls into this category.You can retry the transaction up to 15 times in a 30-day period. Visa charges excessive retry fees if you exceed this limit.
Mapping of raw responses to categories
When receiving raw responses is enabled in your Customer Area, the transaction responses contain:
refusalCodeRaw(only available for Visa and Mastercard transactions through our own acquiring platform): the numeric part of the raw response. This represents the underlying scenario that caused the transaction to fail.refusalReasonRaw: the full raw response including the raw refusal code.
The following table shows the mapping of raw refusal codes and reasons to the four categories of Visa system integrity fees.
refusalCodeRaw |
refusalReasonRaw |
Retry? |
|---|---|---|
| Category 1: Issuer will not approve | ||
| 04 | 04: Pickup card |  |
| 07 | 07: Pickup card, special conditions | |
| 12 | 12: Invalid transaction | |
| 14 | 14: Invalid Account Number (No such Number) | |
| 15 | 15: No such issuer | |
| 41 | 41: Pickup card (lost card) | |
| 43 | 43: Pickup card (stolen card) | |
| 46 | 46: Closed Account | |
| 57 | 57: Transaction not permitted to cardholder | |
| R0 | R0: Stop payment order | |
| R1 | R1: Revocation of authorization order | |
| R3 | R3: Revocation of all authorization | |
| Category 2: Issuer cannot approve at this time | ||
| 03 | 03: Invalid merchant | Max 15x in 30 days |
| 19 | 19: Re-enter transaction | Max 15x in 30 days |
| 51 | 51: Insufficient funds | Max 15x in 30 days |
| 59 | 59: Suspected fraud | Max 15x in 30 days |
| 61 | 61: Exceeds withdrawal amount limits | Max 15x in 30 days |
| 62 | 62: Restricted card | Max 15x in 30 days |
| 65 | 65: Exceeds withdrawal frequency | Max 15x in 30 days |
| 75 | 75: Allowable number of PIN-entry tries exceeded | Max 15x in 30 days |
| 78 | 78: Blocked, First Used | Max 15x in 30 days |
| 86 | 86: ATM malfunction | Max 15x in 30 days |
| 91 | 91: Issuer or switch is inoperative | Max 15x in 30 days |
| 93 | 93: Transaction cannot be completed | Max 15x in 30 days |
| 96 | 96: System malfunction | Max 15x in 30 days |
| N3 | N3: Cash service not available | Max 15x in 30 days |
| N4 | N4: Cash request exceeds issuer limit | Max 15x in 30 days |
| Category 3: Issuer cannot approve with these details | ||
| 14 | 14: Invalid account number (No such Number) | Max 15x in 30 days |
| 54 | 54: Expired card | Max 15x in 30 days |
| 55 | 55: Incorrect PIN | Max 15x in 30 days |
| 82 | 82: Negative Online CAM, dCVV, iCVV, or CVV results | Max 15x in 30 days |
| N7 | N7: Decline for CVV2 failure | Max 15x in 30 days |
| 1A | 1A: Additional customer authentication required | Max 15x in 30 days |
| 70 | 70: PIN data required | Max 15x in 30 days |
| Category 4: Generic response codes | ||
| Any failed transaction with a raw refusal code not listed in the other categories. | Max 15x in 30 days | |