International Payment Gateway: Accept and Pay Out Globally in Fiat or Stablecoins

Share this post Link copied

TL:DR

An international payment gateway in 2026 needs to do three things: accept payments broadly (cards, local methods, and stablecoins), optimize authorization rates through local acquiring (data shows 16-20% improvement on cross-border approvals), and pay out globally (SWIFT, local rails, or stablecoin settlement). The FX markup buried in the exchange rate often costs more than the headline processing fee. This guide provides an 8-point procurement scorecard for evaluating gateways on what actually drives revenue: approval rates, cost transparency, and payout speed.

Why the Gateway Category Is Being Redefined

For most of the last decade, an international payment gateway meant one thing: a hosted page or API that took a card number, routed it to an acquirer, and returned an approval or a decline. The provider that won was usually the one with the cleanest checkout and the lowest headline rate.

That definition is breaking down because the failures are converging. Cards decline at 15-25% on cross-border transactions when they clear at 1-5% domestically [1]. FX markup quietly erodes 1-3% of every converted transaction, buried in the exchange rate and never itemized [2]. Payouts to suppliers and sellers in emerging markets take days through correspondent banking and cost 3-7% all-in [3].

These used to be three separate vendors: a gateway for acceptance, a treasury operation for FX, and a payout provider for disbursement. The teams winning on cross-border conversion in 2026 have collapsed these into one system. They evaluate a gateway on three axes: how broadly it accepts, how well it optimizes authorization rates through local acquiring, and whether it can settle or pay out when banking rails are slow. Stablecoin settlement has emerged as a meaningful option on the third axis, with Visa, Mastercard, Stripe, and Circle all integrating stablecoin rails into their payment infrastructure in 2025-2026 [4].

Acceptance: Cards, Local Methods, and Stablecoins

The acceptance question used to be a coverage checklist: do you take Visa and Mastercard? Today it is a strategy question, because the right method differs by market and counterparty.

Region
Dominant Local Methods
Card Share
What to Offer
Southeast Asia
GrabPay, GCash, OVO, Dana, PromptPay, QR-based wallets
30-50%
Local wallets + cards. E-wallets dominate in PH, ID, TH.
Latin America
Pix (Brazil), OXXO (Mexico), Boleto, PSE (Colombia)
40-60%
Pix is mandatory in Brazil. Cash vouchers still large in MX.
Europe
iDEAL (NL), Bancontact (BE), SOFORT, SEPA Direct Debit
50-70%
Cards strong but country-specific methods lift conversion 10-20%.
India
UPI, Net Banking, Paytm, PhonePe
20-30%
UPI dominates. Gateway without UPI loses 70%+ of Indian buyers.
B2B (Global)
SWIFT, bank transfers, and increasingly stablecoins (USDC, USDT)
Varies
B2B counterparties holding stablecoins can pay directly, removing an FX round-trip.

Card share estimates are approximate and vary by sub-market and vertical. Stablecoin acceptance is primarily relevant for B2B flows where counterparties already hold digital dollars.

For consumer checkout, cards remain the backbone, but the gateway needs to present local methods where they dominate. A gateway that only offers international Visa and Mastercard in Brazil or India is leaving 50-70% of potential buyers without their preferred payment method.

For B2B flows, the calculus is different. Some counterparties, particularly in emerging markets, now hold digital dollars and prefer to settle in stablecoins rather than convert to a volatile local currency and back. EY's 2025 survey found cross-border payments to be the leading stablecoin use case at 77% of corporates surveyed [5]. A payment gateway that can accept a stablecoin payment alongside cards and bank transfers removes an entire FX round-trip for these counterparties.

Authorization Rate Optimization: The Biggest Revenue Lever

The single biggest lever most international merchants are not pulling is local acquiring.

The mechanic is straightforward. When a card issued in Germany is charged by a merchant acquired in the United States, the issuer sees a cross-border transaction and applies stricter fraud scoring. Route the same transaction through a local acquiring entity in the issuer's region and it reads as domestic, which materially raises the chance of approval.

The data on this is consistent across multiple sources. Solidgate reports that switching to local acquiring delivers an average lifetime value improvement of up to 17.9% across cross-border merchant corridors [6]. PayerMax data shows merchants using local acquiring see acceptance rates up to 16% higher than those relying on a single cross-border acquirer [7]. CoinLaw's 2026 analysis found local payment solutions minimize cross-border failures by 20% [1].

Cross-Border Acquiring
75-85%
typical approval rate
Issuer sees foreign acquirer. Higher risk score. Stricter fraud rules applied. 15-25% of legitimate transactions declined.
Local Acquiring
91-99%
typical approval rate
Issuer sees local acquirer. Domestic risk scoring. Transaction recognized as same-country. Up to 16-20% improvement.
On $200M annual volume, a 2-4% improvement in authorization = $4-8M recovered revenue

Sources: [1], [6], [7]. Approval rate ranges reflect typical B2C e-commerce. B2B rates vary.

The revenue at stake dwarfs the fee negotiation everyone fixates on. On $200 million of annual cross-border volume, a 2-4% improvement in authorization recovers $4-8 million per year. That is recovered revenue, not cost saved.

Buyers should ask any prospective gateway for corridor-level approval data, not a global blended number. The improvement from local acquiring is most pronounced in markets where domestic issuers have limited transaction history with international acquirers, particularly Brazil, Southeast Asia, and parts of Eastern Europe [6]. Treat unwillingness to share corridor-level data as a red flag.

The FX Markup Problem

The headline processing rate is the part of gateway pricing buyers understand. The FX markup is the part that quietly costs more.

When a customer pays in one currency and you settle in another, the conversion happens somewhere in the chain, and the spread applied is rarely disclosed on the invoice. A markup of 1-3% on the converted amount can exceed the entire processing fee, and because it is buried in the exchange rate rather than itemized, most finance teams never benchmark it.

Cost Layer
Typical Range
On Invoice?
Your Action
Interchange
0.3-2.0%
Usually
Benchmark by card type
Scheme fees
0.1-0.5%
Sometimes
Ask for breakdown
Cross-border / issuer fees
0.4-1.0%
Rarely
Request corridor detail
FX markup
1-3%
Almost never
Demand mid-market rate
Failed-payment retry cost
Hidden
Never
Track retry volume

FX markup and retry costs are the layers most often missing from buyer comparisons. The G20 roadmap lists FX disclosure among its transparency targets, and progress has been slow [2].

The G20 roadmap explicitly lists disclosure of FX rates and conversion charges among its transparency targets, and progress against those targets has been slow and uneven across jurisdictions [2]. Until disclosure is mandatory everywhere, the burden sits with the buyer to demand the mid-market reference rate alongside the rate actually applied, and to benchmark the FX markup on every corridor where volume is meaningful.

For payout flows where stablecoin settlement is used, the FX economics tighten significantly. The conversion cost of regulated stablecoins runs 0.1-0.5% all-in versus 2-7% for traditional correspondent banking [5], which is why some businesses use stablecoin settlement specifically on corridors where the FX markup through banking rails is widest.

Payout and Settlement: Completing the Loop

A gateway that only accepts is half a system. The funds you collect have to reach suppliers, sellers, and contractors, and for cross-border beneficiaries this is where days and dollars are lost.

Three payout rails are available in 2026, and a serious gateway evaluation weighs all three.

SWIFT payouts reach 70+ currencies globally. They are reliable and universally accepted by banks, but settlement takes 1-3 days and costs 2-7% all-in including intermediary fees and FX markup. SWIFT remains the default for large-value B2B transactions in well-served corridors.

Local rail payouts settle same-day (often within hours) in specific markets through domestic clearing systems: IMPS/NEFT in India, Pix in Brazil, CHATS in Hong Kong, PromptPay in Thailand. Costs are lower than SWIFT, but coverage is limited to the 15-25 countries where the provider has local banking partnerships.

Stablecoin settlement delivers funds to 170+ countries without traversing correspondent banking chains. The stablecoin sandwich model (fiat to stablecoin to fiat) settles in minutes at 0.1-0.5% total cost. This removes the prefunding that traditional cross-border payouts require, freeing working capital.

The industry momentum behind stablecoin settlement is substantial. Visa partnered with BVNK for stablecoin settlement. Mastercard integrated stablecoin capabilities. Stripe acquired Bridge for $1.1 billion in October 2024 to build stablecoin infrastructure. Circle launched the Circle Payments Network with 25+ partners [4]. Stablecoin on-chain volume reached $33 trillion in 2025, surpassing Visa and Mastercard's combined annual volume [4]. This is an industry-wide infrastructure shift, not a niche experiment.

For buyers, the practical question is whether your gateway treats payout as a first-class capability or an afterthought. A gateway that handles acceptance and payout on one reconciled ledger eliminates the multi-vendor reconciliation problem that most finance teams currently manage manually.

How to Evaluate: The 8-Point Gateway Scorecard

8-Point Gateway Evaluation Scorecard
1
Geographic card coverage
How many markets do you process cards in? Do you have local acquiring in my top 5 markets? Which card schemes beyond Visa/Mastercard?
2
Local payment method depth
Which APMs are supported per market? UPI in India? Pix in Brazil? GrabPay in SEA? Coverage list alone is not enough. Ask for live transaction volume per method.
3
Authorization rate data (corridor-level)
Demand approval rates by corridor, not a global blended number. What is the domestic vs cross-border split? What is the improvement from local acquiring? Unwillingness to share this is a red flag.
4
FX transparency
Can you show the mid-market reference rate alongside the rate applied? What is your spread per corridor? Will you contractually commit to a maximum markup?
5
Settlement options (fiat + stablecoin)
Can you settle to my bank account in my preferred currency? Can you settle in stablecoins where I or my counterparties prefer it? What stablecoins are supported (USDC, USDT)?
6
Payout capability and speed
Can you pay out to beneficiaries? SWIFT, local rails, stablecoin? What are actual settlement times by corridor? Is per-transaction funding available?
7
Licensing coverage
Does the provider hold payment licenses in the markets where you accept and pay out? If stablecoin services are offered, are they delivered through a separately licensed entity?
8
Reconciliation and reporting
Do acceptance and payout sit on one ledger? Is there webhook-based reconciliation? Can you access MT103 confirmations via API? One ledger vs two vendors changes the operational cost dramatically.

Compliance and Licensing: What to Verify

A gateway touching multiple currencies, methods, and stablecoins operates under multiple regulators. Three checks matter most.

First, confirm the licensing footprint covers the markets where you accept and pay out. Fiat payment services in a given jurisdiction require the relevant local authorization. Ask to see it rather than taking it on trust.

Second, confirm that any stablecoin activity is delivered through an entity actually permitted to provide digital asset services. A license that covers fiat payment services does not extend to stablecoin services. The two are frequently held by different legal entities within the same provider. For a full breakdown of how these licensing regimes work across the US, Canada, EU, Hong Kong, and Singapore, see our licensing landscape guide.

Third, confirm the provider's AML and KYB program scales to your counterparties, particularly if you onboard sub-merchants, sellers, or sub-entities at volume.

What the Gateway Decision Looks Like by Business Type

Business Type
Top Gateway Priority
Secondary Priority
Stablecoin Relevance
E-commerce
APM coverage + local acquiring. Maximize conversion.
FX transparency on settlement
Low (consumer checkout is fiat)
B2B Trade
FX transparency + payout speed. Protect margins.
Settlement options (fiat + stablecoin)
High (accept + pay out in stablecoin)
Marketplace
Acceptance + payout on one ledger. One reconciliation.
APM depth in seller markets
Medium (payout to EM sellers)
SaaS / Subscriptions
Retry logic + account updater. Minimize involuntary churn.
Local acquiring for recurring auth
Low (recurring fiat billing)

Where Tazapay Fits

Tazapay operates as a payment infrastructure with  international payment gateway for acceptance, and payout capability built into a single integration.

Key capabilities relevant to this guide: accept payments from 173+ countries via cards, local payment methods, bank transfers, and stablecoins; local acquiring in key markets to lift cross-border authorization rates; SWIFT payouts in 100+ currencies plus local rail payouts in India, Brazil, Philippines, Hong Kong, Thailand, Indonesia, Singapore, Malaysia, UAE, and 80+ additional markets; stablecoin settlement via USDC/USDT through Tazapay Canada Corp for corridors where banking rails are slow; named virtual accounts for collection in 35+ currencies; and one reconciled ledger for both acceptance and payout.

Sources

[1] CoinLaw. "Card Decline Statistics 2026: Secrets to Higher Approval Rates." April 2026. https://coinlaw.io/card-decline-statistics/

[2] G20 Cross-Border Payments Roadmap. Priority Theme 2: Transparency. Progress Report 2025.

[3] World Bank. Remittance Prices Worldwide, Q3 2025. https://remittanceprices.worldbank.org/

[4] Bessemer Venture Partners. "Stablecoins: From DeFi Primitive to Global Financial Infrastructure." April 2026. https://www.bvp.com/atlas/stablecoins-from-defi-primitive-to-global-financial-infrastructure

[5] EY-Parthenon. "Cost Savings and Speed Drive Stablecoin Adoption." 2025. https://www.ey.com/en_us/insights/financial-services/cost-savings-and-speed-drive-stablecoin-adoption

[6] Solidgate. "Authorization Rate Optimization: The 2026 Playbook." April 2026. https://solidgate.com/blog/authorization-rate-optimization/

[7] PayerMax. "Local Acquiring Model in Cross-Border Payment Solutions." 2025. https://www.payermax.com/article/knowledge/yuftet9xz8tkt5asiek1j95s

[8] Stripe. "Local Acquiring 101: A Global Approach to Payments." https://stripe.com/resources/more/local-acquiring-101

[9] The Digital Banker. "The Stablecoin Revolution Is Reshaping Business Payments." May 2026. https://thedigitalbanker.com/the-stablecoin-revolution-is-reshaping-business-payments/

General Advice Warning

Stablecoin-related services are provided exclusively by Tazapay Canada Corp, a FINTRAC-registered Money Services Business. Tazapay Pte. Ltd. (Singapore) does not provide Digital Payment Token services under the Payment Services Act 2019.

Share this post Link copied

Frequently Asked Questions

What approval rate improvement should I expect from local acquiring?

Multiple data sources show 16-20% improvement in cross-border approval rates when switching from a single cross-border acquirer to local acquiring. Solidgate reports up to 17.9% LTV improvement across cross-border corridors. The effect is strongest in markets where domestic issuers have limited history with international acquirers, particularly Brazil, Southeast Asia, and Eastern Europe. Ask your gateway for corridor-level data, not a global blended number.

Can a payment gateway accept stablecoins alongside cards and bank transfers?

Yes. Modern gateways can accept stablecoins (USDC, USDT) as a payment method alongside cards and local methods, particularly for B2B flows where the counterparty holds digital dollars. This removes an FX round-trip since the payer does not need to convert stablecoins to fiat before paying, and the gateway can hold or convert at destination. This is most relevant for B2B trade, not consumer e-commerce.

Do I need a single gateway or multiple gateways for global coverage?

The answer depends on your volume distribution. If you have concentrated volume in 3-5 markets, a single gateway with strong local acquiring in those markets is usually better for reconciliation and operational simplicity. If you have thin volume across 30+ markets, a single global gateway avoids the complexity of managing multiple provider relationships. The worst outcome is multiple gateways without a clear routing strategy, which creates reconciliation overhead without meaningful approval rate gains.

How does stablecoin payout through a gateway work?

The gateway converts collected fiat (or stablecoin) into USDC or USDT, sends it to an off-ramp provider in the beneficiary's country, and the off-ramp converts to local fiat for delivery. The beneficiary receives local currency in their bank account. This is the stablecoin sandwich model, and it settles in minutes versus 1-5 days for SWIFT. For a detailed breakdown, see our stablecoin sandwich guide.

In this article