Once known primarily for its transparent, low-cost peer-to-peer international transfers, Wise has quietly evolved into a sophisticated cross-border infrastructure layer—powering payouts, payroll, and embedded finance for fintechs, SaaS platforms, and global enterprises. Recent operational disclosures, regulatory filings, and API adoption patterns suggest a deliberate pivot: away from consumer brand dominance and toward becoming the invisible engine behind real-time, multi-currency settlement.
The Infrastructure Turn: From App to API
Wise’s public-facing app remains popular—but its fastest-growing revenue segment now stems from its Business Accounts and API platform. According to internal data cited in Q1 2024 investor briefings, over 62% of Wise’s non-consumer transaction volume flows through programmable interfaces. These aren’t simple payout wrappers; they integrate with core banking systems via ISO 20022-compliant messaging and support instant local-currency disbursement across 80+ countries—including SEPA Instant, UK Faster Payments, UPI, PIX, and PayNow. Crucially, Wise no longer routes most payments through correspondent banks. Instead, it holds local banking licenses or partnerships in 12 key jurisdictions (including Singapore, Australia, and the EU), enabling direct ledger access and true local settlement.
Real-Time FX at Scale: Beyond the Mid-Market Rate
While Wise still advertises its use of the mid-market rate, its underlying FX execution has matured significantly. The company now operates proprietary liquidity-matching algorithms that aggregate order flow across its own user base—effectively creating an internal FX pool. This reduces reliance on external market makers and allows sub-second price discovery for major currency pairs. For corporate clients, Wise offers dynamic hedging windows and forward contracts settled in local ledgers—not synthetic derivatives. In Q4 2023, over 44% of business FX volume was executed within 500ms of quote request—a metric previously seen only among institutional prime brokers.
Five Ways Wise’s Local Settlement Model Differs From Legacy Providers
- Direct ledger connectivity: No intermediary routing—funds settle instantly in recipient’s local bank account via domestic rails.
- No Nostro dependency: Eliminates pre-funded accounts and associated capital inefficiencies.
- ISO 20022-native architecture: Enables rich data transmission (e.g., invoice IDs, tax codes) alongside payments—critical for ERP reconciliation.
- Regulatory arbitrage mitigation: Local licensing means compliance with national AML/CFT rules—not just home-country oversight.
- Multi-currency accounting by default: Every business account maintains native balances in up to 10 currencies, with auto-reconciliation and P&L visibility.
What This Means for the Broader Ecosystem
This evolution signals a broader industry inflection point: cross-border payment providers are no longer competing solely on cost or speed—but on settlement sovereignty. As central banks roll out CBDC pilots and private-sector stablecoin rails gain traction, Wise’s model demonstrates how licensed, regulated, and interoperable local infrastructure can coexist—and even integrate—with new digital asset networks. Its recent integration with the Monetary Authority of Singapore’s Project Ubin infrastructure, for example, wasn’t about launching crypto wallets—it was about testing atomic settlements between SGD tokenized deposits and traditional bank accounts. That kind of technical pragmatism, grounded in regulation and real-world liquidity, may prove more durable than pure blockchain-first approaches in high-stakes commercial corridors.
Wise’s trajectory suggests that the future of cross-border payments won’t be won by building the fastest app—or the flashiest token—but by operating the most resilient, compliant, and deeply integrated local settlement layer across dozens of markets. For enterprise finance teams, embedded developers, and regulators alike, the question is no longer ‘How cheap is this transfer?’ but ‘Where does the liability land—and who owns the settlement risk?’

