International Payment Processing for Founders: The Real Costs, the Options, and What Nobody Explains

The first time you set up a payment gateway, the decisions are relatively simple. Pick Stripe (or PayPal, or whatever's available in your country), integrate it, start accepting payments.

The second time — when you're running a business that has customers in multiple countries, multiple currencies, and complex compliance requirements — you realise that "payment processing" is a field in itself, with substantial nuance between what the documentation says and what actually happens in production.

This is the fuller picture.

The Currency Problem

Your payment processor settles in a currency. Your costs are in a currency. Your customers pay in their currency. These three are often different, and the cost of the conversion between them is hidden in exchange rate spreads that are rarely as transparent as the transaction fee.

Scenario: A UK Ltd business using Stripe. A US customer pays $200 for a product. Stripe converts to GBP at their exchange rate and settles to your UK bank account. The rate Stripe uses is close to mid-market but includes a margin. Your bank may apply another conversion margin when the funds arrive. Your accountant books the transaction in GBP. Currency exposure: the USD/GBP rate may have moved between invoice and payment.

For businesses with significant multi-currency volume, the aggregated currency conversion cost is often higher than the processor fee. Solutions:

Multi-currency accounts: Wise Business and Revolut Business allow you to hold balances in multiple currencies, receive payments in the customer's currency, and convert only when needed and at rates close to mid-market. Stripe can pay out to a Wise USD account if you have one.

Stripe multi-currency settlement: Stripe can settle in the presentment currency (the currency the customer pays in) if you have bank accounts in those currencies. Worth exploring at scale.

Invoice in the customer's currency: For B2B clients, invoicing in their currency (USD for US clients, EUR for EU clients) is good practice. It eliminates their conversion friction and puts the exchange rate risk on you — which you can manage through holding multi-currency balances.

PSD2 and Strong Customer Authentication in Europe

If you're selling to European customers and you're not compliant with PSD2's Strong Customer Authentication (SCA) requirements, you're either experiencing unexpected payment failures or running in a regulatory grey zone.

SCA requires most online card payments to EU/EEA customers to be authenticated with two factors. The standard mechanism is 3D Secure (3DS2). When triggered, the customer is redirected to their bank's authentication flow (usually a one-time password via SMS or their banking app).

What this means in practice:

Stripe: Implements SCA automatically for European payments if you use Stripe.js and Payment Intents API. Legacy integrations using Charges API may not handle SCA correctly.
Subscription payments: Recurring charges after the first authenticated payment require "off-session" authentication or exemption application. Stripe handles this with Payment Intents and Setup Intents — but only if integrated correctly.
Exemptions: Small transactions (under €30), low-risk transactions (determined by the issuing bank's fraud model), and merchant-initiated transactions may be exempt. Applying for exemptions can improve conversion rates.

Check if you're using Stripe's Payment Intents API (not the legacy Charges API). If not, migration should be prioritised.

High-Risk Payment Processing

Certain business categories are classified as "high risk" by mainstream processors — travel companies, subscription businesses with high refund rates, gambling-adjacent products, adult content, certain financial services, firearms accessories, supplements, and others.

Being high-risk means:

Stripe, Square, and PayPal may decline your business or terminate your account without warning
Rolling reserves (Stripe holds back 10–25% of your revenue for 90–180 days as a chargeback buffer)
Higher per-transaction fees
More intensive KYC/KYB (Know Your Customer/Business) requirements

For travel businesses specifically: Airline ticket sales and OTA businesses are inherently high-risk for payment processors because of the time gap between booking and travel (during which disputes and refunds can occur) and because the ticket value is high. This is one of the structural challenges in operating a travel tech business.

High-risk merchant accounts are available from specialist acquirers (Payvision, Verotel, Vector Payments, Sofort, many others) who price accordingly — typically 3–7% + fixed fee, versus 1.4–2.9% for standard accounts. Rolling reserves are common.

Chargeback mitigation (important for high-risk categories):

Clear refund policy visible before purchase
Descriptor management (the name that appears on the customer's bank statement — make it recognisable to avoid "I don't know what this charge is" disputes)
Order confirmation emails with clear descriptions
3DS authentication to shift liability to the issuing bank
Rapid customer service response to pre-chargeback complaints

Payment Methods Beyond Cards

Card-centric payment processing is fine for UK/US/EU markets. It misses significant payment volume in markets where alternative methods dominate.

SEPA Direct Debit: For recurring payments from EU bank accounts. Lower cost than cards, higher failure rate, 8-day settlement delay. Stripe supports it.

iDEAL (Netherlands), Bancontact (Belgium), Sofort/Klarna Sofort (Germany/Austria): Bank redirect payment methods that are the default for online payments in these markets. A Dutch customer may prefer iDEAL over a card. Stripe Checkout supports these automatically when presented to eligible customers.

Buy Now Pay Later: Klarna, Afterpay, Affirm — significant in certain verticals (retail, consumer goods). If your average order value is high enough, BNPL can improve conversion by reducing the upfront cost barrier.

Alipay / WeChat Pay: For customers from mainland China, these are the dominant payment methods. Card payments are an afterthought. If you serve Chinese consumers, you need to offer these or accept that a large proportion of potential customers can't pay you.

UPI (India): Unified Payments Interface is the dominant real-time payment method in India. Razorpay and Cashfree are the primary gateways for accepting UPI.

bKash / Nagad (Bangladesh): Mobile financial services that function as the primary payment method for a large proportion of the Bangladeshi population. Not available through standard global gateways — integration requires direct partnerships.

Managing Multiple Gateways

At scale, the pragmatic answer is multiple payment gateways:

Primary gateway (Stripe or Adyen) for card payments in primary markets
Regional gateways for high-volume markets with local payment method preferences
Backup gateway for when the primary fails (payment gateway outages happen)

The complexity this creates — reconciliation across multiple systems, different settlement currencies, different reporting formats — is real and requires an accounting and operations setup that can handle it.

Tools that help: Spreedly (gateway abstraction layer that lets you route payments through multiple gateways through one API), Adyen (single platform that supports many local payment methods globally at enterprise scale).

Payouts: Getting Money to Suppliers and Partners

For marketplace and OTA businesses that need to pay out to suppliers (hotels, airlines, tour operators), payout infrastructure is a separate problem from accepting payments.

Stripe Connect: Stripe's marketplace/platform product. Allows you to accept payments from customers and route portions to connected accounts (suppliers). Works well for marketplace businesses where both buyers and sellers are onboarded to your platform.

Wise Payouts API: For paying suppliers or partners in bulk to international bank accounts. Transparent FX rates, wide country coverage, API-first.

Airwallex Payouts: Similar capability, often better rates for high-volume cross-border payouts.

SWIFT transfers: Standard international bank transfers, available through any business bank account. High per-transaction fees (£15–35), slow (2–5 days), but universally supported and required for some destinations.

Tax and Compliance at Scale

When your business operates across jurisdictions, the tax compliance picture expands significantly:

VAT on digital services (EU): EU VAT OSS (One Stop Shop) allows you to file a single VAT return covering all EU sales, rather than registering in each country separately. If you're selling digital services to EU consumers, you need to either register for VAT OSS or use a Merchant of Record platform.

US sales tax: If you have nexus in US states (physical presence, employees, or sufficient economic activity), you may owe state sales tax. TaxJar and Avalara automate US sales tax calculation and filing.

VAT number validation (B2B EU): B2B sales between EU businesses are zero-rated if the buyer provides a valid VAT number. Validate VAT numbers through the VIES database before applying zero-rating.

The general principle: as you expand internationally, tax compliance becomes a real operational burden. Either invest in accounting infrastructure that handles it correctly or use MoR platforms (Paddle, Lemon Squeezy) that absorb it for digital products.

The Payment Infrastructure Stack

A mature payment stack for a multi-market digital business looks something like:

Stripe (primary card processing, EU/UK/US)
Wise Business (multi-currency accounts, receiving international transfers, supplier payments)
Local payment methods through Stripe Checkout or a regional gateway
Spreedly or similar if running multiple gateways
Paddle or similar MoR if selling to global consumers (handles VAT)
Airwallex for high-volume cross-border payouts at competitive rates

No single provider does everything well. The stack is assembled from best-in-class tools for each function. The integration overhead is real — budget for it.