2025 in Review: A Year of Real Payments Usage on Polygon

The challenges of traditional cross-border payment systems (e.g., SWIFT) show up in every CFO dashboard: unpredictable settlement times, opaque fees, and operational overhead across corridors. As cross-border volumes are projected to exceed $250 trillion by 2027, enterprises are under pressure to modernize how value moves internationally, without compromising compliance or control.

Business benefits of modern cross-border payment systems

Cross-border payments are transactions where payer and recipient are in different countries. They span B2B, B2C, C2B, and P2P flows, but the enterprise pain points are consistent: currency conversion, multiple intermediaries, and layered compliance checks.

Modern cross-border systems change the economics and the operating model in four practical ways:

• Faster settlement and more predictable cash flow: When settlement is measured in seconds or minutes instead of days, treasury teams can reduce buffers and improve working capital planning.
• More control over FX outcomes: Access to live rates, multicurrency balances, and programmable conversion timing supports corridor-specific pricing and hedging strategies.
• Cleaner reconciliation and faster close: Real-time status updates, consistent reference data, and explicit fee breakdowns reduce exception handling ("why did the beneficiary receive less?").
• Operational scalability: Automating routing, screening, and payout workflows allows payment volume to grow without linear headcount growth in finance ops.

How SWIFT and correspondent banking work, and where the friction remains

SWIFT is a global messaging network that transmits payment instructions between banks; it does not move money itself. When the sending and receiving banks lack a direct relationship, payments route through correspondent banks.

SWIFT gpi (Global Payments Innovation), launched in 2017 and now effectively mandatory across the SWIFT network, has significantly improved the speed and visibility of this process. According to SWIFT's own data, 90% of gpi payments now reach the beneficiary bank within one hour, and the BIS has found a median processing time of under two hours. On high-volume corridors like the US to Singapore, same-day settlement is the norm during overlapping business hours. gpi also introduced end-to-end tracking (via a Unique End-to-End Transaction Reference on every payment) and requires banks to confirm credit status to a central tracker giving senders real-time visibility into where a payment is in the chain.

However, gpi is a transparency and tracking layer on top of the existing correspondent banking model, not a replacement for it. The underlying architecture is unchanged: funds still move through intermediary banks' nostro/vostro accounts, and each intermediary can still introduce:

• Additional fees: lifting fees, handling fees, FX spreads applied at the intermediary's discretion
• Additional checks: sanctions screening, AML monitoring, local rule validation
• Operational delays driven by banking cutoff times: the daily deadlines after which a bank will not process outgoing wires until the next business day, as well as manual investigations and repair queues
• Data degradation: field truncation or format changes across systems

Critically, gpi improved fee visibility but not fee reduction. Banks can now see what each intermediary charged after the fact, but there is no binding upfront fee quote and no mechanism to prevent unfavorable FX conversions by intermediary banks. SWIFT estimates that 35% of the cost of an international payment relates to nostro-vostro reconciliation and trapped liquidity, capital that banks must park in foreign accounts around the world. gpi cannot address this; it is inherent to the architecture.

There is also a meaningful gap between funds reaching the beneficiary bank (fast, under gpi) and funds being credited to the end customer's account (slower). Globally, only about 43% of gpi payments reach the end customer within one hour. And settlement still pauses entirely on weekends and holidays.

Card networks also power a meaningful share of cross-border activity. In that model, the issuer typically performs FX conversion and passes costs to businesses via cross-border and conversion fees. The result is often speed at the point of authorization, but less transparency and control over total cost and settlement behavior.

New technologies enabling faster payments (APIs, real-time networks, blockchain)

The industry's faster cross-border story is not one technology, it's a stack. Enterprises increasingly combine multiple rails based on corridor, value, urgency, and compliance profile.

Real-time payment networks (and cross-border links)

Many countries now operate instant domestic payment systems. Where these systems can connect across borders, payments can avoid batch schedules and some time-zone-driven delays.

Key limitation: Cross-network interoperability is uneven, and operating rules still vary by jurisdiction.

Digital wallets and regional clearing systems (e.g., SEPA)

Regional schemes and shared-rule environments can reduce cost and complexity within defined markets. SEPA is a common example for euro-denominated transfers.

Key limitation: Coverage is regional by design; global reach requires additional rails.

API-based payments infrastructure

APIs allow banks, fintechs, FX providers, and payment platforms to exchange instructions and status in real time rather than via batch files and manual handoffs.

What APIs change operationally:

• Automated routing decisions (fastest vs. lowest cost vs. highest certainty)
• Programmatic tracking and exception handling
• Automated reconciliation using stable identifiers and structured metadata

Blockchain and stablecoin-based settlement (24/7 value transfer)

Blockchain networks can move value without relying on chains of correspondent banks. Stablecoins, digital assets designed to track fiat value, are increasingly used for cross-border settlement because they can support near-instant transfer and 24/7/365 availability.

Where stablecoins tend to help most:

• After-hours and weekend settlement, where SWIFT gpi cannot operate because the underlying banking infrastructure is closed
• Corridors with high intermediary costs or opaque FX markups, where gpi has improved visibility into the problem but not eliminated it
• Use cases that benefit from atomicity (e.g., delivery-versus-payment style workflows)

What to be clear about: Stablecoins can reduce dependency on intermediary banking chains for settlement, but they do not remove obligations around onboarding, sanctions screening, transaction monitoring, reporting, and local licensing where applicable.

Polygon context: Polygon is built to support high-throughput, low-cost transactions with fast finality, properties that matter when stablecoin transfers are used as a settlement layer for payments. Polygon's Open Money Stack provides the infrastructure layer for stablecoin-based flows: fast-finality chains, bridging, and developer tooling designed to make onchain payments composable and enterprise-ready. For enterprises, the practical question is whether the chain's performance and reliability characteristics fit your settlement and reconciliation requirements.

Virtual accounts and multicurrency wallets

Virtual accounts can function like local account details in multiple countries, enabling businesses to receive and hold funds in different currencies without opening bank accounts in each market.

Why enterprises use them:

• Local-like collection and disbursement experiences
• Reduced friction for payers/beneficiaries
• Centralized visibility for treasury

AI-driven routing and compliance

Machine learning is increasingly used to:

• Optimize routing based on historical corridor performance (bank uptime, return rates, cutoff behavior)
• Strengthen compliance operations by flagging unusual patterns and reducing false positives in screening workflows

Enterprises should treat AI here as an augmentation layer: it can improve throughput and reduce manual review, but governance and auditability remain essential.

Regulatory and compliance challenges in international transfers

Faster rails don't eliminate compliance complexity; they often surface it sooner. The main challenges are structural:

• Different compliance regimes across countries: AML, sanctions, and reporting requirements vary. A single payment may be screened multiple times by different institutions.
• Uneven KYC expectations: Documentation accepted in one market may not satisfy another, triggering manual review or rejection.
• Inconsistent data formats and technical standards: Field limits and message formats can cause truncation or transformation, which can create false alerts or require repair.
• Limited operating hours and time-zone gaps: Even with SWIFT gpi's speed improvements, settlement depends on banking hours. Banking cutoff times — the daily deadline after which a sending bank queues outgoing wires for next-day processing — mean that a wire initiated in the late afternoon may not begin moving until the following business day, and no cross-border wire settles on weekends or holidays.
• Local rules and capital controls: Purpose-of-payment codes, tax documentation, and outbound caps can halt transfers if requirements are missed.

For stablecoin-based settlement specifically, enterprises typically need to evaluate:

• Counterparty onboarding and KYC/KYB standards
• Sanctions screening approach (including address risk where relevant)
• Transaction monitoring and audit trails
• Custody model and key management controls
• Jurisdiction-specific licensing and reporting obligations

How to evaluate a cross-border payments partner (including stablecoin rails)

Enterprises usually win by selecting a partner (or set of partners) that can orchestrate multiple rails while meeting internal risk and control requirements.

Evaluation criteria to pressure-test:

• Coverage aligned to your roadmap: Countries, currencies, and local payment methods. plus payout capabilities.
• Speed, reliability, and measurable SLAs: On-time delivery rates, exception rates, and clear playbooks for outages and investigations.
• Transparent pricing: Fees and FX markups disclosed up front, with controls over conversion timing. Note that SWIFT gpi has improved post-facto fee visibility but still does not provide binding upfront fee quotes; ask how your partner handles FX pricing transparency before the payment is initiated, not after.
• Compliance and security maturity: Licensing posture, screening and monitoring controls, auditability, and incident response.
• Integration fit: APIs, bulk payout tooling, reconciliation exports, role-based access controls, and audit-friendly reporting.
• Scalability: Ability to handle volume spikes and add corridors without re-architecting.

If you are adding stablecoins as a settlement option, also require:

• Clear on/off-ramp model (where conversion happens, by whom, and under what controls)
• Chain-level performance assumptions (finality targets, reorg risk profile, monitoring)
• Operational runbooks for failed/late transfers and dispute handling

Conclusion

Cross-border payment modernization is increasingly about combining rails: real-time networks and APIs for automation, virtual accounts for local-like reach, and blockchain and stablecoin-based settlement for 24/7 value transfer and reduced intermediary dependence.

SWIFT gpi has meaningfully improved the speed and trackability of traditional correspondent banking, but it has not changed the underlying architecture. Funds still move through intermediary banks, FX markups remain at the banks' discretion, and settlement stops when banks close. These are structural constraints, not implementation gaps.

For enterprise decision-makers, the actionable next step is to map your highest-cost or least-predictable corridors, then evaluate which mix of rails improves (1) settlement certainty, (2) total cost, and (3) compliance throughput. Polygon fits into this architecture as a stablecoin settlement layer designed for high transaction throughput and fast finality, attributes that matter when you need payments to clear on internet time.