Chargeback

A chargeback is a reversal pursued through a card-payment dispute process after an issuer challenges a transaction under applicable network or legal rules. It can return transaction value from the merchant side to the issuer side, but it is not automatically final and is not the same as a merchant refund.

Key Takeaways

• A customer dispute can lead to a chargeback, but the two terms are not always identical.
• Chargebacks can involve unauthorized use, processing errors, duplicate charges, nonreceipt, or other recognized dispute reasons.
• The merchant or acquirer may be allowed to respond with transaction and fulfillment evidence.
• A provisional credit to the cardholder can later be confirmed or reversed.
• Deadlines, evidence requirements, reason codes, and liability differ by network, card type, transaction, and jurisdiction.
• Authorization approval does not eliminate chargeback risk.

How a Chargeback Works

    flowchart LR
	    C["Cardholder"] -->|"Reports transaction problem"| I["Issuer"]
	    I -->|"Chargeback and case data"| N["Card network"]
	    N --> A["Acquirer"]
	    A --> M["Merchant"]
	    M -->|"Accepts or submits evidence"| A
	    A --> N
	    N -->|"Outcome and financial adjustment"| I

A simplified card-dispute lifecycle is:

1. The cardholder identifies a transaction problem and contacts the issuer or merchant.
2. The issuer reviews the claim under applicable law, account terms, and network rules.
3. The issuer can provide provisional credit where required or appropriate.
4. If the claim qualifies, the issuer sends a chargeback through the payment network.
5. The network and acquiring bank pass the financial adjustment and case information to the merchant side.
6. The merchant accepts the chargeback or submits permitted evidence through its provider.
7. Additional review, escalation, or network procedures determine the outcome.
8. The parties reconcile the final cardholder, issuer, acquirer, merchant, fee, and reserve entries.

The exact process can include retrieval requests, representment, pre-arbitration, arbitration, or other network-specific stages. Not every dispute follows every stage.

Worked Example: Provisional Credit and Merchant Response

Assume a cardholder disputes a settled $240 purchase, saying the goods were not received. The following entries are illustrative rather than universal network accounting:

Two simplified outcomes are possible:

• Chargeback stands: the cardholder’s credit becomes final under the applicable process, while the merchant bears the transaction reversal and any nonrefundable fees or fulfillment cost.
• Merchant response succeeds: the $240 transaction can be restored to the merchant side and the cardholder’s provisional credit can be removed, subject to the issuer’s notices and governing rules.

The cardholder should not spend a provisional credit as though the case is final, and the merchant should not record the initial debit as final before the response window and case status are known. Exact deadlines, fees, evidence, and outcomes depend on law, network rules, issuer procedures, and the merchant agreement.

Common Chargeback Reasons

• cardholder says the transaction was unauthorized
• transaction was processed more than once
• amount or currency was incorrect
• credit or refund was not processed
• goods or services were not received
• goods or services materially differed from the agreement
• recurring payment continued after cancellation
• transaction lacked required authorization or processing data

These are broad educational categories, not universal reason codes. Networks use detailed and changing classifications.

Chargeback vs. Refund, Void, and Dispute

A merchant refund can be simpler when the merchant agrees the customer is owed money. A chargeback exists to address a dispute or processing claim through the card system; it should not be used to obtain both a refund and a second recovery for the same purchase.

Provisional Credit Is Not Final Resolution

An issuer may temporarily credit a disputed amount while investigating. That entry can make funds or credit available, but it does not necessarily mean the claim has been decided.

If the issuer concludes that the transaction is valid, the provisional credit can be removed under the applicable process. Cardholders should preserve notices and continue paying undisputed amounts as required by their agreement and local law.

Merchant Evidence

Useful evidence depends on the reason for the dispute and can include:

• authorization and authentication records
• receipt and transaction identifier
• customer order and acceptance details
• delivery or service-performance evidence
• cancellation and refund policy shown to the customer
• customer communications
• recurring-payment consent and cancellation record
• refund or reversal confirmation
• device, address, or account history where lawfully collected and relevant

Submitting more documents is not automatically better. Evidence should directly answer the stated dispute reason and comply with deadlines and privacy obligations.

Financial and Operational Impact

For a merchant, chargebacks can affect:

• revenue and refund accounting
• processor and chargeback fees
• reserve requirements and settlement timing
• fraud loss and fulfillment cost
• network monitoring status
• customer support workload
• cash-flow forecasting

For an acquirer or processor, concentrated disputes can create merchant credit exposure and require enhanced monitoring, reserves, or termination controls.

Common Mistakes

• defining every chargeback as proven fraud
• treating authorization as guaranteed payment
• missing a response deadline
• responding without matching the reason code
• confusing a pending dispute credit with final recovery
• issuing a refund without checking whether a chargeback is already active
• failing to reconcile cardholder, merchant, processor, and bank records
• assuming one jurisdiction’s consumer rules apply globally

How to Review a Chargeback

1. Identify the original transaction, card type, issuer, acquirer, and merchant.
2. Record the dispute reason, amount, currency, and every deadline.
3. Match authorization, capture, settlement, refund, and prior communication records.
4. Determine whether provisional credit or merchant debiting has occurred.
5. Submit focused evidence through the authorized channel.
6. Track representment, escalation, and final decision status.
7. Reconcile fees, reserves, recovered value, and account entries.
8. Fix recurring fraud, fulfillment, descriptor, or cancellation problems.

Official Resources

• The CFPB guide to disputing a credit-card charge explains U.S. billing-error notice considerations for consumers.
• The CFPB refund and charge-dispute guidance distinguishes asking the seller for a refund from pursuing a card dispute.
• The OCC Merchant Processing handbook discusses chargeback exposure and merchant-processing controls for U.S. banks.

This article provides general financial education, not personalized legal, payment-dispute, or fraud-recovery advice. Rights, deadlines, evidence, and liability depend on the card, agreement, rules, transaction facts, and jurisdiction.

FAQs

Related Terms

• Void Transaction: Merchant cancellation before completed settlement.
• Card Authorization: Issuer approval or decline before capture.
• Merchant Account: Acquiring arrangement through which disputes affect merchant funding and reserves.
• Credit Card Fraud: Unauthorized use that can lead to an issuer investigation and card-network dispute.
• Credit Card: Revolving credit product subject to cardholder, issuer, and dispute rules.