Cross-Border Payments Are Not All the Same

Most payment gateway comparisons focus on domestic transactions. Processing a credit card in the same country as your business is a fairly solved problem — fees are predictable, settlement is fast, and chargebacks work the same way everywhere.

Cross-border payments are a different animal. When a customer in Brazil pays a business in the UK, you have at minimum two currencies involved, potentially two regulatory regimes, additional fraud risk, and currency conversion happening somewhere in the chain. Where and how that conversion happens determines who profits from it — and by how much.

The Questions Worth Asking Before You Commit

Before evaluating any specific gateway, get clear on your requirements. What currencies do your customers want to pay in? What currency do you want to receive your settlements in? How important is real-time settlement versus waiting a few days? Do you need to support local payment methods in specific markets, or is international card processing sufficient?

These questions reveal whether you need a full cross-border payments solution or just a gateway with good international card acceptance.

Currency Support: More Than Just Displaying Prices

There is a meaningful difference between a gateway that "supports" a currency and one that actually processes payments in that currency end-to-end. Some gateways display prices in local currencies but convert everything to USD at checkout. Others process the transaction in the customer's currency and settle to you in your currency.

The distinction matters for customer experience — customers see a familiar currency — and for your exchange costs. When conversion happens at the gateway level, the gateway applies its own exchange rate, which includes a margin. Understanding where in the flow the conversion happens helps you calculate your true cost per transaction.

The difference between a 0.5% FX fee and a 2% FX fee on $1 million in annual cross-border revenue is $15,000. It is worth understanding exactly what rate you are getting.

FX Fees and Spread: What You're Actually Paying

Payment gateways typically make money on cross-border transactions in two ways: a percentage fee applied to the transaction, and a spread on the exchange rate. The spread is often less visible than the percentage fee but can be larger.

The spot rate — the real mid-market rate available from financial data providers like TheCurrencyAPI.com — is the baseline. Gateways apply a markup above this rate, typically 0.5% to 3% depending on the provider and your pricing tier. Some gateways are transparent about this; others bury it in the exchange rate they display.

If you process meaningful cross-border volume, ask your gateway explicitly: what is your exchange rate based on, and what is your markup? Compare their effective rate against the mid-market rate on the day of a real transaction to see what you are actually paying.

Settlement Currencies and Timing

In what currency will you receive your money? Most gateways default to settling in your home currency, but some allow you to hold balances in multiple currencies and convert at a time of your choosing. If you also have expenses in foreign currencies, being able to hold foreign currency balances can save you on conversion costs.

Settlement timing also varies. Some gateways settle daily, others in two to three business days. For cash flow-sensitive businesses, faster settlement can matter more than the absolute fee level.

Local Payment Methods

International card processing works well in North America, Western Europe, and Australia. In many other markets, it does not. In the Netherlands, iDEAL dominates online payments. In Germany, Sofort and direct debit are widely used. Brazil has Pix and boleto. China has Alipay and WeChat Pay.

If your market research shows that you have meaningful traffic from markets with strong local payment preferences, a gateway that only supports Visa and Mastercard will leave significant revenue on the table. Stripe, Adyen, and PayU are among the providers with broad local payment method coverage, though the specifics vary by market and pricing tier.

Fraud and Chargeback Risk

Cross-border transactions carry higher fraud risk than domestic ones, and chargebacks from international customers can be harder to dispute. The quality of a gateway's fraud detection tools is more important for cross-border merchants than for domestic-only sellers.

Look at what fraud tools are included versus add-on charges. 3D Secure support is important for European markets where it is increasingly mandatory. Some gateways offer chargeback insurance or guaranteed payments for an additional fee — worth evaluating if you have high-value or high-risk product categories.

Regulatory Considerations

Depending on where your business is incorporated and where your customers are located, you may have regulatory requirements around cross-border payments. PSD2 in Europe, for example, requires strong customer authentication for most card payments. Different rules apply in different markets.

Working with a large, established gateway generally means they handle the regulatory complexity for you. If you are entering a new market with unfamiliar rules, check that your gateway is properly licensed there before assuming it works.

Making the Decision

For most businesses processing cross-border payments, the choice comes down to Stripe or Adyen for mature markets with international card acceptance, or a more specialist provider if you need local payment methods in specific regions. Stripe's documentation and developer experience are hard to beat. Adyen's enterprise-grade infrastructure and coverage are worth the complexity for high-volume merchants.

Whatever you choose, build a layer of transparency around exchange rates for your customers. Showing the rate used at checkout, alongside a reference to a live rate from an independent source, demonstrates fairness and reduces disputes. For that reference rate, TheCurrencyAPI.com gives you a clean, independent mid-market rate you can surface directly in your UI.