Disputes and chargebacks
A chargeback is the formal reversal of a settled transaction executed by the cardholder's issuing bank under card scheme rules. When an issuer files a chargeback, funds are debited immediately from the merchant's settlement account without prior merchant consent. The merchant is subsequently granted a limited window to contest the claim by submitting documentary evidence.
Chargebacks represent the foundational consumer protection mechanism of the card ecosystem. The statutory guarantee that cardholders can recover funds from their bank if goods are unfulfilled, defective, or fraudulent is what gives consumers confidence to transact with unfamiliar businesses online. Consequently, the dispute process is intentionally weighted toward the cardholder.
The dispute lifecycle
When a chargeback initiates, capital is debited provisionally from the merchant's processing account. In representment, the merchant is arguing to recover capital that has already been extracted.
If the merchant submits compelling evidence and the issuing bank accepts the representment, the debited funds are credited back to the merchant. However, if the issuer rejects the representment, the parties enter pre-arbitration. If neither institution concedes, the dispute escalates to formal network arbitration, where card scheme adjudicators review the case and issue a final ruling. Crucially, the network assesses substantial arbitration filing fees (typically $250 to $500) against whichever institution loses the ruling, making formal arbitration economically impractical for standard transaction amounts.
Reason codes and evidentiary standards
Every dispute is classified under a specific reason code designated by the card network, identifying the formal legal and factual basis of the claim:
| Dispute category | Cardholder claim | Authoritative representment evidence |
|---|---|---|
| Fraud | Transaction was unauthorized; cardholder did not participate | 3-D Secure authentication cryptogram (ECI), proof of physical card presentment (EMV data), device fingerprint telemetry, proof of digital access |
| Authorization | Transaction cleared without valid authorization approval | Valid authorization approval code matching transaction amount, currency, and date |
| Processing Error | Incorrect transaction amount, wrong currency, duplicate billing | Reconciled transaction receipt showing single submission matching the authorized amount |
| Consumer Dispute | Merchandise not received, service defective, subscription cancelled | Signed carrier proof of delivery, tracking telemetry, accepted terms of service, customer service communication logs |
Differentiating dispute categories reveals operational weaknesses:
- Authorization and processing-error chargebacks point directly to technical software bugs—such as race conditions triggering duplicate captures, late clearing submissions past scheme timeframes, or unmanaged force captures.
- Consumer disputes point to fulfillment bottlenecks, inventory stockouts, unclear return policies, or complicated subscription cancellation flows.
- Fraud disputes indicate inadequate checkout screening or missing 3-D Secure protections.
Executing an effective representment
Representment is the formal procedural mechanism through which a merchant re-presents a disputed transaction to the issuing bank accompanied by a structured rebuttal evidence package.
Compile targeted documentary evidence aligned strictly with the assigned reason code.
- Extract the specific reason code and firm response deadline from the processor dispute notice.
- Verify whether a refund was already issued for the transaction. If a refund occurred prior to the dispute, submit the refund transaction receipt immediately to terminate the chargeback.
- Assemble only the specific evidentiary documents demanded by network rules for that reason code.
- Submit the complete representment package well before the deadline expires, as late submissions are rejected automatically.
Direct costs: dispute administration fees
Every chargeback incurs a mandatory non-refundable dispute fee assessed by the payment processor (typically ranging from $15 to $35 per dispute).
Processors assess this fee regardless of whether the merchant ultimately wins the representment. For high-volume merchants with low average order values, dispute administration fees can easily exceed the gross transaction value.
Monitoring programs and the chargeback ratio
Acquiring banks and card networks continuously evaluate a merchant's dispute health using the chargeback ratio:
Chargeback Ratio = (Total Disputed Transactions in Current Month) / (Total Settled Transactions in Current Month)
Both Visa and Mastercard operate formal compliance monitoring programs (such as the Visa Dispute Monitoring Program and Mastercard Excessive Chargeback Program) that enforce strict operational thresholds:
- Standard monitoring thresholds typically activate when a merchant reaches 100 disputes and exceeds a 0.90% dispute ratio within a calendar month.
- Excessive thresholds trigger at 1.50% dispute ratios.
Breaching network thresholds results in mandatory monthly fines, escalated dispute administration fees, compulsory remediation audits, and increased merchant reserve withholdings. Continued non-compliance leads to termination of merchant processing accounts and permanent placement on the Match / Terminated Merchant File (TMF) list, preventing the business from securing card processing across the industry.
Monitor dispute velocity against scheme calculation methodologies on a monthly basis.
- Obtain exact monitoring thresholds and calculation formulas from the acquiring bank for each card scheme.
- Note whether the network calculates the ratio using current-month sales or previous-month sales as the denominator.
- Establish automated alerts when dispute volume approaches 70% of network thresholds.
- Issue immediate refunds on contentious orders to prevent cardholders from escalating claims to formal chargebacks.
Disputing cards versus ACH returns
Card chargebacks must not be confused with Automated Clearing House (ACH) returns:
| Operational characteristic | Card Chargeback | ACH Return |
|---|---|---|
| Initiating party | Cardholder through issuing bank | Receiving Depository Financial Institution (RDFI) |
| Rebuttal mechanism | Structured representment and scheme arbitration | No formal representment; returns are definitive |
| Dispute window | Typically 120 calendar days from transaction date | 2 banking days for technical errors; 60 calendar days for unauthorized consumer claims |
| Diagnostic code format | Alphanumeric reason codes (e.g. Visa 10.4, MC 4837) | Standardized Nacha R-codes (e.g. R01, R07, R10) |
If an ACH debit is returned, there is no procedural representment mechanism within the ACH network; the merchant must pursue capital recovery directly through private commercial or legal channels.
Terms introduced
- Arbitration: the network deciding a dispute the issuer and acquirer could not settle, and charging a fee to whoever loses.
- Chargeback: the issuer reversing a settled transaction on the cardholder's behalf.
- Chargeback ratio: disputed transactions as a share of volume.
- Dispute fee: your provider's per-dispute charge, which you pay whether you win or lose.
- Pre-arbitration: a second exchange after a representment is rejected, before arbitration.
- Reason code: the network's identifier for what the cardholder is claiming, which determines what evidence counts.
- Representment: re-presenting a disputed transaction to the issuer with evidence.
How providers do it
While card network dispute frameworks—such as Visa Claims Resolution and Mastercard MasterCom—dictate the legal timeframes, reason codes, and arbitration criteria for chargebacks, payment providers differ significantly in how they handle fund debits, representment workflows, and platform liabilities.
The most critical operational distinctions center on whose ledger balance absorbs the chargeback debit and how programmatically evidence can be submitted to challenge the dispute.
| Provider | Where the debit lands | Submitting evidence | Status |
|---|---|---|---|
| Stripe | Deducted directly from the merchant's operational balance as a balance transaction | Programmatic evidence fields uploaded via the dispute API object | unconfirmed |
| Stripe Connect | Debited from the connected account on Direct Charges; debited from the platform balance on Destination and Separate Charges | Uploaded via the dispute API object, with the platform responsible for managing the defense deadline | confirmed |
| Adyen | Deducted from the merchant settlement account, typically days after the initial dispute notification webhook | Structured defense documentation submitted against scheme-specific reason codes via the API | confirmed |
| Checkout.com | Deducted directly from the merchant processing balance | Programmatic file upload and metadata submission via the disputes endpoints | unconfirmed |
| Payrix | Dictated by whether the platform or the sub-merchant operates as the legal merchant of record | Depends on contract configuration; determines whether the platform or seller manages representment | unconfirmed |
Two overarching commercial questions apply across this entire matrix that cannot be answered by API documentation alone:
- Does the provider refund the non-refundable dispute administrative fee if the merchant wins representment?
- When operating a marketplace or software platform, does a delinquent sub-merchant's dispute ratio count against the platform's overall card brand monitoring thresholds?
Both points should be clarified in writing within the merchant processing agreement before onboarding high volumes.
- Stripe
- Stripe Connect
- Adyen
- Payrix
- Checkout.com
What they are: the PSP, so the debit arrives as an entry in the balance rather than as a bank adjustment.
| Standard term | Their term | Status |
|---|---|---|
| Chargeback | Dispute | confirmed |
| Representment | Submitting evidence on the dispute | confirmed |
| Accepting the loss | Closing the dispute | confirmed |
| Question | Answer | Status |
|---|---|---|
| When is the money taken? | At the dispute, as a balance transaction. Winning credits it back later | unconfirmed |
| Is the dispute fee returned on a win? | unconfirmed; assume not until the contract says otherwise | |
| What is the real submission deadline? | unconfirmed; Stripe's own deadline sits before the network's, which is the compression the core page warns about | |
| Are early fraud warnings sent before a dispute? | Offered for some card types | unconfirmed |
Last verified: never.
What they are: the layer that decides whose money a chargeback comes out of. The dispute process is Stripe's either way. Who pays for it is set by the charge type.
| Charge type | Disputed amount debited from | Dispute fee billed to | Status |
|---|---|---|---|
| Direct charge | The connected account | The platform or the connected account, per that account's configuration | confirmed |
| Destination charge | The platform | The platform | confirmed |
| Separate charges and transfers | The platform | The platform | confirmed |
Setting on_behalf_of does not move the debit. On destination charges and separate transfers
the platform balance is debited with or without it, and recovery means reversing the transfer
to the seller.
| Question | Answer | Status |
|---|---|---|
| Who gathers the evidence? | unconfirmed; the seller has the delivery proof and the platform has the deadline, which is how these get missed | |
| What if the connected account has no balance to debit? | It goes negative. Stripe debits the seller's bank account only where debit_negative_balances is set | confirmed |
| Do sub-merchant disputes count against the platform's own ratio? | unconfirmed; ask, because it decides whether one bad seller threatens the whole platform |
That last question is the one to answer first. On a facilitator model the platform's chargeback ratio can be an aggregate of every seller on it, and a single seller shipping nothing can put the platform into a monitoring programme.
Last verified: 2026-09-09 against Stripe's public Connect documentation.
What they are: the acquirer, so the dispute notice comes from them directly and the defence goes back through them.
Adyen splits the incoming message in two, and the difference decides whether the money has gone yet. A request for information asks about a payment and takes nothing. A notification of chargeback starts the defence clock, and the debit follows a few days later.
| Standard term | Their term | Status |
|---|---|---|
| Retrieval request | REQUEST_FOR_INFORMATION, with no money withdrawn | confirmed |
| Chargeback notice | NOTIFICATION_OF_CHARGEBACK, which opens the defence period | confirmed |
| Representment | Defending the dispute, with defence documents | confirmed |
| Accepting the loss | acceptDispute | confirmed |
| Evidence | Defence document, supplied against a defence reason | confirmed |
| Question | Answer | Status |
|---|---|---|
| How is the evidence this reason code needs identified? | Call retrieveApplicableDefenseReasons for the dispute. It returns the reasons and what each requires | confirmed |
| What do the requirement levels mean? | Required needs one document, OneOrMore accepts several, Optional needs none, AlternativeRequired takes a generic document instead | confirmed |
| What formats and sizes are accepted? | JPG, TIFF and PDF, with per-scheme limits. Mastercard caps a document at 19 pages | confirmed |
| What is the defence deadline? | Starts at the chargeback notification | unconfirmed; read the window off the notification rather than assuming a scheme figure |
| What does a dispute cost? | unconfirmed; contract-dependent |
Calling retrieveApplicableDefenseReasons first is the mechanised version of the rule on this
page. It answers "what does this reason code ask for" before anyone starts gathering, which is
where most representments are lost.
Last verified: 2026-09-09 against Adyen's public disputes documentation.
What they are: the facilitator, which means a dispute against a sub-merchant is not first of all the platform's dispute. Who ends up paying for it depends on the engagement model in the contract.
| Question | Answer | Status |
|---|---|---|
| Who is the merchant of record, and so who carries the chargeback? | unconfirmed | |
| Does the sub-merchant defend it, or the platform? | unconfirmed | |
| Where does the debit land if the sub-merchant has already been disbursed? | unconfirmed | |
| Do sub-merchant disputes roll into one ratio, or are they measured per merchant? | unconfirmed; if they aggregate, one seller can put the whole platform into a monitoring programme | |
| What is the dispute fee, and who is billed for it? | unconfirmed |
Nothing here is answerable from the API documentation. Take all five to whoever holds the Worldpay relationship and write the answers down, because the first dispute is a bad time to discover that a seller thinks the platform is handling it.
Last verified: never.
What they are: the acquirer, so disputes arrive from them and evidence goes back through their API rather than a portal somebody logs into by hand.
| Question | Answer | Status |
|---|---|---|
| Can evidence be submitted by API? | Yes, through their disputes endpoints | unconfirmed; confirm which evidence types an integration supports |
| What submission deadline do they give? | unconfirmed; expect it to be shorter than the scheme window | |
| Is the dispute fee returned on a win? | unconfirmed | |
| Do they notify before the debit, or with it? | unconfirmed |
Automating the submission is worth doing here, since the evidence for a delivery dispute lives in a fulfilment system rather than in anyone's inbox. The failure the core page describes, where nobody can find the delivery confirmation in time, is a systems problem with a systems answer.
Last verified: never.