Skip to content

Independent intelligence on digital money in motion

Tuesday, July 14, 2026

Latest JCB and Circle to Explore USDC Treasury and Merchant Payments
Payment Processors

Flutterwave Plans RLUSD Payment-Rail Integration After Ripple Investment

Ripple joined Flutterwave’s Series E as the companies outlined plans to add RLUSD settlement and XRP Ledger clearing to African payment flows.

Flutterwave has announced a strategic equity investment from Ripple as part of its Series E funding round, pairing new capital with plans to integrate Ripple’s stablecoin and blockchain payment infrastructure into Flutterwave’s African payment network.

The companies did not disclose the size of the investment. Flutterwave said the round values it at $3.2 billion, while TechCrunch independently reported the same valuation and said the fintech has raised more than $500 million in total.

The announcement matters to payment providers because it connects a large African payments platform with a specific stablecoin settlement plan. It is not, however, evidence that the integration is already live. Flutterwave described a product roadmap that will place Ripple USD, or RLUSD, in its payment rails and Send App remittance corridors, use the XRP Ledger for transaction clearing, and connect Flutterwave’s domestic network to Ripple Payments through a unified API.

Settlement is the central use case

Flutterwave supports local payment methods such as cards, bank transfers and mobile wallets. The planned Ripple integration sits behind those customer-facing methods: its stated purpose is to change how liquidity and cross-border settlement move through the network rather than require every payer or merchant to interact directly with a crypto asset.

That distinction is important. A stablecoin can serve as an intermediary settlement asset while the sender pays and the recipient receives local currency. In that model, the payment provider must coordinate conversion, liquidity, compliance screening and final payout across multiple jurisdictions. The value of the integration will therefore depend less on the token label than on whether it reduces prefunding needs, settlement delays and reconciliation complexity without shifting new risks to users.

Flutterwave said RLUSD is intended to become a primary settlement asset for high-volume channels, including Send App remittance corridors. It also said the companies plan to use the XRP Ledger for faster clearing and to bridge Flutterwave’s network with Ripple Payments. Those are forward-looking implementation commitments. Neither the company announcement nor TechCrunch provided a launch date, named the first corridors, identified participating banks or disclosed which regulated entities will handle conversion and custody.

A capital deal tied to product distribution

Ripple’s participation is more than a software partnership because it gives the blockchain payments company an equity position in a platform with established merchant, bank and remittance connections. TechCrunch reported that Flutterwave operates in 35 African countries. Distribution across that footprint could give Ripple a route to place RLUSD inside existing payment flows rather than building local acceptance and payout relationships market by market.

For Flutterwave, the arrangement adds a potential settlement layer to a network that already aggregates domestic payment methods. The company says it has processed more than one billion transactions worth over $50 billion; those figures are company-reported and do not establish how much future volume will use RLUSD or the XRP Ledger.

The commercial alignment may accelerate integration work, but it also concentrates important operational questions. Payment firms evaluating similar designs will need clarity on reserve and redemption access, foreign-exchange execution, wallet and key management, sanctions controls, transaction monitoring, consumer disclosures and treatment under each market’s payments and digital-asset rules.

Execution details remain open

The June 16 announcement establishes the investment, the $3.2 billion valuation and the intended architecture. It does not establish production volume, cost savings or real-time settlement performance. Flutterwave’s statements about lower costs, predictable pricing and faster settlement are objectives that will need to be tested once corridors become operational.

The next material milestones will be product availability, corridor-level licensing and named settlement partners. Evidence of live transactions would allow payment companies to compare the model with correspondent banking, prefunded local accounts and other stablecoin settlement services. Until then, the deal is best understood as a funded integration plan with meaningful distribution potential, not a completed migration of Flutterwave’s payment network to stablecoins.