Once hailed as the 'anti-bank' challenger for international transfers, Wise has quietly evolved beyond its consumer-facing app. Over the past 18 months, its strategic emphasis has shifted from marketing cheap USD-to-EUR conversions to building deep, real-time foreign exchange and local payout capabilities — not just for individuals, but for banks, fintechs, and payroll platforms. This pivot reflects a broader industry inflection point: cross-border payments are no longer about margin compression alone, but about infrastructure velocity, regulatory interoperability, and settlement finality.
The Infrastructure Layer Beneath the App
Wise’s public financials tell part of the story: in FY2023, its B2B revenue (via Wise Platform) grew 64% year-on-year to £278M — now accounting for 39% of total revenue. More telling is the underlying architecture: Wise operates 12+ licensed entities across Europe, Singapore, Australia, and the U.S., each holding local banking licenses or e-money authorizations. This isn’t just compliance theater — it enables true local-currency settlement without correspondent banking delays. Transactions routed through Wise’s Singapore entity, for example, settle in SGD within seconds via FAST, while EU payouts leverage TARGET2 and SEPA Instant rails with sub-2-second confirmation.
This infrastructure advantage compounds at scale: Wise processed over 15 billion cross-border transactions in 2023, with 72% settled in under 10 seconds — a metric rarely disclosed by legacy providers. Crucially, Wise no longer relies on SWIFT MT103 for most corridors; instead, it uses ISO 20022-compliant APIs to interconnect with domestic real-time payment systems, reducing reconciliation overhead and FX slippage risk.
Embedded FX: From Feature to Foundation
Three Pillars of Wise’s Embedded Strategy
- Local ledger balances: Holding multi-currency accounts directly on regulated balance sheets — not pooled custodial wallets — enabling instant debit/credit in 10+ currencies without pre-funding.
- Dynamic mid-market rate streaming: Delivering live FX rates with zero markup to enterprise partners via RESTful APIs, updated every 200ms during market hours.
- Regulatory passporting: Leveraging UK’s Temporary Permissions Regime and Singapore’s MAS Major Payment Institution license to deploy localized payout rails across APAC and EEA without re-licensing.
These pillars allow Wise to embed into payroll platforms like Deel and Remote — where salary disbursement in local currency now occurs within the same business day, even for contractors in emerging markets. Unlike traditional FX aggregators, Wise’s model eliminates the need for separate treasury management layers, compressing time-to-value for integrators by an average of 11 days per deployment cycle.
What This Means for the Broader Ecosystem
Wise’s evolution signals a structural shift: the competitive moat in cross-border payments is migrating from user interface and brand trust to settlement sovereignty. Firms that control their own local banking licenses, operate real-time rails, and maintain ISO 20022-native infrastructure gain asymmetric advantages in latency, auditability, and cost predictability. Legacy players — including some Tier-1 banks still reliant on SWIFT GPI overlays — face mounting pressure to either acquire such capabilities or partner deeply. Meanwhile, new entrants must now clear higher regulatory and technical thresholds before scaling beyond single-corridor pilots.
Notably, Wise’s gross margin on platform revenue stands at 61% — significantly above the 32–45% typical for pure-play remittance firms — underscoring how infrastructure ownership transforms unit economics. As central bank digital currencies (CBDCs) begin pilot integrations with private-sector rails, Wise’s architecture positions it not as a disruptor, but as a foundational layer for next-generation cross-border settlement.
For enterprises evaluating cross-border infrastructure, the question is no longer ‘How cheap is this transfer?’ but ‘How many milliseconds does settlement add to my cash conversion cycle — and who owns the liability?’ Wise’s quiet pivot suggests the answer increasingly lies in owned rails, not optimized routing.
