Tutorial8 min read

International Stripe Fees: How Cross-Border Charges Compound

International card surcharge + currency conversion + Connect cross-border can stack to 5.9% on a single transaction. The math, the mitigations (multi-currency settlement, multi-entity setups, local payment methods), and the threshold at which each pays off.

For businesses serving international customers, Stripe fees compound in ways that aren't obvious from the public pricing page. International card surcharges, currency conversion fees, and Connect cross-border surcharges all stack on top of the base rate. This article walks through each layer and the practical strategies for reducing cross-border Stripe costs.

Run your specific scenario through the international transaction calculator.

Three Layers Stack Up

International Stripe fees come from three sources, applied independently:

1. International card surcharge. Cards issued outside the merchant's country pay a higher rate. In the US: +1.5% (so 4.4% total). In the UK and most of EU: +1.75% (so 3.25% total for European-rate countries).

2. Currency conversion. When charging in a different currency than your settlement currency, Stripe applies a conversion fee — 1% in the US, 2% in most other countries.

3. Connect cross-border. When platform and connected account are in different countries, Stripe adds 0.25% on every transaction.

These don't replace each other; they stack. A US merchant taking €100 from a UK customer with a UK card, settling in USD, on Express Connect with a European seller pays: 2.9% (base) + 1.5% (international card) + 1% (currency conversion) + 0.25% (Connect Express) + 0.25% (cross-border) = 5.9% effective on percentage component, plus the $0.30 fixed fee. That's $6.20 on a $100 transaction.

What Counts as "International"

Card origin is what matters — not the customer's location. A US merchant treats a Canadian card as "international" even if the customer is shopping from Times Square. Stripe determines card origin from the BIN (the first 6-8 digits of the card number) which identifies the issuing bank's country.

This trips up merchants who model fees based on customer geography. The actual fee is based on card geography, which often differs (tourists, international remote workers, cross-border employees).

Currency Conversion: When and Why

Currency conversion happens whenever the charging currency differs from your Stripe settlement currency. By default, your settlement currency is the currency of your country (USD for US merchants, GBP for UK, EUR for Eurozone, etc.).

Worked example: US merchant taking €100 from a European customer.

  • Card charged: €100
  • Stripe converts €100 → USD at Stripe's FX rate (close to mid-market, but with a 1% spread baked in)
  • USD amount lands in your account: ~$108 (depending on rate)
  • The 1% conversion fee is what funds Stripe's FX margin

You can avoid this by enabling multi-currency settlement: maintain a EUR balance in your Stripe account that gets paid out to a EUR-denominated bank account. No conversion fee — but you now have a EUR balance to manage on the bank side, which has its own FX cost when you eventually convert to your home currency.

The threshold where multi-currency settlement pays off is roughly 30% of revenue from a single non-home currency. Below, the bank-side FX cost on payouts wipes out the savings. Above, the math shifts in favor.

Where to Incorporate

For businesses with meaningfully international customer base, where you incorporate has a real Stripe cost impact:

Pure US-customer business: US incorporation. Standard 2.9% + 30¢, $0 international surcharge.

Mixed US + EU customer business: US incorporation if EU < 40%, EU incorporation if EU > 60%. The crossover is where the international card surcharge in one direction equals the surcharge in the other.

Pure EU-customer business: EU incorporation (UK, Ireland, or Eurozone). Stripe's European rate is 1.5% + 25¢ on European cards — half the US rate. For this segment, US incorporation costs you 1-1.5% on every transaction.

Global business with strong specific-region presence: multi-entity setup. Separate Stripe accounts in US, EU, and UK with sellers/customers routed appropriately. High operational overhead — typically only justified above $1M/month in cross-border volume.

Multi-Entity Setups

For platforms processing $1M+/month in cross-border volume, splitting into multi-entity Stripe accounts can save serious money. Example structure:

  • US LLC with US Stripe account: handles all US-origin customer transactions
  • UK Ltd with UK Stripe account: handles all UK + EU-origin customer transactions
  • Routing logic in your application: customers see the right merchant of record based on their card origin

Savings: ~1-1.5% on cross-border transactions that previously went through the wrong-region account.

Cost: tax/legal/compliance overhead of operating multiple entities, plus engineering work for the routing logic. Typical setup cost: $50k-$100k for tax structuring + 1-2 weeks of engineering.

The math pencils out at roughly $1M/month in cross-border volume — below that, the operational cost dominates the savings. Above, savings start running into the high six figures annually.

Connect Cross-Border in Detail

For marketplaces using Connect, the cross-border surcharge applies whenever the platform's country and the connected account's country differ. So a US-incorporated marketplace with European sellers pays 0.25% on every transaction settled to those European sellers — on top of all other fees.

Two ways to mitigate:

  1. Multi-region Connect accounts (same as multi-entity for non-Connect): separate Connect accounts in each region with sellers routed to the right one. Eliminates cross-border fee entirely, at operational cost.

  2. Standard Connect instead of Express/Custom. Standard Connect doesn't have the Connect-type surcharge (Express/Custom +0.25%), so you save the 0.25% there even with cross-border still applying. Trade-off: you give up the managed-onboarding flow that Express provides.

For most international marketplaces, the answer is "Standard Connect, accept the cross-border fee, plan to multi-region above $1M/month."

Practical Strategies, Ranked

1. Settle in the right currency. If you have a single dominant non-home currency representing 30%+ of revenue, enable multi-currency settlement. Saves 1-2% on those transactions immediately.

2. Be intentional about incorporation. New businesses targeting European customers: don't reflexively incorporate as a US LLC. Run the math first.

3. Promote local payment methods to international customers. SEPA Direct Debit for European customers (€0.35 flat) is much cheaper than card. Bacs Direct Debit for UK B2B (1% capped at £4) is cheaper than card. Apple Pay/Google Pay for mobile (same rate as card but better conversion).

4. Multi-entity Stripe setup at scale. Above $1M/month in cross-border volume.

5. Negotiate cross-border surcharges in Stripe contract. At enterprise scale, the 0.25% cross-border on Connect is negotiable. Not surfaced as a public knob; bring it up in the conversation.

What Doesn't Work

A few things that look like they should reduce international fees but don't:

  • Charging customers in their currency to avoid the international surcharge. The international surcharge is based on card origin, not customer-charged currency. Charging in EUR doesn't help if the card is European — you'll pay both the international surcharge AND currency conversion.
  • VPN-based geographic routing. Doesn't change card origin. Stripe's BIN-based detection is reliable.
  • "Just absorb the cost in the price." Surcharging international customers is legal in some markets, illegal in others (most EU consumer contexts). Even where legal, it often tanks conversion.

The right framing isn't "how do I avoid international fees" — they're a real cost of serving international customers. The right framing is "given my customer mix, what's the most efficient corporate structure and payment-method mix to minimize the cross-border premium." Run the numbers. The international calculator shows exactly what each component costs for your scenario.

Try the tools