ZocumentsOn this page
How to read the live dispute
-
Open the event Confirm whether it is an RFI, NoF, or chargeback and note the response deadline.
-
Read the scheme Visa, Mastercard, Amex, and other payment methods use different code systems.
-
Open defense requirements Adyen links the reason to the documents and response timeframe it expects.
-
Submit the evidence Use the Adyen dispute workflow or API path attached to the event.
The Adyen fields that answer “what code is this?”
| Field or label | What it tells you | Why it matters |
|---|---|---|
| Dispute event | Whether the record is a chargeback, RFI, or NoF. | The stage changes what response is possible and when. |
| Scheme | The card network or payment scheme that supplied the code. | A Visa 13.3 and a Mastercard 4853 are not interchangeable instructions. |
| CB Reason Code | The chargeback reason code provided by the bank or payment method. | This is the scheme-level code when one exists. |
| Dispute Reason | Adyen's mapped or plain-language reason presentation. | This may be the only useful reason for payment methods without formal coding. |
| Defense requirements | The records Adyen says can support a challenge and the timeframe to provide them. | The code alone does not tell you which files to upload. |
Why the same-looking code can mean different work
Visa condition or legacy code
Translate the number through the Visa condition and the live claim, not a generic code list.
Mastercard message reason
Check the message system, dispute stage, and whether the notice uses a legacy form.
Credit not processed
Use refund, cancellation, credit, and communication records when the issue is a missing credit.
Before you upload a defense document
Adyen case check
- Event type and event date
- Scheme and CB/RFI/NoF reason code
- Adyen dispute reason and defense requirements
- Response deadline and allowed file formats
- Transaction identifiers that link each exhibit to the payment
- Whether the case is still open or has moved to another stage
Adyen's disputed-transactions report also exposes scheme and reason-code fields for operational reporting. Its dispute webhook documentation is useful for integrations, but a webhook does not replace reading the case's defense requirements.
