MoneyGram Ramps on Solana: cash on/off-ramp API for builders

On 1 Aug 2026 the Solana Foundation announced that MoneyGram Ramps is live on Solana: builders get a developer API into MoneyGram’s global fiat on- and off-ramp network, embedded in the Solana Developer Platform payments module.

Source: solana.com/news/moneygram-ramps. This is infrastructure news for app wallets and exchanges — not a new L1 program.

Click to zoom

What shipped

MoneyGram’s network scale (as cited): 60M+ active customers, ~500k retail locations, digital reach across 200+ countries/territories. On Solana they are already an infrastructure partner and active validator; Ramps adds the consumer cash edge.

Why builders should care

Onchain USDC transfer is solved. Getting local cash in and out without a bank account is not. MoneyGram Ramps targets that gap so a Solana app can:

• Remittances / cross-border payouts — move value onchain; recipient cashes out at a participating location without wallet literacy
• Gig / distributed payroll — pay in stablecoins; offer cash-out where banking is patchy
• Aid / disbursement — speed + physical access in hard-to-reach markets

Composition with other Solana payment pieces (Solana Pay, CommerceKit, subscriptions, agent pay) is product-side: Ramps is the fiat perimeter; your app still owns wallet UX, identity, and onchain settlement.

Where it sits: Solana Developer Platform

Ramps is one module next to issuance, payments, wallet management, and other SDP APIs. Goal stated by Foundation: shorter path from idea to production for institutions and developers who should not reinvent compliance + correspondent banking.

User cash (MoneyGram location / digital)
        │
        ▼
MoneyGram Ramps API  (SDP payments module)
        │
        ▼
Solana wallet / exchange / app treasury  (stablecoin on-chain)
        │
        ▼
Your product logic (remit, payroll, checkout, aid)

Start: platform.solana.com and SDP overview. Treat sandbox credentials as mandatory before any production volume.

Builder checklist

1. Create SDP / platform access; request MoneyGram Ramps sandbox keys.
2. Map UX: deposit code / location finders vs withdrawal reference — do not assume “one QR = all markets.”
3. Define onchain asset (almost always a regulated stablecoin path) and custody model (embedded wallet vs user wallet).
4. Compliance: KYC/limits/geography are part of the ramp product — read MoneyGram + SDP docs; do not invent “permissionless cash-out.”
5. Failure modes: expired references, location hours, amount limits, refund paths when the onchain leg succeeds but cash pickup fails (or reverse).
6. Observability: correlate ramp session IDs with your Solana tx signatures for support.
7. Study Rift’s user flow as a reference integration, then differentiate.

What this is not

• Not a substitute for onchain DEX liquidity
• Not global identical coverage (25+ vs 170+ is asymmetric by design)
• Not “no regulation” — it is regulated network access packaged as API
• Not the same as card-acquiring or ACH ramps (e.g. Visa platform / other PFIs) — physical cash is the differentiator

Related DevRels reading

• Borderless — multi-PFI ramp orchestration
• Visa Stablecoin Platform
• Solana Launch hub — Foundation product map

Summary

MoneyGram Ramps on Solana gives SDP builders a single API into one of the world’s largest cash networks for on- and off-ramp, with sandbox and SDKs, so apps can connect stablecoin flows to local currency without standing up a bank. Coverage is cash-deposit–limited relative to cash-out footprint; first named wallet is Rift. If your product dies at “user has no bank and no exchange,” this is the perimeter integration to evaluate next to other ramp vendors.