Selling software internationally sounds like flipping a switch. In practice, every payment crosses banking networks, risk systems, currencies, and tax regimes — and each layer is a place revenue can leak. A checkout that converts in your home market can quietly lose a fifth or more of its international attempts to declines and abandonment that never show up as errors in your own logs. This guide explains how a global payment actually works, end to end, and where to focus to get more of them through.

The anatomy of a global payment

A single card transaction looks instant to the customer, but behind the spinner it passes through five or six parties in under two seconds. Understanding who they are makes every later problem — declines, fees, currency surprises — legible.

The authorization path runs like this:

1. Cardholder enters card details (or taps a wallet) at checkout and submits.
2. Merchant — your site, or the platform acting on your behalf — packages the request and sends it on. It never sees the raw card if tokenization is done right.
3. Acquirer (the merchant's payment processor or acquiring bank) receives the request and routes it into the card networks.
4. Card network — Visa, Mastercard — acts as the switchboard: it identifies the issuing bank from the card number and forwards the authorization request.
5. Issuer (the cardholder's bank) makes the real decision. It checks the balance or credit line, runs fraud and risk scoring, applies any 3D Secure rules, and returns an approve or decline.
6. Response travels back along the same chain — issuer → network → acquirer → merchant → cardholder — carrying either a success or a coded decline reason.

Authorization only reserves the funds. Money does not actually move yet. Later, capture tells the issuer to commit the held amount, and later still settlement and clearing is the batch process where the networks and banks reconcile and the funds flow from issuer to acquirer to the merchant's account, minus fees. Domestically this entire dance is invisible and reliable. Across borders, every hop adds latency, cost, and a fresh reason to say no.

Why payments fail abroad

International transactions are declined more often than domestic ones, and most of those declines are recoverable rather than genuine "no money" rejections. The reasons cluster into a few buckets.

Soft vs. hard declines. A soft decline is temporary — a bank security hold, an issuer time-out, a network error, a velocity throttle from too many attempts. The same card will often succeed on a retry once the bank's caution clears, with the customer doing nothing. A hard decline is permanent at the current state — a lost, stolen, frozen, or expired card, or a definitive fraud block — and no amount of retrying helps until the customer switches cards or fixes their input. Telling these apart is the single most important decision in payment recovery; retrying a hard decline on a fixed schedule just burns attempts and can add fraud signals.

Common decline reasons on cross-border traffic:

• Foreign-issuer caution — the issuer scores an unfamiliar overseas merchant as higher risk and declines or holds it.
• Insufficient funds or over a limit — sometimes transient (recovers after payday), sometimes not.
• AVS / billing-address mismatch — address checks fail more often when formats differ by country.
• 3D Secure not completed — the customer abandoned or failed the authentication step.
• Suspected duplicate — the bank blocks what it thinks is a repeat charge.
• Do-not-honor — a generic issuer decline with no stated reason, often recoverable on a timed retry.

3D Secure 2, SCA, and PSD2 friction. In Europe, PSD2 mandates Strong Customer Authentication (SCA) for most online card payments, and 3D Secure 2 (3DS2) is the technical layer that delivers it. Done well, 3DS2 authenticates the cardholder silently in the background (frictionless flow) or with a quick app approval or one-time code, raising approval rates and shifting fraud liability to the issuer. Done badly — a clunky redirect, a slow OTP, a broken mobile flow — it becomes a step customers simply abandon. A clean 3DS implementation is one of the highest-leverage levers on international acceptance, not a tax to be avoided.

For the full decline taxonomy — soft vs. hard, the specific failure groups, and exactly which retries recover revenue — see Why Payments Fail →

Levers to raise acceptance

Acceptance is not luck; it is a stack of well-understood techniques. The biggest gains on cross-border traffic come from these.

• Local acquiring. Routing a transaction through an acquirer in the customer's region makes it look domestic to the issuer — matching country codes, familiar routing, lower fraud scoring — which lifts approval rates and often lowers fees versus a single far-away acquirer.
• Intelligent retries and dunning timing. Retry soft declines, not hard ones, and time them to when bank holds and velocity throttles reset rather than hammering immediately. For subscriptions, this is dunning: an automatic retry-and-notify sequence that recovers failed renewals before the subscription lapses.
• Network tokens. Replacing the raw card number with a network-issued token (from Visa or Mastercard) improves authorization rates and keeps credentials current as cards are reissued.
• Card account updater. When a customer's card is reissued with a new number or expiry, account-updater services refresh the stored credential automatically, preventing avoidable expiry declines on recurring charges.
• Method localization. Offering the payment methods a market actually uses — not just the ones your home market uses — reduces abandonment before authorization even begins.

Payment-method localization by region

This is industry context, not a feature list — but it explains why a cards-only checkout underperforms in some markets. Buyer preferences are strongly regional:

• North America — credit and debit cards dominate, with Apple Pay and Google Pay rising fast in mobile checkout.
• Europe — cards are common, but bank-transfer rails like SEPA and country wallets matter; the Netherlands skews heavily to iDEAL, Germany to bank transfer.
• Latin America — installment card plans are expected, and account-to-account rails like Brazil's PIX have become a default for a large share of buyers.
• China — mobile wallets such as Alipay and WeChat Pay lead overwhelmingly, with cards a minority for domestic spend.
• Southeast Asia, Africa, and parts of Asia — local wallets, QR schemes, and even mobile-money balances carry significant volume.

The practical takeaway is to match your method mix to where your customers actually are, rather than assuming the world checks out the way your home market does.

Presentment vs. settlement currency, and FX

Two currencies matter in any cross-border sale, and conflating them is a classic source of confusion.

• Presentment currency is what the customer sees and is charged at checkout. Showing prices in the buyer's local presentment currency — €19 instead of "$20 plus whatever my bank charges" — measurably lifts conversion, because the amount feels native and predictable.
• Settlement currency is what actually lands in your account after processing.

When the two differ, a foreign-exchange (FX) conversion happens in between. That conversion carries an FX margin, and the transaction may also incur cross-border / international fees that networks and acquirers apply when the card's country and the merchant's country don't match. None of this is visible to the buyer, but it directly affects your net revenue. The levers are: price in local currency to win the sale, understand which fees apply on the corridor, and know the rate at which your provider settles back to you.

Tax and settlement: the hidden half

Getting the payment approved is only half the job. The other half — tax and settlement — is where international selling gets genuinely hard, and where most software teams underestimate the work.

With a plain payment gateway, you are the merchant of record. That means you are responsible for figuring out where you have a tax obligation (VAT in the EU and UK, GST in several countries, US sales tax by state, consumption tax in Japan, and dozens more), registering in each, charging the correct rate at checkout, filing returns, and remitting what you collected — per jurisdiction, on each jurisdiction's schedule. For a small team selling into many countries, that is a real and growing operational burden that has nothing to do with your product.

A Merchant of Record (MoR) changes the structure. The MoR becomes the legal seller on the transaction. It calculates and collects the right tax at checkout, files and remits across the countries it covers, and settles net revenue back to you. The tax obligation, and the chargeback and fraud liability that ride on each charge, sit with the MoR rather than your account. That is the single biggest reason software businesses adopt the model when they go global.

With Waffo Pancake as your MoR, you accept Visa and Mastercard, Apple Pay, and Google Pay across 173 countries, with 3D Secure handled inside the flow and tax handled for you. The two-step checkout collects email, country, and billing details first — for tax and order processing — then takes payment, and renders in English, Chinese (Simplified), and Japanese. Pricing is 3.9% + $0.50 per successful transaction, with no monthly or setup fees. Payouts are currently in CNY (to a mainland-China bank card or Alipay), with more corridors on the roadmap.

A practical acceptance checklist

If you are setting up — or auditing — global payments, work through these in order:

1. Show local presentment currency wherever you can; price feels native and converts better.
2. Localize the checkout language to the buyer, not just your home market.
3. Offer the methods your customers actually use — at minimum cards plus Apple Pay and Google Pay, which span most geographies.
4. Implement a clean, frictionless 3D Secure 2 flow so SCA helps rather than hurts approvals.
5. Use network tokens and a card account updater so reissued cards keep working on recurring charges.
6. Route through local acquiring where your volume justifies it, to look domestic to issuers.
7. Classify declines and retry only the recoverable ones, timed to when bank holds reset — automate this as dunning for subscriptions.
8. Decide who owns tax and settlement before you scale: do it yourself per jurisdiction, or hand it to a Merchant of Record.

Get the first half right and more customers reach a successful authorization. Get the second half right and that approved revenue actually lands in your account, clean of tax and compliance overhead. A global payment is only "done" when both halves are.

This article is general information, not tax, legal, or financial advice. Tax rates and rules change; verify current requirements with the relevant authority or a qualified advisor before acting.

Related articles

Payments

Why Payments Fail: A Field Guide to Declines and Recovery (2026)

Payments

SWIFT vs IBAN: How International Bank Transfers Actually Work

Payments

ACH Payments 101: Lower Fees for B2B Transactions