National merchant education
Chargebacks & Payment Disputes
A practical guide to the dispute workflow, merchant records, response decisions, prevention practices, and the questions to take to your processor or acquirer.
Start with the process
What a chargeback means for a merchant
A payment dispute begins when a cardholder questions a transaction through the card issuer. The issuer, card network, acquirer, processor, and merchant may each have a role before the case is resolved.
Dispute notice
The merchant typically receives a notice through its acquirer, processor, gateway, or dispute portal. The notice identifies the transaction, reason, response path, and applicable deadline.
Merchant decision
The business reviews its records and decides whether to accept the dispute or submit a response. A response should address the stated reason with relevant, accurate records.
Evidence review
The responsible providers route the response under current network rules. Supplying evidence does not guarantee that a chargeback will be reversed.
Outcome and records
The merchant should record the result, reconcile account activity, preserve the case file, and use recurring patterns to improve operations.
Decision path
Respond without guessing
1. Confirm the notice
Verify the case in a known provider portal or through a trusted support channel. Match the amount, date, transaction identifier, payment channel, and reason without emailing cardholder data or credentials.
2. Preserve the deadline
Record the provider's stated due date, time zone, submission method, and file requirements. Network rules change, so do not rely on a generic online deadline.
3. Choose an accurate response
Accept the dispute when the transaction should not be defended. If responding, address the specific reason and avoid irrelevant documents, altered records, or claims the business cannot substantiate.
4. Track the case
Save submission confirmation, monitor provider messages, reconcile debits or credits, and document the final status. Escalate unclear or conflicting instructions to the acquirer or processor.
Evidence planning
Build records around the customer journey
Useful evidence depends on the dispute reason and current provider rules. Organize records so staff can find the transaction story quickly.
Transaction identity
Keep order numbers, timestamps, authorized amounts, payment channel, receipt details, and a recognizable billing descriptor connected to the business record.
Customer communication
Retain relevant order confirmations, service messages, support history, cancellation requests, and refund communications under the business's retention policy.
Delivery or performance
Connect shipping, pickup, reservation, attendance, milestone, acceptance, or service-completion records to the exact order when those facts are relevant.
Policy presentation
Document which return, refund, cancellation, trial, or recurring-payment terms the customer saw and how acceptance was recorded.
Prevention
Reduce avoidable customer confusion
Make the merchant recognizable
Use clear receipts and customer communications, and confirm how the billing descriptor appears. Give customers an easy route to ask about an unfamiliar charge.
Set expectations early
State fulfillment timing, cancellation steps, return conditions, recurring terms, and customer-support methods before checkout and in follow-up messages.
Correct mistakes promptly
Investigate duplicates, incorrect amounts, failed cancellations, missing refunds, and fulfillment exceptions. Coordinate with the processor before taking action on a transaction already under dispute.
Review patterns
Group disputes by reason, channel, product, descriptor, fulfillment method, and workflow. Fix root causes instead of treating every case as an isolated event.
Responsibility boundaries
Know where to escalate
Merchant team
Owns accurate business records, customer communication, fulfillment evidence, staff access, response decisions, and reconciliation.
Acquirer or processor
Provides the merchant notice, case portal, deadlines, submission requirements, status information, and escalation route for the merchant's account.
Issuer and card network
The issuer handles the cardholder relationship, while network rules shape the dispute process. Merchants generally work through their acquirer or processor, not directly with the issuer.
Legal or specialist advice
Contract, regulatory, consumer-law, or litigation questions require qualified advice. This operational guide is not a substitute for legal guidance or provider instructions.
Related guidance
Continue your research
Common questions
Chargeback and dispute FAQ
Can a merchant respond to every chargeback?
Not necessarily. Rights and response options depend on the notice, reason, transaction, provider, and current network rules. Review the case instructions promptly.
What evidence wins a dispute?
No document guarantees an outcome. Relevant evidence should directly address the stated reason and follow the provider's current format and submission rules.
Should a merchant issue a refund after a dispute begins?
Do not assume. A separate refund can complicate reconciliation or duplicate a credit. Check case status and ask the responsible processor or acquirer how to proceed.
What should a merchant do first?
Verify the notice through a trusted channel, preserve the stated deadline, gather the transaction record, and contact the processor or acquirer when instructions are unclear.
Last editorial review: August 11, 2026. Sources reviewed: Visa merchant dispute guidance, Mastercard merchant rules and chargeback guide, and CFPB billing-dispute guidance.
Next step
Organize your dispute workflow
Payments Max can help map transaction records, provider responsibilities, customer communication, and operational questions before you compare payment solutions.
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