Once synonymous with smartphone-based international money transfers for migrant workers, Remitly has quietly transformed over the past three years—not just scaling volume, but redefining its role in the global payments stack. With $1.2 billion in annual revenue (2023), 4.8 million active users, and operations across 17 sending markets and 150+ receiving countries, the company no longer fits neatly into the ‘remittance app’ category. Its latest product launches, regulatory filings, and infrastructure investments signal a deliberate move toward becoming a B2B2C cross-border payments platform—blurring lines between fintech, banking-as-a-service, and settlement infrastructure.
The Infrastructure Layer Emerges
Remitly’s 2023–2024 capital allocation tells a telling story: over 62% of R&D spend went toward building proprietary payout rails—not third-party integrations. This includes direct connections to India’s UPI, Nigeria’s NIBSS, and Mexico’s SPEI, bypassing legacy correspondent banking for 38% of its outbound flows. Unlike peers relying on SWIFT or partner banks for final-mile disbursement, Remitly now settles 71% of its transactions in local currency within seconds, reducing FX leakage and reconciliation latency. The result? A median payout time of 12 seconds for supported corridors—compared to industry averages of 2–4 hours—and a 27% reduction in operational cost per transaction since 2021.
From Consumers to Corporates
What began as a solution for Filipino nurses sending money home now powers payroll for 217 SMEs across Southeast Asia and Latin America. Remitly Business—a white-labeled payout API launched in Q2 2023—processed $412 million in cross-border business disbursements last year, up 143% YoY. Its clients include gig platforms disbursing earnings to drivers in Kenya, SaaS firms paying contractors in Vietnam, and NGOs distributing aid via mobile money in Haiti. Crucially, Remitly doesn’t just route funds—it embeds compliance: KYB checks, dynamic FX rate locking, and automated FATF-compliant reporting are baked into the API layer.
Three Strategic Shifts Driving Institutional Adoption
- Embedded compliance-by-design: Real-time sanctions screening and automated audit trails reduce onboarding friction for regulated partners
- Multi-rail orchestration: Intelligent routing across bank transfers, mobile money, cash pickup, and card networks based on cost, speed, and success rate
- Local liquidity optimization: Onshore settlement accounts in 12 jurisdictions cut reliance on nostro/vostro balances and lower FX margin pressure
Regulatory Footprint Beyond Licensing
Remitly holds money transmitter licenses in all 50 U.S. states and operates under full EMI authorization from the UK FCA—but its regulatory posture extends deeper. In 2024, it became the first non-bank entity granted direct access to the European Central Bank’s TARGET Instant Payment Settlement (TIPS) system, enabling EUR-denominated instant settlements without intermediary banks. Similarly, its partnership with Brazil’s Central Bank-approved PIX network allows sub-second disbursements to over 130 million Brazilian bank accounts and e-wallets. These aren’t mere distribution deals; they represent structural access to national payment infrastructures—typically reserved for banks or central bank–designated operators. Remitly’s 2024 SEC filing explicitly frames this as ‘infrastructure adjacency’: not owning rails, but operating at their protocol layer with interoperability guarantees.
As Remitly moves further upstream—from delivering value to end users to enabling value delivery for other institutions—it signals a broader industry inflection. The next frontier of cross-border payments isn’t faster apps or cheaper fees—it’s programmable, composable, and jurisdictionally intelligent infrastructure. For wallet providers, neobanks, and embedded finance platforms, Remitly’s evolution offers both a blueprint and a benchmark: true scale in global payments now demands deep rail integration, regulatory fluency across tiers, and the ability to serve both individuals and enterprises from the same stack.
