A woman in Lisbon buys a $99 course from you. She sees $99.00 on your checkout page and clicks pay. Three days later her banking app shows a charge of €92.40. A week after that, her statement posts it as €94.71. She does the math, gets confused, and opens a dispute that says the amount is wrong.

Nobody lied in this story. Not you, and not her. The number changed because the money crossed a border, and every party that touched it had a say in the final figure. You will still be the one asked to explain it.

Why the number moved

A cross-border card payment passes through several hands. Each hand can change what the cardholder finally sees.

The first number is the presentment currency. This is the currency you showed on the checkout page and the currency you told Stripe to charge. If you priced in dollars, the charge was created in dollars.

The second is the conversion done by the cardholder's side. When the card is denominated in euros, the card network and the issuing bank convert the dollar amount into euros. You don't control the rate that gets applied. The rate can also differ between the day the charge is authorized and the day it settles, which is why a pending amount and a posted amount often don't match.

The third is the issuer's own foreign transaction fee, if their card has one. Many issuers add a small percentage on purchases made in a foreign currency or processed abroad. It appears folded into the total or as a separate line, depending on the bank. You never see that fee and you never receive it, but the customer experiences it as part of what you charged them.

Put those together and a charge that was exactly $99.00 on your side can display as an unfamiliar figure on theirs, one that drifts for days. To the customer it looks like an error. To you it's arithmetic you had no part in.

What the customer is actually claiming

This dispute rarely arrives labelled "currency." It usually shows up as one of these:

  • The amount was incorrect. They believe you charged more than advertised.
  • Unrecognized or fraudulent. The amount doesn't match what they remember agreeing to, so the charge feels foreign in the literal sense.
  • Duplicate. A pending authorization in one amount and a posted charge in another can look like two separate charges.

The reason code tells you which story the bank was handed. Your evidence has to answer that story, not the story you wish they had told. If you haven't yet learned to read the code, do that first, because it decides which facts matter.

The one idea: prove the agreed price, not the final price

Here is the trap. Your instinct is to explain exchange rates, and that is a lecture the reviewer doesn't need. The reviewer is not deciding whether currency conversion exists. They are deciding a narrower question: did the customer agree to pay this amount, in this currency, for this thing?

You can't prove what the bank converted it into. You can prove exactly what the customer saw and approved. That is the entire case.

So anchor everything on the presented price. Your evidence should show one consistent number, in one named currency, from the moment they decided to buy to the moment you charged them. Then the gap on their statement is visibly something that happened after your part of the transaction ended.

What good evidence looks like

The checkout view. A screenshot or reproduction of the page as the customer saw it, with the price and currency symbol clearly legible. If your checkout shows "$99.00 USD," include that. The currency code matters because a bare dollar sign is ambiguous across several countries.

The Stripe charge record. It shows the amount and currency that were actually charged. This ties the checkout number to the payment and demonstrates they match to the cent.

The receipt you sent. The email receipt is a time-stamped record that the customer was told the same figure afterward. Include the delivery confirmation if you have it. A receipt that states the amount and currency again is quiet, strong support.

Proof of what they received. Access logs, a download record, a shipping confirmation. The amount dispute often rides alongside a not-received claim, and delivery evidence closes both at once.

A short note on the conversion. One or two sentences, no more. For example: the charge was made in USD at the displayed price; any different figure on the cardholder's statement reflects conversion and fees applied by the card network or issuer after the charge. Say it plainly and move on.

What to leave out

Don't paste a currency calculator screenshot. Don't quote a rate for that day, because you can't verify what rate the issuer used and a wrong guess hands the reviewer a reason to doubt the rest. Don't speculate about the customer's bank fees. State that conversion happens downstream and keep your claims to what your own records can prove.

Resist tone, too. The customer is probably not committing fraud. They are confused by a number that really did change. A calm, factual response reads as more credible than an indignant one.

When you might not win

Be honest about the weak cases. If your checkout never displayed a clear currency, or showed one price and charged another, the customer's complaint has merit and no framing fixes it. The same goes for a pricing page that said one thing while the charge reflected a different tier.

This is also where the real fix lives, because most of these disputes are preventable before anyone files anything.

Your next moves

  • Open your own checkout today in a private window and look at it as a stranger would. Confirm the price shows a currency code (USD, not just $) on the page where they click pay.
  • Check your receipt template. Make sure the amount and currency appear in the email exactly as they did at checkout, and that the line item description matches what you sold.
  • Screenshot your checkout and receipt now, dated, and save them with your dispute files. If you change the page later, you'll still be able to show what it looked like on the purchase date.
  • Pull your last year of disputes and filter for customers outside your home country. If a cluster claims wrong amounts, you've found a pattern worth fixing at the source.
  • Write a two-sentence conversion note as a reusable paragraph for future cross-border responses, so you're not improvising under a seven-day clock.

Where Argeback fits

The hard part of this dispute isn't the argument. It's assembling the checkout view, the charge record and the receipt into a clean response before the deadline, while you're on a phone somewhere and the dispute notice arrives at the worst hour. Argeback pulls those records from your Stripe disputes, drafts a response built around the price the customer agreed to, and files it before the seven days run out. If cross-border customers are starting to show up in your dispute list, you can see how it works at argeback.lumenlabs.works.