Once synonymous with fast, low-cost migrant remittances, Remitly has quietly evolved into something far more consequential: a vertically integrated cross-border payments infrastructure provider. While public perception still anchors it to its 2011 origins as a mobile-first money-sending app, internal data, regulatory filings, and recent product launches point to a deliberate, multi-year repositioning—one that mirrors the wider convergence of remittance platforms, banking-as-a-service (BaaS), and real-time settlement ecosystems.
The Beyond-Remittance Playbook
Remitly’s 2023–2024 financial disclosures show that non-remittance revenue grew 67% year-over-year, now representing 22% of total revenue—a figure analysts expect to exceed one-third by end-2025. This growth stems not from marketing spend, but from three structural shifts: acquiring direct banking licenses in key corridors (notably the UK’s FCA authorization in Q2 2023), launching white-label payout APIs for fintechs and payroll platforms, and onboarding over 180,000 local bank and cash-agent partners across 15 countries to enable same-day, fee-transparent disbursement in local currency. Crucially, these capabilities are decoupled from the consumer-facing app—making Remitly less a ‘brand’ and more a middleware layer.
Embedded Finance at Scale
Where Remitly once competed with Wise and WorldRemit on UX and FX spreads, it now competes with banking cores like Mambu and settlement rails like RippleNet on integration depth and latency. Its Embedded Payouts API—launched in early 2024—supports ISO 20022 messaging, dynamic FX rate locking, and automated AML screening per transaction batch. Over 42 payroll SaaS platforms, including Deel and Remote, now route outbound wage disbursements through Remitly’s infrastructure, bypassing traditional correspondent banking entirely. This isn’t just efficiency—it’s architecture: each payroll flow generates structured payment data, enabling credit scoring, liquidity forecasting, and even micro-lending models in emerging markets.
Five Pillars of Remitly’s Infrastructure Shift
- Direct banking licenses in the UK, Canada, and Singapore—enabling balance sheet control and reduced counterparty risk
- Local-currency liquidity pools in 12 currencies, reducing reliance on third-party forex providers
- Real-time settlement APIs compliant with SEPA Instant, UPI, and PIX—cutting average payout latency from 24 hours to under 90 seconds
- Regulatory-grade KYC orchestration, integrating ID verification, biometric liveness, and watchlist screening into single API calls
- Multi-rail routing logic that dynamically selects between SWIFT, instant rails, and cash networks based on cost, speed, and compliance constraints
What This Means for the Broader Ecosystem
This evolution signals a quiet but irreversible segmentation in cross-border payments: consumer-facing brands are increasingly becoming front-ends for shared, interoperable infrastructure layers. Remitly’s move echoes similar trajectories at Wise (with its Business Accounts and B2B API suite) and PayPal (via its Xoom acquisition and cross-border merchant solutions). Yet unlike peers, Remitly built its core infrastructure around high-frequency, low-value, high-compliance transactions—the exact profile demanded by gig economy platforms, micro-insurance payouts, and government social transfers. As central banks roll out CBDC bridges and regional instant payment systems mature, Remitly’s embedded model positions it not as a remittance company playing catch-up—but as a foundational node in next-generation cross-border settlement networks. The question is no longer whether remittance firms can scale; it’s whether legacy banks and rails can integrate fast enough to remain relevant in this new topology.
Remitly’s infrastructure pivot reflects a deeper truth about global payments: the most valuable assets are no longer brand recognition or app downloads—but interoperable, compliant, and real-time-ready rails that serve both consumers and institutions. As regulatory harmonization accelerates and open finance frameworks gain traction, the line between ‘remittance provider’ and ‘payments infrastructure operator’ will vanish—not through consolidation, but through functional convergence.
