Assemble the dispute record
- Match each disputed amount to its statement entry, merchant descriptor and transaction date.
- Keep order records, cancellation terms, delivery evidence and merchant correspondence in sequence.
- Record the dispute reason in factual language and save the issuer's reference and deadline.
Match the dispute reason to the proof that supports it
A focused record is easier to review than a folder of unrelated screenshots.
- Transaction not authorized
- Preserve the statement entry, card possession facts, alerts and the time access was blocked.
- Merchant or delivery problem
- Keep the order, terms, cancellation or refund record, delivery evidence and merchant messages.
- Amount or duplicate error
- Place the correct receipt beside each statement line and explain the difference in one sentence.
Match every claim to a transaction record
- Export or save the statement while the transaction details are visible.
- Make one row per transaction with date, descriptor, amount and status.
- Keep the case number, submission proof and response deadline together.
Build the file around the actual dispute reason
A focused file explains one transaction and one reason clearly. Extra screenshots that do not support that reason can hide the useful evidence.
- Transaction identity
- Capture merchant descriptor, amount, date, status and statement reference. If the merchant name differs from the storefront or website, record both without assuming the charge is fraudulent.
- Authorization question
- State whether you made, approved or benefited from the transaction and whether the physical card remained with you. Preserve security alerts and the time the card or account was secured.
- Merchant problem
- For delivery, cancellation, refund, duplicate or amount disputes, keep the order, terms, receipt, tracking and messages that show what was promised and what happened.
- Submission control
- Record every file submitted, the channel, confirmation and deadline for anything still requested. Keep the original evidence and send a redacted copy when full account or identity numbers are not required.
Use the issuer's dispute categories and instructions. A card replacement protects future access, but it does not automatically open or complete the transaction dispute.
Build a focused dispute file
Separate dispute types
An unauthorized transaction, duplicate charge, wrong amount, missing refund and product dispute are not the same. Use accurate language so the issuer sends the case through the right process.
Explain merchant descriptors
A statement name can differ from a storefront name. Check legitimate receipts and household users before asserting fraud, but do not delay reporting a compromised card.
Submit a focused evidence set
Include the relevant statement line, receipt or cancellation record, merchant correspondence and short chronology. Redact unrelated balances or account numbers when the channel allows.
Track the decision
Record temporary credits, requests for more information and final decisions separately. Save any appeal or complaint deadline stated in the response.
Records that support the next step
Put calls, alerts and transaction changes into a verifiable fraud incident timeline.
If the disputed amount affects essential payments, calculate the short-term cash-flow amount to discuss.
For an ATM transaction, preserve the terminal details described in the unauthorized cash-withdrawal guide.
Questions about building the record
Should I contact the merchant?
For billing or service errors it may help, but report suspected card compromise to the issuer immediately. Follow the issuer's instructions.
Can I dispute a pending charge?
Tell the issuer about the compromise now; it can explain when a particular pending item becomes eligible for a transaction dispute.
Processes, rights and deadlines depend on your location, provider and policy. Use the relevant official service for your jurisdiction.