Ripple and Convera Bet on the Stablecoin Sandwich for B2B Payments

Every platform lead in cross-border payments now has a board question to answer in the next two quarters: do you build a stablecoin settlement layer, rent one, or partner your way out of the problem entirely. Convera just picked option three. The decision tells you more about the build-vs-buy math at mid-market FX firms than any vendor whitepaper will.

On March 31, Ripple announced a strategic collaboration with Convera to roll out stablecoin-enabled cross-border payments to enterprise customers. The structure is unglamorous and that's the point: Convera owns the customer, Ripple owns the rails. For engineering leaders watching this category, it's a clean case study in how the value chain is splitting.

What Happened

As TradingView reported, Convera, one of the larger non-bank B2B FX networks, has partnered with Ripple to introduce stablecoin-enabled cross-border payments for businesses. The pitch is straightforward: combine Convera's existing global payment network with Ripple's blockchain infrastructure to deliver faster settlements, improved liquidity, and more flexible treasury solutions for enterprise customers.

Convera handles the full payment flow, including customer experience and compliance. Ripple supplies the backend: liquidity sourcing, on- and off-ramps, and cross-border settlement. The target use cases are payment corridors where legacy financial rails remain slow or costly, exactly the corridors where correspondent banking economics have always been worst.

Patrick Gauthier, CEO of Convera, framed Ripple as "a clear leader in the crypto space and a natural fit for the company," and added, "We look forward to continued success and growth as we roll out these capabilities to customers near and far." Aaron Slettehaugh, SVP of Product at Ripple, positioned the demand side bluntly: "Enterprises are increasingly looking for faster, more flexible ways to move money globally without taking on the complexity of digital assets directly."

That last quote is the actual product spec. The end customer never sees a wallet, never holds a token, never reconciles a crypto balance. They send fiat, receive fiat, and a stablecoin moves in the middle. Ripple announced the deal via tweet on March 31, 2026, and the messaging emphasizes speed, liquidity, and reliability over anything XRP-specific.

Technical Anatomy

The architecture in play is what the industry now calls the "stablecoin sandwich." Payments originate in fiat at the sending end, convert into a stablecoin for the cross-border leg, then convert back into fiat at the receiving end. Three legs, two FX events, one settlement asset. Customers maintain familiar fiat-based workflows; the stablecoin is plumbing they never see.

Mechanically this collapses what used to be a chain of three to five correspondent banks into a single hop across a blockchain settlement layer plus two regulated on/off ramps. The model reduces reliance on multiple intermediary banks, which is where most of the latency and fee leakage in traditional SWIFT-based corridors actually lives. It also sidesteps crypto price volatility because the asset in flight is a stablecoin held for minutes, not a balance-sheet position.

From a platform engineering perspective, the interesting work is at the seams. The first conversion (fiat to stablecoin) needs deep, programmatic liquidity at the source currency. The settlement leg needs deterministic finality and a transaction monitoring layer that satisfies the receiving jurisdiction's AML regime. The off-ramp needs a banking partner in the destination country willing to credit a beneficiary account from a stablecoin-funded inflow. Any one of those three legs failing turns a "faster payment" into a stuck payment with worse customer-service economics than a normal SWIFT delay.

This is also where observability becomes non-negotiable. A correspondent banking failure has decades of operational runbooks. A stablecoin sandwich failure spans a fiat ledger, an on-ramp partner, an L1 or L2 settlement event, an off-ramp partner, and a destination ledger. Without distributed tracing across all five hops, mean time to resolution balloons. Teams building this in-house should be looking hard at OpenTelemetry instrumentation across every adapter, because that's the only way ops can tell a customer where their money actually is at minute 14 of a stuck payment.

Who Gets Burned

The first group exposed is mid-market cross-border payment providers who have been quietly building their own stablecoin settlement stacks for the last 18 months. Convera just demonstrated that you can skip that capex entirely by partnering with an infrastructure provider, keep your customer relationship, and ship the same product. If you're a competing FX firm with a half-built crypto team, your CFO is going to ask why headcount line items 12 through 20 still exist when a partnership gets you 80% of the outcome.

The second group is correspondent banks in slow corridors. The economics of intermediary banking depend on volume in exactly the corridors where stablecoin sandwiches work best: high-friction, high-fee, high-latency routes. Every enterprise that switches to a sandwich model takes deposit float and FX margin out of that chain. The banks won't disappear, but their pricing power on those specific lanes erodes quickly.

The third group, less obvious, is internal platform teams at large enterprises who pitched their boards on building a direct stablecoin treasury capability. Slettehaugh's quote about enterprises wanting speed "without taking on the complexity of digital assets directly" is the death sentence for those projects. If a treasurer can get the same settlement speed through their existing FX provider with zero wallet management and zero token custody risk, the in-house build loses its sponsor.

The General Counsel at any company evaluating a stablecoin sandwich vendor should be asking this week: which entity is the regulated payment institution of record in each corridor we operate in, and does the partnership structure shift any compliance obligation back onto us? In the Convera-Ripple split, Convera owns compliance. In a different vendor's split, that line might land somewhere far less comfortable for your filing cabinet.

Playbook for Engineering Teams

If you run platform at a payments or treasury company, three concrete moves matter this quarter. First, audit your settlement-layer roadmap against a partnership scenario. Map every engineer-month allocated to building blockchain settlement primitives and ask whether a Ripple-style backend partnership replaces 60% of that scope. If yes, redeploy the team toward customer-facing differentiation: corridor coverage, compliance UX, treasury analytics. The infrastructure layer is commoditizing faster than most roadmaps assume.

Second, design your integration boundary as if you'll swap the settlement provider in 24 months. Wrap on-ramp, off-ramp, and settlement calls behind a stable internal interface. The Convera-Ripple deal is a partnership, not a merger, and partnerships in this category get repriced. Vendor lock-in at the settlement layer is a board-level risk you can engineer around now for low cost or pay for later at high cost.

Third, build the observability story before you build the product. Distributed tracing across fiat ledgers, on-ramp APIs, chain events, and off-ramp confirmations is what separates a payments product that scales from one that drowns in support tickets. Containerized adapters per corridor, deployed via Docker with consistent logging contracts, will save you a re-platform in year two.

For VPs of Engineering, the hiring implication is also worth naming. The market for "blockchain settlement engineer" just got narrower and more senior; the market for "payments integration engineer who understands stablecoin plumbing" just got broader and more valuable. Adjust job ladders accordingly.

Key Takeaways

• The Convera-Ripple deal validates a clean split: payment networks own the customer and compliance, infrastructure providers own liquidity and settlement. Plan your org chart against that boundary.
• The stablecoin sandwich model lets enterprises move money globally without crypto exposure, removing the single biggest objection from corporate treasurers.
• Mid-market FX firms with in-flight in-house crypto builds should pressure-test their roadmap against a partnership alternative this quarter, before more capex sinks in.
• Observability across the five-hop sandwich (fiat, on-ramp, chain, off-ramp, fiat) is the operational moat. Teams without distributed tracing will lose on support economics.
• Teams evaluating stablecoin settlement should now be asking themselves whether their differentiation is the rails or the relationship, because they probably can't afford to own both.