For a crypto card merchant dispute, preserve evidence from four places: the purchase agreement, fulfillment or cancellation, the posted card transaction, and the crypto funding or conversion ledger. Build the file before messages disappear, but use the dispute route and deadline stated by your issuer; no single chargeback rule applies to every card, country, or transaction.

Key Takeaways

State the exact problem: goods not received, service not provided, wrong amount, duplicate charge, cancellation ignored, or refund missing.

Save the terms and product description that applied when you ordered.

Keep merchant communication in chronological order, including your attempt to resolve the issue.

Pair the receipt with the final posted card and conversion records.

Redact secrets, submit through the official issuer channel, and retain proof of submission.

The online security guide covers safe account access and evidence handling during a financial complaint.

What kind of crypto card merchant dispute are you documenting?

Start with one sentence that describes the failure. Evidence for non-delivery differs from evidence for a duplicate amount or canceled subscription. Do not label every disagreement “fraud” or “refund missing.”

Dispute type	Core evidence	Common confusion
Goods not received	Order, promised delivery, tracking, merchant response	Delivery delay without a missed promise
Service not provided	Scope, appointment or access record, cancellation	Dissatisfaction with a completed service
Not as described	Listing, specifications, photos, expert record where relevant	Change of mind
Duplicate or wrong amount	Receipt and two posted entries	Authorization plus one final posting
Canceled recurring payment	Cancellation terms, request, confirmation, later posting	Cancellation after the next billing cutoff
Refund missing	Merchant credit proof and posted purchase	Unreleased authorization hold

If you did not authorize the transaction at all, use the issuer's fraud route immediately. This guide addresses an authorized merchant relationship that later became disputed.

Step 1: Save the purchase agreement

Preserve the order confirmation, invoice, item or service description, quantity, price, currency, delivery promise, cancellation policy, refund policy, and merchant identity. Save the version visible at purchase time where possible, not only a page that the merchant can later update.

Record the order number, merchant legal or trading name, website, physical address if shown, and payment descriptor. A card statement may use a processor or parent-company name that differs from the storefront.

For a subscription, save the billing interval, trial terms, renewal notice, cancellation steps, and effective cancellation time. Avoid relying on a cropped screenshot that omits the date, URL, or relevant qualification.

Step 2: Document fulfillment or non-fulfillment

For physical goods, keep shipping confirmations, tracking history, delivery photo, carrier case, pickup record, and any report of loss or damage. If tracking says delivered, document why it does not establish delivery to you: wrong address, inaccessible location, mismatched signature, or carrier correction.

For digital goods, record activation, download, login, license, or access failures and the device or account used. For services, keep appointments, attendance records, deliverables, and the agreed scope.

Photograph damaged or materially different goods before repair, disposal, or return. Preserve packaging, serial numbers, and return tracking where they matter. Do not fabricate a screenshot or alter metadata to make the case look stronger.

Step 3: Preserve merchant communication

Contact the merchant through a verifiable channel unless safety, fraud guidance, or issuer instructions say otherwise. State the order, problem, requested remedy, and a reasonable response point based on the contract and applicable rules.

Export complete email threads, chat transcripts, support tickets, and call notes. Record the date, time zone, channel, representative, promises, case number, and attachments. A screenshot of one favorable sentence can omit context; keep the full conversation.

If the merchant refuses, does not respond, changes its explanation, or promises a refund, preserve that result. Coinbase's card troubleshooting guidance, for example, asks customers to retain transaction details and steps already taken with the merchant.［1］ It is a program example, not a global evidence rule.

Step 4: Capture the posted card transaction

Save the final statement or transaction export showing merchant descriptor, posting date, amount, currency, card last four digits, and transaction reference. Also preserve the earlier authorization if the amount or descriptor changed.

Do not mistake an authorization and its final posting for two completed charges. Match dates, amounts, references, and available-balance effects. If a pending reserve remains, use the authorization hold guide.

For a missing merchant credit, obtain the refund reference and use the crypto card refund guide. A refund dispute requires proof of the promised credit as well as the original purchase.

Step 5: Add crypto funding and conversion records

Crypto funding creates an extra accounting layer, but it does not replace the card transaction. Save the asset, quantity, conversion timestamp, quote or applied rate, fiat proceeds, fees, and card-ledger entry used to fund the purchase.

If the amount changed between authorization and posting, include the worksheet from the exchange-rate settlement guide. Separate a merchant dispute from a disagreement about conversion.

Never include a wallet seed phrase, private key, complete API key, or unrestricted wallet export. A transaction hash or masked statement can identify the record without granting control.

Step 6: Build a chronological case file

Use stable filenames and an index:

Date and time	Event	Evidence file	What it proves
Purchase	Order accepted	Order PDF	Terms, item, amount, merchant
Expected fulfillment	Promise passed	Tracking or access log	Nature of non-performance
Merchant contact	Remedy requested	Full message export	Attempt to resolve
Card posting	Transaction completed	Statement	Posted amount and descriptor
Crypto conversion	Funding debited	Ledger export	Separate funding calculation
Dispute submission	Case opened	Confirmation	Channel, claim, and submission time

Keep originals read-only and make a redacted submission copy. List every redaction. Preserve file metadata where useful, and avoid repeatedly resaving images in a way that obscures when they were captured.

Write a short cover note: what happened, the remedy requested, the amount disputed, and which files support each point. Do not bury the issuer in unrelated account history.

Step 7: Check the issuer's process and jurisdiction

Read the cardholder agreement and current dispute instructions. Confirm eligible transaction types, required merchant contact, submission channel, evidence format, and any stated deadline. A prepaid, debit, credit, or crypto-linked program may provide different contractual and legal protections.

The U.S. Consumer Financial Protection Bureau explains recordkeeping and billing-error procedures for certain U.S. credit-card disputes.［2］［3］ Those pages are United States examples and do not establish rights for every prepaid, debit, crypto-linked, commercial, or non-U.S. card.

Ask the issuer which agreement and rule it is applying. If the amount is material or the classification is disputed, seek independent legal advice in the relevant jurisdiction rather than relying on a generic online timeline.

Step 8: Submit safely and preserve the receipt

Open the dispute route from the official issuer app or website. Verify the domain, sign in without following an unsolicited support link, and upload only the requested redacted evidence. Keep the exact claim category consistent with your cover note.

Save confirmation of submission, uploaded filenames, case number, date, and any provisional credit terms. If the issuer requests more information, record the request and your response as the next timeline entries.

Do not pay a “recovery agent,” disclose one-time codes, install remote-control software, or sign a crypto transaction to open a card dispute. Those actions are unrelated to legitimate card evidence collection.

Evidence checklist

Order, invoice, product or service description, and applicable terms.
Delivery, return, cancellation, or access records.
Complete merchant correspondence and case numbers.
Final posted card record plus relevant authorization or refund records.
Crypto conversion and funding-ledger records, with secrets removed.
Cardholder agreement and issuer dispute instructions.
Redaction log, evidence index, submission receipt, and follow-up history.

Summary

Define one precise dispute reason before assembling documents.
Preserve the purchase terms, fulfillment facts, and complete merchant contact history.
Pair the final card posting with any authorization, refund, and crypto conversion records.
Follow the issuer's stated process and jurisdiction-specific rules.
Submit a redacted, indexed package and retain proof of every step.

Frequently Asked Questions

Is a merchant dispute the same as reporting card fraud?

No. Fraud usually means you did not authorize the transaction. A merchant dispute often concerns an authorized purchase that was not delivered, was misdescribed, was charged incorrectly, or was not canceled as agreed.

Do I need to contact the merchant first?

That depends on the issuer process, dispute type, safety considerations, and applicable rules. Preserve any attempt and result, or the issuer instruction explaining why direct contact is unnecessary.

Is a screenshot enough evidence?

Usually not by itself. Keep full messages, statements, receipts, dates, URLs, references, and context; use screenshots as part of that package.

Should I include the crypto transaction hash?

Include it when it identifies the relevant funding event, but explain how it connects to the card ledger. It does not prove the merchant dispute by itself.

Can I dispute an exchange-rate difference as a merchant problem?

Only if the merchant amount itself is wrong. Card-network or crypto conversion questions belong with the party that applied that rate.

What should I redact?

Redact full card numbers, CVV, passwords, one-time codes, seed phrases, private keys, unrelated transactions, and unnecessary identity data while leaving transaction identifiers usable.

Is there one universal chargeback deadline?

No. Deadlines and rights vary by agreement, card type, network process, dispute reason, and jurisdiction. Check the issuer's official instructions promptly.

Can a VPN decide or accelerate the dispute?

No. A VPN cannot create merchant evidence, alter a card transaction, grant chargeback rights, or control the issuer's investigation.

Disclaimer: This article provides general recordkeeping and security information, not legal, financial, dispute, or account-specific advice. Rights, deadlines, evidence requirements, and outcomes depend on the card program, agreement, facts, and jurisdiction.

Sources

Coinbase — Coinbase Card Troubleshooting: https://help.coinbase.com/en/coinbase/trading-and-funding/coinbase-card/cb-card-troubleshoot
Consumer Financial Protection Bureau — How to Fix Mistakes in Your Credit Card Bill: https://www.consumerfinance.gov/consumer-tools/credit-cards/how-to-fix-mistakes-in-your-credit-card-bill/
Consumer Financial Protection Bureau — How Do I Dispute a Charge on My Credit Card Bill?: https://www.consumerfinance.gov/ask-cfpb/how-do-i-dispute-a-charge-on-my-credit-card-bill-en-61/

Sources checked 9 September 2026.

Related articles:

Crypto Card Merchant Dispute: What Evidence to Keep