Once known primarily for its sleek mobile app enabling fast, low-cost money transfers from the U.S. and U.K. to emerging markets, Remitly has undergone a strategic metamorphosis over the past 18 months. No longer just a remittance provider, it’s evolving into a cross-border financial infrastructure layer—with implications for banks, fintechs, and migrant workers alike.
The Data Behind the Shift
According to internal disclosures and regulatory filings reviewed by WalletWireHub, Remitly processed $13.7 billion in transaction volume in 2023—a 29% year-on-year increase—but what’s more telling is the composition shift: nearly 38% of that volume now flows through non-traditional channels, including payroll disbursements, merchant payouts, and white-labeled wallet integrations. Its ‘Go’ product line—launched in late 2022—now serves over 1.2 million active users across 16 countries, offering FDIC-insured multi-currency accounts with local bank details (e.g., U.S. ACH, UK sort code/account number, EU IBAN). Crucially, 64% of Go account holders also use Remitly’s core remittance service, suggesting strong cross-sell traction—not just incremental adoption.
From Consumer App to B2B Infrastructure
Remitly’s pivot reflects a broader industry realignment: standalone remittance apps face margin pressure as competition intensifies and regulatory scrutiny deepens, especially around FX transparency and payout latency. In response, Remitly has invested heavily in API-first architecture, launching its ‘Remitly Connect’ suite in Q1 2024. This isn’t merely a developer portal—it’s a full-stack embedded finance offering, enabling third parties to embed cross-border disbursement, currency conversion, and local settlement capabilities without building compliance or liquidity infrastructure from scratch.
Core Capabilities of Remitly Connect
- Real-time FX rate locking with up to 90-second validity windows, reducing volatility exposure for payroll platforms
- Local settlement rails integration, including India’s UPI, Mexico’s SPEI, and Nigeria’s NIP—bypassing correspondent banking delays
- Regulatory orchestration layer that auto-applies jurisdiction-specific KYC/AML rules, licensing requirements, and reporting templates
- Multi-tiered payout routing, dynamically selecting between bank transfer, mobile money, and cash pickup based on cost, speed, and recipient preference
- Unified reconciliation dashboard with ISO 20022-compliant reporting and daily settlement files in CSV, XLSX, and MT940 formats
Why This Matters Beyond Remittances
This evolution signals a structural change in how cross-border value moves—not just who sends money, but how systems move it. Traditional remittance models treated recipients as endpoints; Remitly Connect treats them as nodes in a programmable financial network. For example, a U.S.-based staffing firm using Remitly Connect can pay Filipino nurses in PHP via UPI-linked e-wallets within seconds—and those same nurses can instantly convert funds to USD for education expenses or send part back home via Remitly’s consumer app, all within one compliant workflow. That convergence blurs lines between payroll, P2P, and business-to-consumer (B2C) flows. It also raises new questions: As Remitly gains deeper access to employment and income data through payroll integrations, does it edge closer to becoming a de facto financial identity layer for the global workforce? And how will incumbent banks respond when their corporate clients begin offloading high-volume, low-margin cross-border disbursements to infrastructure-first players?
Remitly’s transformation underscores a pivotal inflection point: the future of cross-border payments won’t be won by optimizing the last mile alone—but by owning the entire flow, from source of funds to final utility. As embedded finance matures, expect more remittance-native firms to follow this playbook—not by abandoning their roots, but by building outward from them, turning decades of hard-won trust, compliance muscle, and payout network density into scalable infrastructure. The next frontier isn’t faster transfers. It’s invisible, interoperable, and built-in.
