For a U.S. credit card charge dispute, find the first statement showing the problem. Write to the issuer, attach copies, and ask for a specific correction. Keep the packet tight.
People often call this a chargeback. For many card problems, the consumer process is a billing-error dispute with the issuer, while a merchant request is only one part of the record. It won't replace the notice the issuer requires.
These steps cover U.S. credit cards and credit-card billing errors. Debit cards, prepaid cards, bank transfers, and payment apps can follow different rules.
Start with the right type of dispute
Name the problem before you gather proof. An unfamiliar charge needs a different response from a damaged delivery.
Start with facts, not the word "chargeback."
| Problem | First move | Records to gather |
|---|---|---|
| An unauthorized credit card charge | Use the issuer's fraud or billing-dispute channel | Statement, date noticed, account activity, and issuer correspondence |
| A wrong amount or duplicate charge | Send written notice to the issuer; contacting the merchant may help too | Receipt, order confirmation, and records showing the duplicate or incorrect amount |
| Goods or services were not delivered or were not as agreed | Ask the merchant for a remedy and notify the issuer in writing | Order details, promised delivery date, tracking, photos, and messages |
| A promised refund or credit never appeared | Contact the merchant and issuer with a clear refund timeline | Cancellation confirmation, refund promise, credit amount, and later statements |
| A debit, prepaid, ACH, wire, or payment-app transaction | Use the bank or provider's dispute process | Provider records and transaction-specific evidence |
The FTC's credit card dispute guidance describes the written billing-error process. The CFPB's billing error regulation supplies the related federal framework.
What evidence should you send?
Your packet should answer three questions: what was charged, why it is wrong, and what happened afterward. A simple timeline gives the issuer a way to check the account.
Don't bury the point in screenshots. A large folder can still make a weak explanation.
| Document | What it helps establish |
|---|---|
| Statement or account page | Merchant name, amount, transaction date, and the first bill showing the error |
| Receipt or order confirmation | What you bought, the agreed price, and the expected date |
| Merchant emails or chat messages | Your request, the merchant's response, and any promised remedy |
| Shipping, return, or cancellation records | Delivery details, returned goods, cancellation timing, or a missing refund |
| Terms or refund policy | The policy shown when you purchased or canceled |
| Photos or service records | Damage, defects, missing items, or a service that was not performed |
| Fraud details requested by the issuer | When you noticed the charge and facts about your card or account activity |
Keep complete messages where possible. If you use a screenshot, leave the date, sender, relevant words, and order number visible.
Records don't always line up neatly. One email may say Tuesday, the portal may say Wednesday, and the receipt may use a merchant name you don't recognize; keep each record and explain the mismatch.
Gather and submit the evidence
Use the steps below before any deadline runs out.
- Find the first statement. Mark the disputed transaction and write down the date the statement was sent.
- Describe the error accurately. Use terms such as unauthorized, duplicate, wrong amount, not delivered, or refund missing only when they fit.
- Collect copies. Include the statement, receipt, order record, communications, and documents that support your explanation.
- Build a short timeline. List the purchase date, promised date, merchant contact, response, cancellation or return, and date you noticed the problem.
- Ask the merchant for a remedy when practical. Request a written correction or refund, but don't let that conversation run past the issuer's deadline.
- Send written notice to the issuer. Use the billing-dispute address on the statement when one is provided, or follow the issuer's secure submission instructions.
- Save the submission trail. Keep the letter, uploaded files, confirmation number, proof of delivery, and every reply.
Send copies, not irreplaceable originals. Redact unnecessary sensitive information, but leave enough account and transaction detail for the issuer to identify the charge.
A chargeback dispute letter you can adapt
A short letter can do the job. It needs a clear charge, a factual reason, and matching attachments.
Subject: Written billing error dispute - [merchant], [amount], [date]
I am writing to dispute the charge from [merchant] for [amount] dated [date] on my account ending in [last four digits].
The problem is: [brief, accurate description].
I contacted the merchant on [date] by [email, phone, chat, or other method]. The response was [describe the response, or state that no response was received].
Please investigate this billing error and correct the charge. I have attached [list the documents].
Please confirm receipt of this dispute and tell me if you need additional information.
[Full name]
[Address]
[Phone or email]
[Date]
Make each important claim traceable to an attachment. Unauthorized is a precise description. Use it only when the charge truly was unauthorized.
If you received the product but it was damaged or not as described, say that instead. The label should match the facts.
Deadlines that matter
Timing matters because the formal process has a short opening window.
Under the FTC's credit card dispute guidance, written notice generally must reach the issuer within 60 days after the first bill containing the error was sent to you. That clock starts with the bill, not simply the purchase date.
Keep the purchase date too. The issuer needs both dates to understand the transaction.
If you changed your address, the FTC says you must have sent the issuer the change in writing so it had the new address at least 20 days before the billing period ended.
After receiving the notice, the issuer generally must acknowledge it within 30 days. It doesn't have to do that if the problem was already resolved. The FTC says the issuer must resolve the dispute within 90 days.
Turns out, waiting for a merchant's promised fix can consume much of the first 60-day period.
A phone call or online form may start the issuer's internal process. If you're relying on the formal written billing-error procedure, send the written notice the issuer requires and keep proof.
Missed the 60-day period? Contact the issuer anyway and explain what happened promptly. Another issuer process may be available, but don't assume the same statutory protections still apply.
Merchant and card-network response dates are separate. Follow any deadline the issuer gives you, even if you already sent a general complaint.
If the merchant challenges your dispute
A merchant may answer with a receipt, shipping confirmation, customer communication, or similar record. Visa describes that type of response in its chargeback process explanation.
Thing is, one document may answer only one part of the dispute. Read what it actually proves.
| Merchant record | What your response should clarify |
|---|---|
| Receipt showing an approved purchase | Whether the amount, merchant name, and issue you reported actually match |
| Tracking marked delivered | The delivery address, date, signature, and any reason the record does not resolve your complaint |
| Refund or cancellation policy | The version shown at purchase and whether you canceled or returned the item under its terms |
| Message suggesting satisfaction | What the message actually referred to and whether the later problem remained unresolved |
| Technical records such as IP or device data | Which facts they establish and which facts they do not establish about your authorization |
Answer the issuer's questions directly. Keep the account of events short.
For non-delivery or a missing refund, use those descriptions clearly. Calling the problem fraud can send the dispute into the wrong review path.
Evidence checklist
Check the packet once before you submit it.
- [ ] Statement showing the disputed transaction and first bill date
- [ ] Exact amount, merchant name, and transaction date
- [ ] Written explanation of what went wrong
- [ ] Receipt, order confirmation, or service agreement
- [ ] Merchant communications and any promised remedy
- [ ] Delivery, return, cancellation, or refund records
- [ ] Photos or other documents supporting a damaged or incomplete order
- [ ] Copy of the letter or online submission
- [ ] Proof of delivery, confirmation number, or upload receipt
- [ ] Issuer's response deadline and follow-up records
To be honest, submission proof and the response deadline are easy to overlook. They matter if the issuer later says your documents never arrived.
If the issuer does not fix the problem
Check the destination first. Confirm that you used the correct address or the issuer's approved submission channel.
Then follow up in writing. Include the original submission date, disputed charge, missing response, and correction you want.
If the issuer mishandles the complaint or gives no meaningful response, submit a credit card complaint through the CFPB complaint portal. The CFPB says companies generally respond within 15 days. You can review the response and provide feedback for 60 days.
A CFPB complaint is an escalation route. It doesn't replace a timely billing dispute.
Common questions
Is a phone call enough to dispute a credit card charge?
A call may open the issuer's internal workflow. Don't rely on it alone for the formal written billing-error process.
Send the required written notice. Keep a copy.
Can a merchant receipt automatically defeat my dispute?
No. A receipt doesn't guarantee the outcome.
The issuer reviews it alongside your explanation, account records, and other evidence.
Is the 60-day deadline measured from the purchase date?
Usually, no. The formal billing-error deadline runs from when the first statement containing the error was sent.
Keep the purchase date in your timeline as well.
Does this process cover debit cards?
Not automatically. Debit, prepaid, ACH, wire, and payment-app disputes can use different rules and provider procedures.
Contact the relevant bank or service promptly.
For a credit card problem, mark the first statement showing the error, record its sent date, and start the timeline before contacting the merchant.