diagram.mmd — flowchart
Chargeback Handling flowchart diagram

A chargeback is a forced payment reversal initiated by a cardholder through their issuing bank, disputing a transaction as unauthorized, fraudulent, or not as described. Unlike a refund (which is merchant-initiated), a chargeback bypasses the merchant and temporarily returns the funds to the cardholder while the dispute is investigated.

The chargeback lifecycle begins when a cardholder contacts their bank to dispute a charge. The issuing bank assigns a reason code (each card network has its own code set — Visa uses reason codes like 10.4 for card-absent fraud, 13.1 for merchandise not received, etc.) and provisionally credits the cardholder's account. The issuer then sends a chargeback notice to the acquirer via the card network.

The acquirer debits the funds from the merchant's settlement account and forwards the chargeback notice to the merchant along with the reason code and evidence submission deadline (typically 7–20 days depending on the network).

The merchant must then decide whether to accept the chargeback (lose the funds) or fight it by submitting a representment — compelling evidence that the transaction was legitimate. Valid evidence varies by reason code: for fraud disputes, device fingerprints, IP addresses, and signed order confirmations are relevant; for "item not received" disputes, delivery confirmations and tracking numbers are key.

The acquirer forwards the merchant's evidence package to the card network, which reviews it and either rules in favor of the merchant (chargeback reversed) or upholds the chargeback. If upheld, the merchant can escalate to pre-arbitration. If still unresolved, either party can request formal arbitration from the card network — a costly and final process.

A high chargeback rate (above 1% of transaction volume for most networks) triggers the merchant into a monitoring program with financial penalties and potential account termination. Prevention is critical: strong fraud controls (see Fraud Detection Pipeline), clear billing descriptors, and responsive customer service reduce chargebacks at the source.

Free online editor
Edit this diagram in Graphlet
Fork, modify, and export to SVG or PNG. No sign-up required.
Open in Graphlet →

Frequently asked questions

Chargeback handling is the process by which a merchant responds to a forced payment reversal initiated by a cardholder through their issuing bank. It covers receiving the chargeback notice, deciding whether to accept or contest it, and submitting evidence through the card network's dispute system.
The cardholder disputes a charge with their bank, which assigns a reason code and provisionally credits them. The acquirer notifies the merchant, who can submit a representment with evidence. The card network reviews both sides and rules accordingly; unresolved disputes can escalate to pre-arbitration or formal arbitration.
Fight chargebacks when there is clear evidence the transaction was legitimate — delivery confirmations, signed order agreements, device fingerprints, or IP logs. Accept them when the claim is valid, the dispute amount is small relative to representment costs, or evidence is insufficient to prevail.
Common mistakes include missing evidence submission deadlines, submitting irrelevant evidence for the specific reason code, not using 3D Secure to shift liability for CNP transactions, and failing to track the chargeback ratio before it triggers a monitoring programme.
A refund is merchant-initiated and follows a straightforward credit path with no fees or penalties. A chargeback is cardholder-initiated through the bank, includes a dispute fee (typically $15–$100), and can raise the merchant's chargeback ratio if not managed carefully.
mermaid
flowchart TD A([Cardholder disputes transaction]) --> B[Issuer assigns reason code] B --> C[Issuer provisionally credits cardholder] C --> D[Issuer sends chargeback to card network] D --> E[Network forwards to acquirer] E --> F[Acquirer debits merchant settlement account] F --> G[Acquirer notifies merchant with deadline] G --> H{Merchant decision} H -->|Accept chargeback| I[Accept funds loss] H -->|Fight chargeback| J[Compile evidence package] J --> K[Submit representment to acquirer] K --> L[Acquirer forwards to card network] L --> M{Network ruling} M -->|Merchant wins| N[Funds returned to merchant] M -->|Chargeback upheld| O[Merchant loses funds] O --> P{Escalate to pre-arbitration?} P -->|No| Q([End]) P -->|Yes| R[Submit pre-arbitration] R --> S{Pre-arbitration result} S -->|Resolved| Q S -->|Unresolved| T[Formal network arbitration] T --> U[Final binding decision] U --> Q N --> Q I --> Q
Copied to clipboard