For over a decade, Wise (formerly TransferWise) has been synonymous with transparent, low-fee international transfers—especially for freelancers, expats, and SMEs. But recent operational shifts, product architecture changes, and regulatory filings suggest the company is quietly transforming its core identity: no longer just a payment conduit, but an increasingly foundational layer for cross-border financial plumbing.
The Infrastructure Turn
Wise’s Borderless Account—once marketed as a multi-currency ‘bank account for the world’—has evolved into something more systemic. As of Q1 2024, over 8.2 million active users hold balances across 50+ currencies, with 63% of those balances held outside their home currency. Crucially, Wise now processes over 47% of its total transaction volume through internal ledger settlements rather than external correspondent banking rails. This isn’t just cost optimization—it’s infrastructure consolidation. By routing payments internally where possible, Wise reduces reliance on SWIFT, minimizes FX exposure windows, and shortens settlement finality from hours to seconds for intra-platform flows.
This shift aligns with broader industry movement toward ‘settlement-as-a-service’. Unlike traditional banks that treat multi-currency accounts as retail offerings, Wise treats them as interoperable nodes—each balance representing a programmable, auditable, and API-accessible ledger position. That architectural choice enables features like instant currency conversion at mid-market rates without pre-funding, real-time balance synchronization across devices, and granular sub-accounting for teams—all built atop a unified, horizontally scalable ledger.
Regulatory Anchoring and Operational Realities
Wise’s expansion into local banking licenses—including full banking authorizations in the UK, EU, Singapore, and Australia—has fundamentally altered its risk posture and service scope. These aren’t just compliance checkboxes; they’re enablers of structural autonomy. With local deposit-taking licenses, Wise can now hold customer funds on its own balance sheet rather than relying on custodial arrangements with partner banks. This reduces counterparty risk, improves capital efficiency, and allows for faster innovation cycles—such as launching instant SEPA credit transfers or SGD-to-INR direct rail settlements without third-party intermediaries.
Key Regulatory Milestones Driving Product Evolution
- UK Prudential Regulation Authority (PRA) authorization — enabled direct GBP lending and safeguarding of client money under FCA rules
- EU Banking License (Estonia) — permitted euro-denominated deposits, SEPA Instant, and integration with TARGET2
- Singapore MAS Major Payment Institution license — unlocked SGD liquidity pools and local bank transfer integrations
- Australia APRA ADI approval — allowed AUD deposits, ACH-style PayID linking, and direct RBA settlement access
- US state-by-state money transmitter licenses — facilitated USD disbursement via FedACH and RTP, bypassing legacy correspondent networks
From Wallet to Workflow Engine
Perhaps the most consequential evolution lies not in what Wise *is*, but in how it’s being *used*. Business customers now deploy Wise accounts as operational hubs—not just for payroll or vendor payments, but as synchronized financial control points integrated into ERP, accounting, and treasury platforms. Over 34% of Wise’s B2B revenue now originates from API-driven use cases, including automated multi-currency invoicing, dynamic FX hedging triggers, and real-time cash position dashboards fed directly from Wise’s ledger. This signals a quiet but profound repositioning: Wise is no longer competing with PayPal or Revolut on user interface or branding—but with core banking systems on reliability, latency, and composability.
Still, challenges remain. Liquidity fragmentation persists across jurisdictions—Wise cannot yet offer true omnichannel liquidity pooling without additional central bank access. And while its transparency model sets industry benchmarks, regulatory divergence (e.g., MiCA vs. U.S. stablecoin frameworks) continues to constrain feature parity. Yet these constraints are increasingly treated as engineering problems—not strategic limitations.
Looking ahead, Wise’s trajectory suggests a future where borderless accounts become less about convenience and more about sovereignty: giving individuals and businesses direct, auditable, and composable control over cross-border value flow. As real-time rails proliferate and regulatory sandboxes mature, the line between ‘wallet’, ‘bank’, and ‘financial operating system’ will blur—not through marketing, but through architecture, licensing, and daily usage patterns.
