Home Home / Insights / Blog

What Is a Chargeback and How Should Merchants Respond to a Payment Dispute?

2026-11-16    Author : ZCS

Key Takeaways

  • ● A chargeback is a card-payment reversal initiated through the cardholder’s issuing bank, while a refund is initiated directly by the merchant.
  • ● A payment dispute is the broader case; a chargeback is the financial reversal that may result from that case. Providers sometimes use the terms interchangeably in their dashboards.
  • ● Merchant evidence must answer the specific dispute reason. A delivery record does not resolve a duplicate-charge claim, and a receipt alone may not resolve a non-delivery claim.
  • ● A merchant normally responds through its acquirer or payment processor, not directly to the card network or issuing bank. The applicable notice sets the response route and deadline.
  • ● An approved and settled payment can still become a chargeback later. Approval confirms a stage in payment processing; it does not make the transaction immune from a future dispute.

A chargeback is a reversal of all or part of a card transaction through the banking and card-network dispute process. The cardholder questions a payment through the issuing bank, the merchant receives the case through its acquirer or processor, and the merchant may accept the claim or respond with relevant evidence.

The practical merchant question is not only “Did the customer get the money back?” It is who initiated the return, which payment stage had been reached, why the transaction was challenged, and what records now have to be produced. Those details separate a chargeback from an ordinary refund, a voided authorization and a technical reversal.

This article explains the common operational model for card-payment disputes. Card-network rules, consumer laws, reason codes, deadlines, fees and escalation stages vary by provider and jurisdiction, so the dispute notice from the merchant’s own acquirer or processor remains the controlling instruction for a specific case.

 

Close-up of a restaurant bill payment terminal


1. What Is a Chargeback?

A chargeback transfers the disputed value of a card transaction back through the payment chain after an issuing bank accepts or advances a cardholder’s dispute. The merchant may first see a notification, a debit, a request for information or a temporary case status, depending on the payment provider and the applicable network process.

A normal card sale moves in one direction. The merchant accepts the card, the transaction is authorized, the payment is cleared and settled, and the merchant receives a payout. A chargeback moves disputed value in the opposite direction. The issuer raises the case against the acquirer, and the acquirer or processor usually passes the financial effect and information request to the merchant.

The Visa chargeback process describes a customer questioning a charge through the issuing bank, the merchant receiving notice through the acquiring side, and the merchant supplying evidence such as receipts, shipping confirmation or customer communication. Visa also notes that an issuer may provide temporary credit while the case is reviewed, so a customer-visible credit does not always mean the case is final.


1.1. Is a Payment Dispute the Same as a Chargeback?

A payment dispute is the broader disagreement, while a chargeback is a financial action within the dispute process. A cardholder can question a merchant name, request more information or complain about delivery before the case reaches a formal chargeback stage. Some processors label the entire case a “dispute,” even after funds have been debited.

Provider terminology therefore needs context. A dashboard marked “disputed” may refer to an inquiry, notification, first chargeback, representment, pre-arbitration or final loss. The merchant should read the case status and required action instead of assuming every use of the word “dispute” describes the same financial event.


1.2. Who Takes Part in a Chargeback?

Five parties commonly connect the customer complaint to the merchant’s balance. Their roles are different even when a processor dashboard hides some of the handoffs.

Party Main role in a card dispute
Cardholder Questions the payment and provides the claim to the issuing bank
Issuing bank Reviews the cardholder’s claim and raises the dispute through the card network
Card network Supplies the dispute framework, conditions and message flow
Acquirer or processor Receives the case for the merchant, applies the provider workflow and submits the merchant’s response
Merchant Accepts the dispute or supplies records that address the stated reason

The merchant does not normally send a defense directly to the cardholder’s bank. The merchant submits the response through the channel named by its acquirer or processor, which may be an online portal, dashboard, API or managed support process.


2. Why Do Chargebacks Happen?

Chargebacks arise from fraud claims, customer-service disputes, processing errors and authorization problems. Calling every case “fraud” hides the actual cause and makes the merchant’s response less relevant.


2.1. Unauthorized or Unrecognized Transactions

An unauthorized claim says the cardholder did not approve the payment. Genuine account misuse belongs in this group, but an unfamiliar billing descriptor, a household purchase or a forgotten subscription can also cause a legitimate transaction to be questioned.

Merchant records should help identify the transaction without assuming the customer is dishonest. A recognizable merchant descriptor, clear order confirmation and accessible customer support can resolve confusion before it becomes a formal dispute.


2.2. Goods or Services Not Received

A non-receipt dispute says the customer paid but did not receive the promised product or service. Delivery dates, collection records, service attendance, download activity and customer communications are more useful here than a generic payment receipt.

The expected fulfillment date matters. A customer may dispute a future service after cancellation, a parcel after the promised delivery date or a digital product that never became accessible. The merchant’s evidence must connect the specific customer and transaction to actual delivery or use.


2.3. Not as Described, Defective or Canceled

A quality or cancellation dispute says the merchant delivered something materially different from the agreement or continued charging after cancellation. Product descriptions, signed agreements, cancellation terms, photographs, service records and dated communications can establish what the merchant promised and what occurred.

Clear policy text is not automatically enough. The merchant may also need to show that the customer saw or accepted the relevant policy at the time of purchase and that the merchant followed it.


2.4. Duplicate, Incorrect or Misprocessed Payments

A processing dispute concerns how the payment was recorded rather than whether the customer wanted the product. Common examples include the same sale being submitted twice, the wrong amount or currency, a canceled authorization being captured, or a promised credit not appearing.

Transaction identifiers are central to this group. The merchant should compare order numbers, timestamps, terminal or gateway references, amounts, capture records and any refund confirmation instead of relying on a screenshot that lacks a traceable payment reference.


3. How Does the Chargeback Process Work?

A chargeback starts after the original payment event, but the exact sequence depends on the network and provider. A simple 100-unit sale shows the operational stages without implying that every case uses identical names.

  1. 1. The merchant records a 100-unit sale. The card transaction is authorized and captured under the merchant’s normal payment workflow.
  2. 2. The transaction clears and settles. The sale may be included in a later merchant payout, less applicable fees or other adjustments.
  3. 3. The cardholder questions the charge. The cardholder contacts the issuing bank and states a reason, such as unauthorized use, non-delivery or duplicate processing.
  4. 4. The issuer reviews the claim. The issuer decides whether the claim fits an available dispute condition and may give the cardholder provisional credit.
  5. 5. The acquiring side notifies the merchant. The merchant sees a reason code, disputed amount, deadline and available actions through the acquirer or processor.
  6. 6. The merchant accepts or responds. Acceptance ends the merchant’s challenge. A response, often called representment, supplies evidence that addresses the dispute reason.
  7. 7. The evidence is reviewed. The issuer evaluates the response under the applicable network rules and may uphold or reverse the chargeback.
  8. 8. Some cases continue. Pre-arbitration, second chargeback, arbitration or another escalation stage may be available under the relevant scheme.

Authorization, settlement and final dispute exposure are separate states. An approval means the issuer authorized that transaction at that time; settlement moves financial records between payment participants; a later dispute asks whether network rules permit the transaction value to be reversed. The related guide to approved payment settlement explains why an approved sale can reach the merchant’s bank later and still remain subject to subsequent adjustments.

The merchant should not infer a final outcome from one balance movement. A debit can occur before the merchant’s defense is reviewed, and a successful response may create a later credit. Some providers fund or hold cases differently, so the processor statement and case status must be read together.

The Mastercard Merchant Edition chargeback guide demonstrates why one universal flow is unsafe: dispute conditions carry their own prerequisites, documentation requirements and processing paths. Merchant staff should follow the case-specific notice rather than a generic deadline copied from an unrelated network or provider.


4. Chargeback vs Refund vs Void vs Reversal

Chargebacks, refunds, voids and reversals can all reduce or release a customer’s card balance, but they begin for different reasons and create different records. The initiator and payment stage are more reliable distinctions than the date on which the customer sees money move.

Action Typical initiator Payment stage Main financial effect Merchant evidence process
Void Merchant Before final capture or settlement, where supported Cancels or releases an authorization Normally an operational cancellation, not a dispute defense
Refund Merchant After a completed payment Creates a credit against the original sale Merchant authorizes the credit under its return or cancellation process
Reversal Merchant, processor, acquirer or issuer Often after an authorization error, timeout or incomplete payment Cancels or corrects a payment message Depends on the cause and provider workflow
Chargeback Issuer through a dispute process After the cardholder or issuer challenges the transaction Debits disputed value through the acquiring side Merchant accepts the case or submits reason-specific evidence

A refund is a merchant-controlled resolution. The customer and merchant agree that money should be returned, and the merchant sends a credit through the payment provider. The original sale normally remains in the records, with the refund recorded as a related but separate event.

A chargeback is an issuer-led dispute action. The merchant may disagree with the claim, but the merchant cannot convert the case into an ordinary refund merely by labeling it differently in the POS. Once a formal dispute is active, the merchant should ask the processor how to avoid issuing a second credit for the same transaction.

A void usually stops a payment before it becomes a completed sale. The detailed POS void versus refund workflow explains why staff should check the transaction status before choosing an action. Deleting an order, voiding a card authorization and refunding a settled payment are not interchangeable operations.

A reversal often corrects a payment-processing event. A timeout can leave the POS uncertain even though the payment host received an authorization. The terminal or processor may reverse the authorization to release the cardholder’s funds, but the merchant must verify the host status before retrying the sale.

 

POS Hardware


5. What Evidence Must a Merchant Provide?

Merchant evidence must directly answer the dispute reason and connect the disputed transaction to the claimed facts. A large document bundle is weaker than a short, organized response that shows the transaction reference, customer agreement, fulfillment event and relevant communication.

Dispute reason Evidence that may be relevant
Unauthorized or unrecognized charge Order confirmation, transaction receipt, applicable authentication records, customer account activity and prior undisputed history
Goods not received Tracking data, delivery address, delivery date, collection confirmation or signed receipt
Service not provided Booking confirmation, attendance record, access log, service completion record or customer acknowledgement
Not as described or defective Product description shown at purchase, invoice, photographs, return terms and dated customer communication
Duplicate payment Separate order references or proof that one payment was voided, reversed or refunded
Incorrect amount or currency Invoice, customer agreement, checkout confirmation and transaction record
Credit not processed Refund confirmation, original payment reference, refund date and processor-provided trace information
Recurring charge after cancellation Subscription terms, cancellation request, cancellation effective date and service-use records


5.1. Evidence Should Match the Reason Code

The reason code determines what the response needs to prove. Proof of delivery may answer a non-receipt claim but may not prove that a duplicate transaction was valid. A signed invoice may show agreement but may not establish that an online service remained available after cancellation.

Visa’s public Visa Core Rules, dated October 24, 2026, contain different response requirements for different dispute conditions. The rules also distinguish regional or country-specific provisions, reinforcing why merchants should not reuse a single evidence template for every network, market and reason.


5.2. Evidence Should Be Contemporary and Traceable

Contemporary records carry more operational value than a reconstruction created after the dispute. A receipt generated at purchase, a timestamped delivery scan, an access log and a dated customer email can be matched to the original transaction more easily than an unsupported explanation written weeks later.

Transaction references should remain intact. The merchant should preserve the original order ID, processor reference, terminal reference where available, amount, currency, date and payment method. Screenshots can support a case, but screenshots without identifiers may be difficult to connect to the disputed payment.


5.3. Evidence Should Be Relevant and Safe to Submit

A merchant should submit only the information needed for the case and allowed by the processor. Unrelated customer records create privacy and review problems, while sensitive authentication data should never be added merely to make a response look more complete.

The processor’s upload rules control the format. File type, page limits, text limits, image quality and prohibited data can determine whether evidence is accepted for review. The merchant should verify those constraints before the deadline rather than discovering them during the final upload.


5.4. The Merchant Has a Response Responsibility, Not a Guaranteed Win

The merchant’s responsibility is to provide a timely and relevant response when contesting the case. The merchant does not control the issuer’s final decision, and even strong records cannot guarantee that every chargeback will be reversed.

Acceptance can be the correct response when the customer’s claim is valid, the merchant did not deliver, a duplicate charge occurred or the merchant lacks the evidence required by the stated reason. Contesting every dispute can consume staff time and create additional costs without improving the outcome.


6. What Happens to Merchant Funds and Records?

A chargeback should be recorded as a separate payment event rather than used to erase the original sale. The original order explains what was sold, while the dispute record explains why money was later debited, held or returned.

A merchant may need to reconcile several entries:

  1. 1.the original gross sale;
  2. 2.the processor fee attached to the sale;
  3. 3.the merchant payout containing that sale;
  4. 4.the chargeback debit or reserve movement;
  5. 5.any chargeback fee;
  6. 6.a later credit if the merchant wins;
  7. 7.the final loss if the dispute is upheld.

The customer balance and merchant bank balance may change on different dates. An issuer can provide provisional credit before the merchant response is complete, while the acquirer can apply the corresponding debit under its own funding schedule. Neither date alone proves the case outcome.

The merchant’s POS reconciliation records should bridge the original sale to the processor’s dispute entries and the bank payout. Gross sales, refunds, chargebacks, fees and reserves should remain distinguishable so an accountant can explain the net deposit without changing the historical sales total.

A POS report may not contain the complete dispute lifecycle. The processor or acquirer usually owns the case status, reason code, deadline and financial adjustment. The merchant therefore needs a stable link between the POS order ID and the processor’s payment reference.


7. Should a Merchant Accept or Contest a Chargeback?

A merchant should contest a chargeback only when the claim is incorrect and the available evidence addresses the stated reason. Transaction value matters, but evidence strength and procedural eligibility come first.

Question Accepting may be reasonable when Contesting may be reasonable when
Is the customer’s claim accurate? The merchant confirms non-delivery, duplication or an unprocessed credit Records show authorization and correct fulfillment
Is relevant evidence available? The merchant cannot connect records to the disputed transaction The merchant has dated, traceable and reason-specific records
Is the deadline still open? The response window has closed The processor still permits a response
Does the value justify the work? The amount is low relative to documented handling costs The amount and evidence justify the operational effort
Could another credit create a duplicate loss? The processor instructs the merchant to accept the case A prior refund or reversal can be proven through the dispute response

The merchant should avoid emotional language. A clear response identifies the claim, states the merchant’s position, lists the attached evidence and explains what each record proves. Accusing the customer of fraud without evidence does not answer a delivery, duplicate or cancellation claim.

The merchant should also avoid irrelevant volume. Ten pages of general terms may hide the one page that shows customer agreement. A short timeline with labeled attachments is easier to review than a mixed folder of receipts, policies and screenshots.


8. How Can Merchants Reduce Avoidable Chargebacks?

Avoidable chargebacks fall when the merchant makes the transaction recognizable, documents fulfillment and resolves clear errors quickly. Prevention is not limited to fraud screening.

Fraud screening addresses one part of chargeback prevention. AI payment fraud detection uses transaction monitoring and risk scoring to help identify suspicious payments for further checks or review. A low risk score does not prevent a later dispute, and fraud screening cannot replace clear billing descriptors, fulfillment records or timely handling of cancellations and refunds.

  • ● Use a recognizable billing descriptor. The descriptor should help the cardholder connect the statement entry to the store, website or service used.
  • ● Show refund and cancellation terms before payment. The merchant should preserve evidence that the applicable terms were presented or accepted.
  • ● Send useful order confirmation. The confirmation should identify the merchant, items, amount, currency, delivery or service date and support route.
  • ● Prevent duplicate submission. Staff and software should verify payment status after a timeout instead of immediately repeating the transaction.
  • ● Keep delivery and service records. Physical delivery, customer collection, appointment attendance and digital access require different proof.
  • ● Process agreed refunds promptly. The original payment reference and refund confirmation should remain available for later tracing.
  • ● Provide accessible support. A customer who can identify a transaction and resolve a delivery problem may not need to contact the issuing bank.
  • ● Review reason-code patterns. A rising number of unrecognized-charge cases calls for a different fix from a rise in non-delivery cases.

Visa’s dispute-prevention guidance recommends clear return and cancellation policies, prompt transaction submission, protection against duplicate processing, customer updates on delayed delivery and recognizable merchant names. These controls target the events that create disputes rather than treating every chargeback as an isolated back-office task.

Chargeback monitoring should connect operations and finance. Customer support can identify recurring complaints, fulfillment teams can correct delivery gaps, payment teams can review duplicate or timeout behavior, and finance can measure the final loss after reversals and recovered cases.


9. Why Do Chargeback Rules and Deadlines Vary?

Chargeback rules vary because networks and payment methods define different dispute conditions, stages and evidence requirements. Regional law, issuer practice, acquirer contracts and processor operating procedures add further differences.

A merchant can therefore encounter different names for similar stages:

  • ● inquiry or request for information;
  • ● notification of fraud;
  • ● notification of chargeback;
  • ● first chargeback;
  • ● representment or information supplied;
  • ● chargeback reversal;
  • ● pre-arbitration or second chargeback;
  • ● arbitration.

The presence of a stage does not mean every case can use it. Some reason codes limit the merchant’s response options, some providers handle low-value cases automatically, and some payment methods do not follow the card-network model described in this article.

The May 2025 Mastercard merchant chargeback guide illustrates this variation through condition-specific prerequisites and supporting documents. The guide is useful for understanding Mastercard cases, but it should not be applied as a universal rulebook for Visa, domestic debit networks or non-card payment methods.

The dispute notice should answer four immediate questions: What is the reason? What amount is disputed? What action is available? What is the deadline? A generic online guide cannot replace those case-specific instructions.


10. Merchant Chargeback Response Checklist

A repeatable response checklist reduces missed deadlines and irrelevant evidence. The checklist should begin when the notification arrives, not when the deadline is approaching.

  1. 1.Confirm the case. Record the case ID, processor reference, disputed amount, reason code and deadline.
  2. 2.Find the original transaction. Match the payment to the POS order, invoice, customer and fulfillment record.
  3. 3.Check for prior corrections. Look for a void, reversal, refund, partial refund or duplicate entry.
  4. 4.Read the reason requirements. Identify exactly what the issuer’s claim requires the merchant to prove.
  5. 5.Choose accept or contest. Base the decision on the facts, available evidence, deadline and processing cost.
  6. 6.Build a short timeline. Show purchase, authorization, fulfillment, customer contact and any refund or cancellation.
  7. 7.Label each attachment. State what each receipt, log, photograph or message proves.
  8. 8.Remove prohibited or irrelevant data. Follow the processor’s privacy, security and file-format rules.
  9. 9.Submit through the approved channel. Save confirmation that the response was received before the deadline.
  10. 10.Reconcile the outcome. Match subsequent debits, fees, credits and final status to the original transaction.

 

Learn More


11. Frequently Asked Questions


Q1. Is a chargeback the same as a refund?

No. A refund is initiated by the merchant through its payment provider. A chargeback is initiated through the issuing bank under a dispute process. Both can return money to the customer, but the initiator, records, fees and response rights are different.


Q2. Is every payment dispute a chargeback?

No. A payment dispute can begin as a question, inquiry or request for information. A chargeback is the reversal stage that may follow. Provider dashboards sometimes use “dispute” as the label for the entire lifecycle.


Q3. Can a merchant win a chargeback?

Yes, when the rules permit a response and the evidence successfully addresses the stated reason. No evidence package guarantees a win because the issuer or applicable decision body evaluates the case under the relevant rules.


Q4. What evidence is needed to dispute a chargeback?

The correct evidence depends on the reason code. Common records include receipts, order confirmations, delivery proof, service-use logs, authentication records, refund confirmation, disclosed policies and customer communications. Every record should connect clearly to the disputed transaction.


Q5. How long does a chargeback take?

There is no universal duration. The network, reason code, provider, response stage and possible escalation determine the timeline. Merchants should follow the dates shown in their own dispute notice.


Q6. Can a merchant issue a refund after a chargeback starts?

The merchant should ask the processor before issuing a separate refund. A refund outside the active dispute workflow can create a second credit or make the accounting harder to reconcile. A prior refund should normally be documented through the case response.


Q7. Can an approved card payment be charged back later?

Yes. Authorization confirms that the issuer approved the transaction at the authorization stage. A later dispute can still challenge authorization, processing, delivery, quality, cancellation or credit handling.


12. The Bottom Line

A chargeback is a structured payment dispute, not simply another name for a refund. The issuing side raises the case, the acquiring side delivers it to the merchant, and the merchant must decide whether to accept the claim or submit evidence that answers the stated reason.

The strongest merchant process connects three records before a dispute occurs: the original payment, the customer’s agreement and the fulfillment event. That connection makes legitimate cases easier to accept, invalid cases easier to contest and every final debit or credit easier to reconcile.

Have a Question? Write to Us!
Contact
ADD: Room 402, Dewisen Building, No. 16, Gaoxin Nan Seventh Road, Nanshan District, Shenzhen City, China,518000