Currency Conversion Markups: The Silent Fee Stacking on Top of Stripe and PayPal

A fan in Manila buys your $29 course. Your dashboard says $29 sold. Your bank statement, three days later, says something like $27.40 landed. You already know about the processing fee — that's the cut you signed up for. But there's a second deduction hiding in that gap, one almost nobody explains to creators: a currency conversion markup. It's the spread a bank or processor quietly adds when converting a buyer's currency into yours, and unlike the processing fee, it's rarely itemized anywhere you'd naturally look. If you sell to an international audience — and online, you almost always do — this markup nibbles at every cross-border sale whether you've noticed it or not.

The fee you already know, and the one riding along with it

Every payment processor charges a processing fee — a percentage plus a small flat amount per transaction. That's the cost of moving money securely, and it's the same whether the buyer is next door or on another continent. Currency conversion is a separate cost that only shows up on cross-border transactions, and it works differently: instead of a flat fee, it's a spread baked into the exchange rate itself. Say the real mid-market rate between euros and dollars is 1.00 EUR = 1.08 USD. A processor converting that payment might apply 1.06 USD instead, quietly keeping the difference. You never see a line that says "currency markup: $0.35" — you just see a slightly lower final amount, and unless you go looking, it blends into "that's just what the fee was."

Where the spread actually gets applied

There are a few distinct points where conversion can happen:

• At checkout, if the buyer pays in their own currency and the processor converts it to the currency your account is set up in — this is the most common scenario for a global creator audience.
• At payout, if you're paid in a currency you don't primarily use and your bank converts it again when it lands in your local account — a second conversion, a second spread, on the same dollar.
• Inside PayPal specifically, which has historically applied its own conversion rate on cross-currency transactions that can differ meaningfully from the interbank rate, separate from PayPal's standard processing fee.
• On the card network side, if the buyer's card issuer does its own conversion before the money even reaches the processor — this one is largely outside anyone's control but is worth knowing exists.

The worst case is stacking: a buyer pays in Currency A, it converts to Currency B at checkout, then converts again to Currency C at your bank. Two spreads on one sale is how a $50 product quietly becomes $46-and-change with nothing that says why.

A concrete illustrative example

These numbers are illustrative, not a quote from any specific processor, but they show the shape of the problem. Imagine a $40 digital product sold to a buyer paying in a foreign currency:

Nothing in that chain is dishonest — conversion spreads are how currency exchange has worked for decades in banking generally, not just payments. But if you're pricing a $40 product assuming you keep $38-ish after "the fee," and cross-border sales actually land closer to $36-37, that gap adds up fast once you're doing meaningful volume from outside your home market.

What you can actually do about it

You can't negotiate away currency conversion — it's a real cost of moving money across borders, not a junk fee. But you have more control than it feels like.

Reduce how often conversion happens at all

The single biggest lever is making sure your primary payout currency matches the currency most of your revenue actually arrives in. If the bulk of your audience is in the US, holding and getting paid in USD means only the minority of non-USD sales ever trigger a conversion, rather than every sale getting converted twice. When you create your store and connect Stripe or add a PayPal email, this is worth setting up correctly from day one rather than fixing later.

Price with the spread already priced in

If a meaningful share of your buyers pay in a currency that gets converted, build a small buffer into your price rather than pricing to the exact cent and being surprised every payout cycle. A product priced at $39 instead of $35 gives you room to absorb a spread you can't see coming and still land where you intended.

Know your real take-home rate, not the listed one

Track a rolling average of what you actually keep per international sale versus per domestic sale. If domestic sales net you roughly 96 cents on the dollar and international sales net closer to 91-93 cents, that's your real spread — and it's the number you should be using when you model out whether hitting a Pro plan or scaling international marketing spend actually pencils out.

A fee you can see is a cost. A fee you can't see is a habit you don't know you have.

Where store.fan fits in

store.fan doesn't sit between you and your money — when you connect Stripe in one click or add a PayPal email, payments go straight to your own account, with Apple Pay and Google Pay working automatically for buyers on top of that. There's no store.fan wallet holding funds or adding its own conversion step, and paid plans run at 0% platform fees, so the only conversion math you deal with is whatever your processor and bank apply — not a third layer stacked on by the storefront itself. That's exactly why understanding processor- and bank-level conversion is worth ten minutes: it's the one part of the stack genuinely outside anyone's control but yours to plan around.

If you're just getting your pricing strategy in order, a live example store is a useful reference for how creators structure pricing across a mixed product line, and the blog has more guides on pricing and payouts specifically if this is a rabbit hole you want to keep pulling on.