How to send cross-border payments with stablecoins

Cross-border payments do not have a single problem. They have a dispersion problem. 

The FSB's 2025 progress report found that average global retail cross-border payment costs remained sticky, with peer-to-peer transfers running at roughly 2.5% and receiver-side costs adding another 0.1–1.3% of the amount sent. The World Bank's Remittance Prices Worldwide data puts the global average cost of sending $200 at 6.36%. The dispersion across corridors, provider types, and funding methods is wider than any single average suggests. 

Stablecoin payments do not replace cross-border banking. They are the rail that wins on specific dimensions — cost in lower-volume corridors, FX transparency, programmability, and emerging-market reach — while complementing existing rails on others.

What are cross-border payments?

A cross-border payment is any transfer of value between parties in different countries or currencies. The legacy rails include correspondent banking (SWIFT messaging plus a chain of banks holding nostro accounts in each currency), card networks (Visa, Mastercard, settlement T+1 or T+2), and a layer of fintech APIs that wrap one of the first two.

The performance characteristics vary widely. SWIFT gpi (live since 2017) credits nearly 60% of payments to end beneficiaries within 30 minutes and almost 100% within 24 hours, and many institutional flows now run on prefunded nostro relationships that are same-day. 

The cost and timing story for cross-border has moved; the friction has migrated.

Where the friction actually sits today

Modern correspondent banking is fast for institutional G7 flows. The friction has shifted to other dimensions:

• FX cost. The FSB explicitly identifies FX as the largest component of total retail cross-border payment costs. Faster rails have not made the FX spread more transparent.
• Lower-volume corridors. SWIFT gpi coverage is uneven across emerging markets; settlement times and cost stay high outside the major G7 routes.
• Retail and SME flows. World Bank RPW Q3 2025 shows banks averaging 14.99% on retail remittance, MTOs at 4.72%, with funding method making a major difference (bank-account-funded at 8.69%, card-funded at 4.39%, mobile money at 5.29%).
• Receiver-side delivery. Even when network-level processing is fast, beneficiary credit timing depends on local payout method, bank hours, and compliance review.

The aggregate picture: rails are faster than they used to be at the network layer, but the end-user cost and timing experience still varies widely by corridor and method.

How stablecoins fit

Stablecoin payments route value directly between sender and recipient over a blockchain network. There is no correspondent chain, no per-leg fee stack, no FX spread embedded in a quoted rate that diverges from the settlement rate.

On Polygon specifically, a stablecoin transfer costs $0.002, settles in approximately 5 seconds , and is verifiable onchain. As part of the Open Money Stack, we’re building the all-in-one API that brings stablecoin settlement, on-/off fiat ramps, wallet infrastructure, and build-your-own blockchain. Everything in a vertically integrated platform. 

The cost and FX become legible: the onchain fee is published, the FX conversion (if any) happens at a quoted rate at the moment of off-ramp, and the settlement event is independently auditable.

Stablecoins beat the legacy stack most cleanly on:

• Lower-volume and emerging-market corridors where gpi coverage is thin
• FX transparency because the spread is observable at the off-ramp, not hidden in correspondent bank rates
• Per-transaction economics at smaller ticket sizes, where the fixed cost of a wire is uneconomic
• Programmability — conditional payments, escrow, milestone-based release encoded onchain
• Receiver-side reach through licensed off-ramps in geographies with weak retail banking

They do not beat SWIFT gpi on speed for institutional G7 wires. The right framing is portfolio: use the rail that wins on the corridor you have.

Use cases

• Vendor payments in emerging-market corridors. A US manufacturer pays a Vietnam supplier in USDC. The supplier converts to VND through a licensed local partner at a quoted rate.
• Contractor payouts at scale. A SaaS company pays 200 contractors across 40 countries in stablecoins. The platform does not need a banking relationship in every recipient country.
• Lower-ticket B2B. Cross-border invoices under $10K where wire fixed costs dominate.
• Remittances. The most expensive segment of cross-border today. World Bank RPW Q3 2025: 6.36% average for $200. Stablecoin-rail remittances through licensed off-ramps run materially below this baseline, though the realized cost varies by corridor and disbursement method.

CASE STUDY: Paxos. Over $1.3B in volume on Polygon, 50x monthly growth in under 12 months, more than 82,000 transactions, less than $700 in total gas fees, estimated 99.998% reduction versus card-network interchange.

How to get started

A cross-border pilot on Polygon usually runs one to four weeks depending on the corridor and the compliance setup:

1. Pick one corridor. US-to-Mexico, US-to-Brazil, US-to-Philippines, and EU-to-Africa are common starting corridors because gpi coverage is weaker and the cost delta is largest.
2. Choose your on/off-ramps. Coinme operates a US-licensed network of cash-pickup and bank-rail access points; partners integrate for additional corridors. The OMS routes through the appropriate ramp without requiring separate per-partner integrations.
3. Run a small batch. $50K–$100K of monthly volume through the new corridor while the existing rail runs in parallel.
4. Measure realized cost and settlement timing. End-to-end, including the off-ramp leg. Compare against your current rail's actual numbers for the same corridor.
5. Scale to additional corridors. Once one corridor proves out, the second adds in days, not weeks.

Why Polygon for cross-border payments

Three reasons specific to this use case:

• Production track record. Polygon has cleared $2.4T in cumulative stablecoin transfer volume [VERIFY: latest cumulative figure]. The chain has handled treasury-scale flow at production reliability.
• OMS handles the routing. OMS contains an intent-based orchestration layer. A payer states the desired outcome (send X to Y); OMS picks the optimal token, chain, and route. The quickstart widget integration is documented at under 5 minutes; production deployment includes the usual product, compliance, QA, and operational work.
• The stack is open and vertically integrated. Wallets, blockchain settlement, ramps, cross-chain liquidity and orchestration, and build-your-own chain are all part of the OMS, designed to compose. Each layer can be replaced or operated independently. The architecture is open; the integration is unified.

Why this matters for finance teams

For a CFO evaluating cross-border cost reduction, the conversation moves past the false binary of “stablecoins replace wires.” 

The right framing is portfolio optimization: keep wires where they win (institutional G7), add stablecoins where they win (emerging corridors, lower tickets, programmable flows, transparent FX). A treasury moving $50M in cross-border flow can typically find 30–60% of that volume sitting in corridors and ticket-size bands where stablecoin rails outperform on both cost and timing.

The reporting becomes legible: per-corridor cost, per-corridor settlement time, per-corridor success rate. That is a defensible quarterly review line rather than a vague modernization claim.

Disclaimer

This post is for general informational purposes only and does not constitute legal, financial, tax, regulatory, or investment advice. Nothing contained herein should be construed as a solicitation, offer, or recommendation to buy, sell, or engage with any product, service, or asset, nor should it be relied upon as the basis for any decision.

Users and institutions are solely responsible for ensuring that their access to and use of any Polygon product or service complies with all applicable laws, rules, and regulations in their respective jurisdictions, including those governing payments, money transmission, foreign exchange, sanctions, the Travel Rule, and anti-money-laundering obligations. Polygon Labs makes no representation or warranty that any particular corridor, configuration, feature, or use case will satisfy the legal or regulatory requirements of any specific jurisdiction. Users and institutions are strongly encouraged to seek independent legal counsel regarding their specific compliance obligations before engaging with any Polygon product or service.

The features, corridors, cost figures, settlement times, and illustrative examples described in this post are provided for illustration only, are subject to applicable law, and may not be available in all jurisdictions. Realized costs, settlement times, foreign-exchange rates, and recipient outcomes depend on the corridor, the chosen on-ramp and off-ramp, third-party partners, funding method, and other factors, and may differ materially from any figures referenced herein. Comparisons to other payment rails, including SWIFT and card networks, are illustrative and corridor-specific. All statements regarding future products, features, functionalities, or capabilities are forward-looking in nature and subject to change without notice, and should not be relied upon as representations of future performance or availability.

Polygon Labs reserves the right, in its sole discretion and without prior notice, to modify, suspend, limit, restrict, or discontinue any program or any component of the Open Money Stack ("OMS"), in whole or in part, at any time. Use of OMS is subject to the OMS terms and conditions. On-ramp, off-ramp, foreign-exchange, custody, and fiat-disbursement services may be provided by independent third parties subject to their own terms; Polygon Labs does not control and is not responsible for such services. Polygon Labs further reserves the right to restrict or terminate access to any code, feature, or support for any user or in any jurisdiction where required by applicable legal or regulatory obligations.

Blockchain technology, smart contracts, stablecoins, and decentralized protocols involve inherent and significant risks, including but not limited to technical vulnerabilities, regulatory uncertainty, foreign-exchange and liquidity risk, stablecoin de-pegging or issuer risk, and potential loss of funds. To the fullest extent permitted by applicable law, Polygon Labs shall not be liable for any damages of any kind arising from or in connection with the use of, or reliance upon, any program, the Open Money Stack, or any information contained in this post.