Submit an Adyen dispute defense for a Request for Information (RFI)
domain: docs.adyen.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Receive the dispute notification webhook containing the disputePspReference, defendByDate, and defenseReasonCode.
Call POST /retrieveApplicableDefenseReasons with the disputePspReference in the request body to obtain the list of defense reasons your evidence can support for this specific dispute.
Select the appropriate defenseReasonCode from the response based on your available evidence (e.g., proof of delivery, cardholder correspondence, authorization records).
Assemble evidence documents; upload each file using POST /uploadDocument with the disputePspReference and document type, receiving a documentReference for each upload.
Submit the defense by calling POST /defendDispute with the disputePspReference, chosen defenseReasonCode, and the array of documentReferences.
Monitor the dispute outcome via subsequent dispute webhooks or by polling the dispute status; retain all evidence and pspReference values for chargeback reconciliation.
Known gotchas
All Adyen Disputes API operations are POST — there is no GET endpoint to retrieve defense reasons; omitting this step and hardcoding a reason code may result in a rejected defense submission.
The defendByDate in the webhook is a hard deadline; missing it forfeits the dispute automatically regardless of evidence quality.
Defense reasons available vary by dispute reason code and card network; always call retrieveApplicableDefenseReasons first rather than assuming which reasons are valid.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?