Defend an Adyen chargeback through the Defense submission flow including evidence upload and defense deadline tracking
domain: docs.adyen.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Receive the CHARGEBACK or SECOND_CHARGEBACK notification via Adyen webhook; parse the pspReference, reason code, and defense deadline from the notification payload
Retrieve the dispute details via the Disputes API to confirm the defense period and required defense reason code mappings
Assemble evidence documents (proof of delivery, customer authorization, AVS/CVV match records) and upload each as a base64-encoded document via the supply-defense-document endpoint
Submit the defense by calling the defend-dispute endpoint with the appropriate defense reason that maps to the chargeback reason code
Monitor subsequent webhook notifications for DISPUTE_WON, CHARGEBACK_REVERSED, or SECOND_CHARGEBACK to determine final outcome
Known gotchas
Defense deadlines are strict calendar deadlines set by the card network; Adyen does not accept submissions after the deadline even by minutes
The defense reason code must correspond to the original chargeback reason code; submitting a mismatched reason results in automatic loss at the network
Second chargebacks (arbitration) generally cannot be defended via the same flow; consult Adyen support for arbitration escalation procedures
Give your agent this knowledge — and 15,500+ 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?