Ripple Executive Sets Near-Term xRapid Production Window

Ripple executive Sagar Sarbhai said on September 17, 2018 that the company expected to put xRapid, its XRP-dependent cross-border liquidity product, into production within roughly a month. The statement, made in a CNBC interview, was a timetable from a company official—not a launch announcement, customer deployment record or proof of transaction volume.

That distinction mattered. Ripple had already sold financial institutions on payment messaging and settlement software that did not require them to hold or route value through XRP. xRapid was the more consequential test: it was designed to convert an originating fiat currency into XRP at an exchange, transfer XRP across the ledger, and convert it into destination currency. A production launch would therefore connect an openly traded digital asset to a commercial payment workflow rather than confining “blockchain” adoption to private institutional software.

From pilot plumbing to a production forecast

Ripple’s own August 17, 2018 release described the intended exchange structure. Bittrex was designated the preferred venue for U.S.-dollar legs, Bitso for Mexican-peso legs and Coins.ph for Philippine-peso legs. In Ripple’s illustrative U.S.-to-Mexico flow, dollars would be converted into XRP on Bittrex, XRP would settle on the XRP Ledger, and Bitso would convert it into pesos for delivery through local rails.

On September 17, Sarbhai said Ripple had made significant progress and expressed confidence that production news would come within “the next month or so.” His wording left important questions unanswered: he did not identify production customers in the CNBC report, quantify expected payment volume, specify a launch date, or provide independently audited cost and speed results. The verified development was therefore Ripple’s public commitment to a near-term production window, not evidence that banks were already using XRP at scale.

The institutional significance lay in liquidity design. Conventional cross-border providers often pre-position balances in destination markets. Ripple argued that a rapid fiat-XRP-fiat conversion could source liquidity on demand and reduce the need for those prefunded balances. But that thesis also depended on exchange access, orderly XRP markets, compliance controls and enough local depth to complete both conversions without erasing the claimed savings through spread or slippage. None of those conditions was established by the September 17 interview alone.

A risk-off market backdrop

The announcement arrived during a broad selloff on Kraken. The exchange’s September 17 daily market report listed bitcoin at $6,236, down 4.05% for its reporting session; ether at $193.10, down 12.9%; XRP at $0.2681, down 4.67%; and EOS at $4.70, down 13.8%. Kraken reported $123 million traded across all markets, including crypto pairs quoted in U.S. dollars, euros, yen, Canadian dollars and pounds.

Those figures describe Kraken only, not a consolidated global market. The surviving report does not state the timezone or precise cutoff methodology on the page, and its prices and percentages should not be treated as universal closes. They nevertheless show that Sarbhai’s forecast landed in a session when XRP fell alongside a much wider decline. The record does not establish that the xRapid comments caused the day’s price action, and the cross-asset losses argue against assigning the move to a Ripple-specific catalyst.

Later confirmation

Later context confirms the timetable but should not be read backward into September 17. On October 2, 2018, Ripple announced that xRapid was commercially available and moving into production with MercuryFX, Cuallix and Catalyst Corporate Federal Credit Union. That later release validates Sarbhai’s near-term forecast. It does not convert the September 17 statement into proof of live volume, savings or broad bank adoption on that earlier date.