When TransferWise officially became Wise in February 2021, the change sparked quiet industry debate. While many interpreted it as a simple modernization of branding, WalletWireHub’s analysis of product roadmaps, regulatory filings, and partner integrations reveals something deeper: a deliberate transformation from a consumer-facing money transfer service into a foundational layer for global financial interoperability.
The Infrastructure Turn: From App to API
Wise’s public disclosures since 2022 show a sharp increase in B2B revenue—now accounting for over 42% of total income, up from just 18% in 2019. This shift is anchored in its Wise Platform, launched in 2020 and now powering cross-border payouts for 350+ fintechs, payroll providers, and neobanks across 80+ countries. Unlike legacy banking rails that charge per transaction or require correspondent relationships, Wise Platform offers programmable multi-currency accounts with real-time FX settlement, built on direct central bank settlement access in key jurisdictions like the UK, EU, US, and Singapore.
This isn’t abstraction: in Q3 2023 alone, Wise processed $12.7 billion in business-to-business flows—more than double its consumer remittance volume that quarter. The company’s 2023 Annual Report explicitly frames its mission as “building the financial infrastructure for a borderless world,” not merely simplifying international payments for individuals.
Regulatory Architecture as Competitive Moat
Wise’s expansion beyond borders has been underpinned by an unusually granular licensing strategy. Rather than relying on passporting or third-party banking partners, Wise holds 26 distinct regulatory authorizations—including EMIs in the UK and EU, MSBs in all 50 US states, and a full banking license in Lithuania granted in 2022. This allows it to hold customer funds locally, bypass SWIFT for domestic clearing, and comply with local capital requirements without intermediaries.
Core Regulatory Advantages Enabled by Direct Licensing
- Local currency settlement: Enables instant EUR/GBP/USD clearing via TARGET2 and CHAPS without correspondent fees
- Direct FX execution: Avoids markups from wholesale interbank brokers by accessing ECN feeds directly
- Multi-jurisdictional compliance automation: Real-time AML screening integrated with national PEP and sanctions databases
- Embedded finance readiness: Allows third-party apps to offer regulated multi-currency accounts without building their own compliance stack
- Capital efficiency: Reduces liquidity buffers required under EBA guidelines versus agent-based models
From Transparency to Interoperability
Wise’s original value proposition—fee-and-rate transparency—has evolved into technical transparency. Its open API documentation includes ISO 20022 message schemas, UETR tracking support, and granular webhook events for reconciliation. In 2024, Wise joined the ISO 20022 Migration Working Group alongside SWIFT, ECB, and JP Morgan, signaling intent to shape next-generation standards—not just adapt to them. Crucially, Wise does not gatekeep this infrastructure: its sandbox environment is publicly accessible, and pricing for Platform usage is published upfront—unlike most banking-as-a-service providers that negotiate bespoke contracts.
This openness reflects a broader industry inflection point. As central banks accelerate CBDC interoperability pilots (e.g., Project Dunbar, mBridge), Wise’s architecture—built on modular, auditable, and jurisdictionally compliant components—is increasingly seen as a viable bridge between legacy systems and sovereign digital currencies. It’s no longer about moving money faster; it’s about enabling money to be *recognized*, *valued*, and *settled* consistently across legal and technical boundaries.
Looking ahead, Wise’s trajectory suggests a future where cross-border finance is less defined by who moves money—and more by how seamlessly value can be verified, converted, and delivered across sovereign, technical, and regulatory domains. For developers, regulators, and financial institutions alike, the question is no longer whether to integrate with such infrastructure—but how deeply to rely on it as the new default rail.
