How to Report a Scam to Your Credit Card Company: Scripts
A card dispute is decided on a reason code and a short written record, not on how sympathetic your story is. The reason code is chosen from what you say in the first call, and it determines which evidence the issuer will look for. Getting the wording right is most of the work.
The reason code decides the evidence. Say the wrong thing and you will be asked to prove something you cannot, for a claim you could have won.
The Short Version
- Pick the right category before you call: fraud, not as described, or services not rendered.
- Use the network vocabulary — "dispute", "chargeback", "reason code" — rather than describing feelings.
- Never say you authorized the charge if you did not, and never say you did not if you did.
- Ask which reason code was filed and write it down with the case number.
- Send a written follow-up the same day with the documents that match that code.
Why Wording Decides the Outcome
Card disputes are not adjudicated by a person reading your story and deciding what is fair. They are adjudicated against a rulebook, and the rulebook is indexed by reason code. The code determines the burden of proof, the documents required, the deadline, and which party the network defaults in favour of.
That is why two people with identical facts can get opposite results. One described the situation in a way that mapped to a strong code with a light evidence burden; the other described it in a way that mapped to a weak code with a heavy one.
The good news is that the mapping is predictable. There are three main categories for scam-adjacent card claims, and each has a script.
The Fraud Script
Use this when your card details were used by someone else, or when you did not authorize the specific charge. This is the strongest category, and it is the one to use only when it is literally true.
Say: "I am calling to dispute a charge on my account as fraud. I did not authorize this transaction and I did not receive any goods or services from this merchant. The charge is [amount] on [date], and the reference is [number]. I would like to open a chargeback under the fraud reason code, and I would like the case number and the reason code you file it under."
Then answer only what is asked. If they ask whether you have the card in your possession, answer factually. If they ask whether you gave your details to anyone, answer factually — this is the question that most often reclassifies a fraud claim into something weaker, and a truthful answer is still the right one.
What the issuer will look for: that the card was not present or was used without authorization, that you still hold the physical card, and that you reported promptly. Promptness is weighted heavily.
The "Not as Described" Script
Use this when you paid for something and what arrived was materially different from what was advertised — a different model, a counterfeit, a wrong size, a product that does not work as listed.
Say: "I am disputing this charge as goods not as described. The listing stated [what was promised]. What I received was [what actually arrived]. I have photographs of the item and a screenshot of the listing as it appeared when I bought it. I contacted the merchant on [date] and they [did not respond / refused]. I would like to file a chargeback under the not-as-described reason code."
The evidence that decides this category is the listing as it was at the time of purchase. If the merchant has since changed the page, your screenshot is the case. Take it before you contact them.
One requirement that catches people out: most networks expect you to have attempted to resolve it with the merchant first, and to have returned the item if a return was reasonable. Keep the return receipt.
The "Services Not Rendered" Script
Use this when you paid for a service that was never delivered, or was delivered so partially that it does not constitute the service you bought. This is the category most scam-website and fake-service cases fall into.
Say: "I am disputing this charge as services not rendered. I paid [amount] on [date] for [the service described]. The service was never provided. The delivery date was [date] and nothing was delivered. I contacted the merchant on [date] by [email / their contact form] and received [no response / a refusal]. I have the order confirmation, the payment receipt and my contact attempts. I would like to file a chargeback under the services-not-rendered reason code."
What decides this category: proof of payment, proof of what was promised, proof of the promised delivery date, and proof that you tried to resolve it. A dated contact attempt is close to essential.
If the merchant's website has since gone offline, say so explicitly and give the date you last saw it working. A domain that disappeared is itself evidence, and it is worth capturing a screenshot of the error page.
What Never to Say
Some phrases are read as admissions or as signals that the case belongs in a weaker category. Avoid all of these.
| Do not say | Why it hurts |
|---|---|
| "I authorized it, but..." | Converts a fraud claim into an authorized-payment complaint, which has a much weaker position. |
| "I think it might have been..." | Uncertainty is logged as a customer-service issue rather than a dispute. |
| "I gave them my card details." | Can be read as authorization. If it is true, say it plainly and let the correct category be chosen — do not volunteer it as a confession. |
| "I should have known." | Reads as an admission of negligence and is used to argue you accepted the risk. |
| "I want compensation for the stress." | Signals a complaint rather than a dispute. Keep the two separate. |
| "Just do whatever you can." | Hands the classification to the agent. Name the category you want. |
Also avoid arguing about the merchant's character. The dispute is about a transaction, not about whether the seller is a bad person. Facts about the transaction are what get filed.
Written Follow-Up Template
Send this the same day, through the issuer's secure message centre where possible. Replace the bracketed fields.
Subject: Dispute follow-up — case [CASE NUMBER] — [AMOUNT] on [DATE]
I am writing to confirm the dispute I filed by telephone on [DATE] at [TIME] with [AGENT NAME/ID].
The disputed transaction is [AMOUNT] on [DATE], merchant [NAME AS ON STATEMENT], reference [NUMBER].
The reason code filed was [CODE, if known]. The basis of my dispute is [fraud / goods not as described / services not rendered].
Attached: [list each document by name].
Please confirm in writing that the dispute is open, the reason code on file, and the date by which a decision will be made.
[YOUR NAME]
Attach only what matches the reason code. A thick bundle of irrelevant material slows the review and can bury the one document that decides the case.
Keeping the Paper Trail
Disputes can take weeks and can be reopened. Keep everything in one folder, named by date, and keep it after the case closes.
- The case number and reason code, written down on the day you filed.
- The statement showing the charge, saved as a PDF rather than a screenshot where possible.
- The listing or offer as it appeared, captured before you contacted the merchant.
- Every contact attempt, with dates and the channel used.
- All correspondence with the issuer, including the provisional-credit notice and the final decision letter.
If the dispute is denied, the decision letter will state the reason. That reason tells you whether a second attempt with a different code, or an escalation to the regulator, is worth making. For the wider picture of what a dispute can and cannot achieve, see whether you can dispute a transaction if you were scammed.
If the Agent Refuses
Refusals usually take one of three forms, and each has a response.
| Refusal | Your response |
|---|---|
| "It is past the dispute window." | Ask for the exact deadline and the date it was calculated from. Deadlines run from the statement date or the date of discovery, and those are not always the same. |
| "You authorized the payment." | Ask which reason code they filed and on what basis. If the classification is wrong, ask for it to be reviewed by a supervisor. |
| "We need the merchant to agree." | Ask for the dispute to be filed anyway. The network, not the merchant, decides a chargeback, and the merchant's agreement is not a precondition. |
If the issuer still will not file, put the request in writing and escalate to the bank's complaints process, then to the consumer protection agency and the regulator for your country. A written refusal is itself useful: it is the document an ombudsman will ask for.
For the procedural walkthrough rather than the scripts, see how to report a scam to your credit card company.
Questions people ask
What do I say when I call my credit card company about a scam?
Name the category first: "I am disputing a charge as fraud" or "as services not rendered". Give the amount, date and reference, then ask for the case number and the reason code. The category you name determines which evidence the issuer will look for.
What is a reason code in a card dispute?
A reason code is the network-defined category a dispute is filed under. It sets the burden of proof, the documents required and the deadline. Two identical situations can produce different outcomes depending on which code was used.
Can I dispute a charge if I gave the scammer my card details?
It depends on what you were told and what you agreed to. If you were deceived into believing you were paying a legitimate merchant, the transaction may still be disputable as services not rendered. Be truthful about what happened and let the correct category be chosen.
How long does a credit card dispute take?
Issuers typically issue a provisional credit within a few days and a final decision within 30 to 90 days, depending on the network and the complexity. The decision letter will state the reason if the dispute is denied.
What if my card company refuses to file a dispute?
Ask which reason code they filed and on what basis, request a supervisor review, and put the request in writing the same day. If they still refuse, escalate to the bank's complaints process and then to your country's consumer protection agency and the card issuer's regulator.
Check the address before you send anything
A free scan reads public chain data in your browser: balance, activity, counterparties and flags. No wallet connection, no seed phrase, no signup.
Primary sources and further reading
- Consumer Financial Protection Bureau — the US federal complaint route for card and payment disputes
- FTC Consumer Sentinel Network — how consumer fraud reports are collected and shared
- FBI Internet Crime Complaint Center — federal reporting portal for fraud
- Visa consumer security guidance — card network guidance on reporting fraud and disputes
Related guides
Information only. We never promise recovery.