B2B cross-border payments: Rails, costs, and how to choose

B2B cross-border payments reached $31.7 trillion in 2024 and are forecast to hit $47.8 trillion by 2032. Most of that volume still clears through correspondent banking built in the 1970s: settlement in days, fees that resist auditing, and pre-funding requirements that scale linearly with volume.

If you run payments at a fintech, PSP, or platform, you already know the pain points. The useful questions are which settlement model fits which corridor, what each one actually costs at your volume, and how to tell a provider with real local rail depth from one with a long country list and a SWIFT fallback. This guide covers all three.

What are B2B cross-border payments?

B2B cross-border payments are transfers between businesses in different countries, typically across different currencies and regulatory jurisdictions. They include supplier payments, platform and marketplace payouts, international payroll, intercompany treasury transfers, and PSP-to-PSP settlement.

They differ from consumer transfers in three ways that affect infrastructure decisions:

• Transaction size: average values are far higher, so FX spread dominates fixed fees as the main cost driver
• Compliance scope: KYB, beneficial ownership disclosure, and transaction reporting apply on top of standard KYC and sanctions screening
• Settlement stakes: a delayed payroll run or supplier payment has direct operational consequences, not just a support ticket

How B2B cross-border payments work: 3 settlement models

Three infrastructure models carry the majority of global B2B cross-border volume. Each solves the same problem, moving value between banking systems that do not interoperate, with different trade-offs on speed, cost, and capital.

1. Correspondent banking (SWIFT)

SWIFT is the messaging network behind most international bank-to-bank payments. The payment hops through a chain of correspondent banks, each holding accounts with the next, until it reaches the destination. Each intermediary deducts its own fee before passing the balance forward, which is why recipients often receive less than the sent amount with no clear breakdown.

Settlement runs one to five business days. SWIFT remains unmatched on reach (roughly 200 countries) and stays the default for high-value, low-frequency institutional transfers and for corridors with no alternative. At high transaction frequency or in time-sensitive flows, its cost and capital profile breaks down.

2. Local payment rails

Most major economies now run real-time domestic rails: PIX in Brazil, SEPA Instant in the eurozone, SPEI in Mexico, UPI/IMPS in India, Faster Payments in the UK. Once a payment clears the cross-border leg, the destination leg settles in seconds.

The constraint is access. Reaching a local rail from abroad requires a licensed, funded presence in that market, or a provider that has already built the connection. Rail coverage is the single biggest differentiator between providers, and the one hardest to verify from a website.

3. Stablecoin settlement

Stablecoin settlement routes the cross-border leg on-chain: fiat converts to USDC, USDT, or EURC at origination, moves across a blockchain in seconds, and converts back to local fiat at destination. The structure is commonly called the stablecoin sandwich.

The model removes the correspondent chain entirely. Capital sits only at the two conversion points instead of being distributed across pre-funded accounts in multiple jurisdictions, and settlement runs 24/7 with no dependence on banking hours.

The trade-offs are regulatory coverage at each conversion point and FX spread management. Multi-network support (Ethereum, Tron, Base, Solana) and multi-stablecoin support add routing flexibility.

For a direct cost comparison, see our article on stablecoin vs traditional FX.

Payment methods compared: speed, cost, coverage

No single method wins across every corridor and transaction profile. The table below summarizes how the main options stack up on the dimensions that drive routing decisions.

Most fintechs operating at scale route per corridor rather than picking one method: local rails where connected, stablecoin where fiat options are slow or absent, SWIFT where nothing else reaches.

Common use cases

Different commercial flows put different demands on the same infrastructure. Speed, currency coverage, and compliance weight vary across the five flows below, which is why corridor-level routing beats a one-method approach.

• International supplier payments. Invoice payments in the supplier's local currency, where payment timing affects commercial terms and FX transparency affects landed cost.
• Platform and marketplace payouts. High-frequency disbursements to merchants and sellers across many currencies on fixed schedules.
• International payroll and contractor payments. Recurring salary runs with hard deadlines and employment-related compliance obligations in each destination market.
• Treasury and intercompany transfers. High-value liquidity moves between legal entities, where documentation and FX execution quality outweigh speed.
• Remittance and wallet platforms. PSP-to-PSP settlement and platform-to-wallet payouts requiring broad corridor coverage and competitive retail-facing FX.

Key challenges (and what they cost)

Instant rails, stablecoin settlement, and API-first providers have improved the landscape without eliminating its structural problems. Four of them recur regardless of provider, and each carries a quantifiable cost.

Settlement speed is a working capital cost

Every day of settlement delay is capital locked in transit. A fintech moving $10M monthly through SWIFT-dependent corridors at a 3-day average window holds roughly $1.5M in pre-funded accounts at any moment (illustrative: $10M / 20 business days x 3 days). Shifting a corridor to instant settlement via local rails or stablecoin cuts that requirement by 80% or more. At $100M monthly volume, the freed capital exceeds $12M.

FX spread is the real price, and it hides in the rate

Banks and many providers embed markup in the quoted exchange rate rather than stating it in basis points, which makes provider comparison and margin modeling difficult by design. Competitive spreads run:

• Major pairs (EUR/USD, GBP/USD): 5 to 25 bps
• Emerging market and exotic pairs: 30 to 90 bps or more

At $10M monthly volume, the gap between 10 bps and 50 bps is $40,000 per month. At $100M, it is $400,000. Spread is a P&L line, not a procurement detail.

Compliance spans every jurisdiction you touch

Each corridor adds licensing and monitoring obligations: MSB registration, EMI or payment institution licenses, VASP registration for stablecoin legs, plus sanctions screening and transaction reporting. A provider settling funds on your behalf must hold valid authorization in every market where it does so; an unlicensed provider transfers its regulatory exposure to you. KYC and AML requirements extend in B2B to KYB and beneficial ownership verification.

Country counts overstate coverage

The questions that separate real coverage from a marketing number:

1. Which corridors settle via direct local rails, and which fall back to SWIFT?
2. Is settlement bidirectional (pay-in and payout) or payout-only?
3. Are virtual accounts available, so customers can receive locally without a foreign bank account?
4. What share of the provider's total volume clears through local rails?

A 60-country provider with deep local connections will outperform a 150-country provider routing most of those markets through SWIFT.

5 criteria to evaluate a b2b payment providers

Provider selection is an architectural decision with multi-year consequences for cost, capital, and coverage. These five criteria separate providers in practice, and every one of them can be verified before signing.

1. Rail depth per corridor. For each corridor you serve, get the specific rail (PIX, SEPA Instant, SPEI, UPI, M-Pesa, Faster Payments), direction (pay-in, payout, or both), transaction limits, and operating hours. SWIFT fallback does not count as local coverage.
2. Settlement architecture. Fiat-only, stablecoin-only, or multi-rail. Multi-rail routing (local rails where strong, stablecoin where fiat is weak, SWIFT where unavoidable) gives per-corridor cost optimization a single-model provider cannot.
3. FX pricing transparency. Request a rate card before integration, with spreads in basis points off mid-market, fixed vs volume-tiered pricing, and the model for high-volatility corridors (fixed spread vs request-for-quote). A provider that withholds the rate card until contract stage will not get more transparent after launch.
4. Compliance coverage. Get the license list with legal entities: MSB, EMI/PI, VASP registrations per market. Confirm where AML screening, sanctions checking, and KYC responsibility sit when your end users initiate transactions.
5. API quality and time to production. Documentation depth, sandbox access, webhook reliability for status updates, idempotency handling, and the realistic time from contract to first live transaction. For an integrating fintech, the payment API is the product surface.

Building your cross-border payment function with Due

Settlement architecture decided at integration determines working capital, corridor margins, and market reach for years afterward. The strongest providers are not those with the longest country lists but those with direct local rail depth in the corridors that carry your volume, basis-point-transparent FX, and licenses in every market they settle.

Due provides cross-border payment infrastructure for fintechs and neobanks, connecting local rails (PIX, SEPA Instant, SPEI, Faster Payments, UPI, M-Pesa, and more), SWIFT, and stablecoin networks across 80+ countries through a single API. See our corridor and coverage detail or speak to our team.

‍