Handle the Mastercom chargeback collaboration cycle on Mastercard disputes via Adyen: respond to issuer requests and escalate to pre-arbitration
domain: adyen.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
When Adyen surfaces a Mastercard chargeback in the Disputes API or console, check the dispute.chargebackReasonCode to map it to the correct Mastercom reason code category (e.g. 4853=cardholder dispute, 4863=counterfeit, 4807=warning bulletin)
In the collaboration stage, the issuer and acquirer can exchange messages; submit your rebuttal via the Adyen Disputes API defend endpoint with supporting documents before the first response deadline
If the issuer issues a second chargeback (pre-arbitration), you receive a new dispute notification; evaluate whether to accept or escalate to arbitration based on the strength of your evidence and the cost of arbitration fees
To escalate to arbitration, submit a second defense through the Adyen Disputes API with additional evidence; Adyen coordinates the submission to the card network on your behalf
Track all deadlines from the defenseByDate field on each dispute stage; the collaboration and pre-arbitration stages have separate independent deadlines
Known gotchas
Mastercard arbitration fees are substantial (hundreds of dollars regardless of outcome); only escalate if the disputed amount significantly exceeds the arbitration fee and you have compelling evidence
The Mastercom collaboration cycle has strict timing windows at each stage; a response submitted even one day late is treated as forfeiture at that stage
Adyen may internally handle some Mastercard dispute stages without surfacing them separately in the API; check Adyen's dispute management documentation for the exact lifecycle stages exposed via API vs. handled automatically
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?