National merchant dispute guidance

What Is a Chargeback?

A chargeback is a card-payment reversal initiated through the cardholder's issuing bank under a card-network dispute process. For a merchant, it means the transaction has been challenged and the disputed amount may be removed or held while the case is handled.

Plain-language overview

A chargeback is not the same as a merchant refund

A merchant refund starts when the business returns funds through its payment system. A chargeback starts within the card dispute framework after a cardholder questions a transaction with the issuer. The issuer, card network, acquirer, processor, and merchant may each have a role, depending on the network and case.

Use the live case instructions: terminology, deadlines, evidence rules, and available response options vary by network, processor, acquirer, transaction type, and dispute condition. The notice in the merchant's approved portal is the operational source for that case.

Why disputes arise

Common chargeback categories

Fraud or an unrecognized charge

A cardholder may state that the payment was not authorized or may not recognize the merchant name on the statement. The applicable authentication and transaction records depend on the payment channel.

Authorization or processing issues

A dispute may concern authorization, duplicate billing, an incorrect amount or currency, late presentment, or another transaction-processing condition.

Goods or services concerns

The cardholder may say an order did not arrive, differed from its description, was canceled, or did not meet the disclosed terms. Fulfillment and communication records may be relevant.

Credit or refund concerns

A cardholder may claim that an expected credit was not processed or posted. Merchants should reconcile the original sale and the refund record before responding.

Typical workflow

What happens after a transaction is disputed

The cardholder contacts the issuer

The issuer reviews the cardholder's claim and transaction information. Some inquiries can be resolved before becoming a formal chargeback, while others proceed under a network dispute condition.

The merchant receives a case notice

The acquirer or processor generally delivers the notice through a portal, report, or approved communication channel. The notice should identify the transaction, reason, response deadline, and permitted next steps.

The merchant reviews the facts

The team matches the case to the original payment, order, customer communication, fulfillment, cancellation, and refund records. The reason code or condition helps focus that review.

The merchant accepts or responds

If the claim is correct or cannot be supported, the merchant may accept it. If the merchant challenges the case, it submits the relevant response and evidence through the provider's approved workflow before the displayed deadline.

The case moves toward an outcome

The issuer and other parties evaluate the response under applicable rules. Additional stages may exist, but merchants should not assume every case offers the same sequence or appeal options.

First response

What a merchant should do when a chargeback arrives

Confirm the notice is genuine

Open the case through the known processor or acquirer portal. Avoid sending records to an unfamiliar address or following credentials links from an unexpected message.

Record the deadline

Use the date, time zone, and submission method shown in the case. Set an earlier internal deadline so the response can be reviewed and submitted on time.

Match the transaction

Confirm the amount, date, currency, payment channel, transaction identifier, order number, and customer record before deciding how to proceed.

Address the stated reason

Collect only relevant, legible records that answer the dispute condition. Do not alter documents, invent details, or overwhelm the reviewer with unrelated material.

Evidence discipline

Useful records depend on the claim

Potential records can include receipts, order details, delivery or service confirmation, authentication results, a disclosed refund or cancellation policy, customer messages, recurring-payment consent, and proof of a processed credit. No single document proves every case. The response should connect reliable records to the exact dispute condition and follow the current provider prompts.

Protect payment data: use approved dispute channels and follow data-handling requirements. Never submit complete card numbers, passwords, bank credentials, or secret API keys through a general contact form.

Operational prevention

Reduce avoidable confusion before a dispute

Make billing recognizable

Use the descriptor and customer-facing business information approved for the account, and provide support details customers can recognize and use.

Disclose important terms

Present return, cancellation, delivery, recurring-payment, and service terms clearly before purchase, then preserve the version the customer accepted.

Keep connected records

Link payment, order, fulfillment, refund, and communication records with consistent identifiers so the team can retrieve them quickly.

Review patterns

Track dispute reasons and operational causes without treating every chargeback as fraud. Recurring confusion may reveal a descriptor, fulfillment, support, or policy issue.

Common questions

Chargeback FAQ

Does a chargeback mean the merchant did something wrong?

No. It means the transaction entered a formal dispute process. The underlying facts and applicable rules still need to be reviewed.

Can a merchant respond to every chargeback?

Response rights and options depend on the case, stage, deadline, and network or provider rules. Follow the choices displayed for the live case.

Is a chargeback a refund?

Both can return funds to a cardholder, but they begin through different workflows. A refund is initiated by the merchant; a chargeback is initiated through the issuer's dispute process.

Where should a merchant get help?

Start with the processor or acquirer portal and support contacts listed for the merchant account. Use current official network rules for additional context.

Last editorial review: August 11, 2026. Sources reviewed: current Visa chargeback guidance and Mastercard merchant dispute rules and guidance. Network rules and provider workflows can change.

Next step

Create a repeatable dispute workflow

Document who receives notices, how deadlines are tracked, where supporting records live, who approves responses, and how outcomes are reconciled.

Contact Payments Max

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US