MoneyGram exposes its global send, receive, and cash-network capabilities to partners through a REST API platform hosted at developer.moneygram.com. The platform spans consumer transfers (C2C), business disbursements (B2C), an agent locator, FX quoting, webhooks, and a newer crypto on/off-ramp product called MoneyGram Ramps. With the June 2, 2026 launch of MGUSD, MoneyGram added a stablecoin issued natively on Stellar to the same surface that already routes cash pickups across roughly 200 countries.
​

This article walks through what MoneyGram actually exposes today, which partner types integrate against it, and where MGUSD opens a new programmable surface for builders.
​

MoneyGram's developer platform is split into consumer transfers, business disbursements, reference data, webhooks, and the MoneyGram Ramps crypto on/off-ramp. Authentication uses OAuth 2.0, with separate sandbox and production environments. Per the developer portal, the API covers send, receive, status, refund, amend, FX quoting, agent lookup, and regulatory event webhooks.
​

The platform is REST-based. Two environments are documented: https://sandboxapi.moneygram.com for development and certification, and https://api.moneygram.com for production. Each environment has its own OAuth credentials, and production access is gated on certification of the integration.
​

The platform's product surface, per the developer portal, breaks down roughly like this:

The send and receive APIs handle the lifecycle of a money transfer: quote the fee and FX rate, stage the transaction, commit it, and either deliver to cash pickup, deliver to a bank account, or refund. The agent locator returns nearby retail locations. Webhooks push transaction-state changes and regulatory holds back to the integrator.
​

A typical send flow against the C2C surface looks roughly like this. The integrator calls a quote endpoint with send country, receive country, amount, funding method, and payout method. MoneyGram returns the quote with fee, FX rate, and total cost. The integrator then calls update to attach sender and recipient details, then commit to lock the transaction. The status endpoint and webhook subscriptions surface state transitions like "in process," "available for pickup," "paid out," "refunded," or "on hold for regulatory review."
​

The receive and disbursement surface mirrors that pattern for businesses that need to push funds out to recipients. A payroll platform sending wages to contractors in another country, a marketplace paying out sellers, or a neobank funding cross-border withdrawals would integrate against the disbursement endpoints, with batch and asynchronous variants documented for high-volume flows.
​

Compliance webhooks are not optional in cross-border payments. MoneyGram exposes regulatory notifications as a webhook event type per its developer documentation, so partners can react when a transaction is paused for sanctions screening, KYC review, or recipient ID mismatches without needing to poll.
​

MoneyGram's recent public partnerships span bank-account authentication (Plaid), card-funded sends (Mastercard Move), and crypto on/off-ramp distribution through MoneyGram Ramps. The Ramps product, launched May 2, 2025, targets wallets, exchanges, and fintech apps that want to plug a global cash network into a crypto frontend.
​

Per MoneyGram's April 2025 announcement, Plaid powers bank-account authentication for U.S. customers funding domestic and cross-border transfers, replacing manual micro-deposit verification. Mastercard Move was integrated to let any U.S.-issued Mastercard fund sends to 38 receiving markets, with payout reach extended through Mastercard's broader endpoint network.
​

On the Ramps side, the named partner stack is Stellar (blockchain), Circle (USDC), and a documented set of integrators. PYMNTS and Electronic Payments International coverage of the Ramps launch describes the target audience as "wallets, exchanges, and fintech apps" embedding cash-in and cash-out, with the developer portal claiming sandbox setup in approximately five minutes versus the prior multi-week timeline.
​

The MGUSD launch release (June 2, 2026) names Bridge, a Stripe company, as the regulated issuer; M0 as the smart-contract infrastructure provider for mint and burn; Fireblocks as the custody and wallet layer; and the Stellar Development Foundation as the blockchain partner. Each of those is a partner of MoneyGram, not a downstream integrator, but the stack signals which infrastructure layers a developer building against MoneyGram's stablecoin rails will touch indirectly.
​

MGUSD adds a programmable, MoneyGram-issued dollar to the same network developers already integrate against. Per the launch release, MGUSD is issued by Bridge (a Stripe company) under the GENIUS Act framework, deployed natively on Stellar, with M0 providing the smart-contract infrastructure for mint and burn, and Fireblocks handling MoneyGram's wallet layer. As of June 2026, limited public technical detail is available beyond the launch announcement.
​

Structurally, this changes what's possible at the API edge in a few ways, though specifics will depend on what MoneyGram and its partners document over the coming quarters.
​

First, the cash-in and cash-out leg becomes addressable in the same asset. Before MGUSD, the Ramps product moved customers between fiat cash and USDC on Stellar. With MGUSD live, an integrator can route cash deposits into a MoneyGram-issued dollar that settles on the same chain, with the same agent network on the off-ramp side. Per the launch release, MoneyGram's roughly 500,000 retail locations across approximately 200 countries become the cash-out network for an asset MoneyGram itself issues.
​

Second, programmable settlement becomes available for partners building treasury or payout flows. M0's smart-contract layer is the mint-and-burn primitive per the launch release, so MGUSD movement is a Stellar operation that can be observed onchain rather than requiring a polling loop against the transaction-status endpoint.
​

Third, the developer pattern shifts from "API call plus webhook" to "API call plus webhook plus onchain event." Builders accustomed to indexing Stellar transactions can correlate them with MoneyGram's transaction IDs. The exact event shape and how MoneyGram surfaces MGUSD movement through its existing webhook subscriptions is not yet documented publicly, so this is per the launch positioning rather than a published spec.
​

A MoneyGram integration covers cash-in, cash-out, and stablecoin issuance on Stellar. Stablecoin orchestration layers like Eco Routes, Across, LI.FI, Squid, and Jumper sit at a different altitude: they aggregate multiple chains and rails so a builder can express an intent (move X dollars from chain A to chain B) without picking the underlying transport.
​

The two layers compose rather than compete. A fintech wallet integrating MoneyGram's API gets cash-in and cash-out in roughly 200 countries and a Stellar-native dollar. If that wallet's users also hold balances on Ethereum, Base, Arbitrum, or other EVM chains, an intent-routing layer can bridge balances toward Stellar (or vice versa) using whatever transport rail is fastest or cheapest for that route, then settle into MGUSD for the MoneyGram leg.
​

Eco Routes is one example of an intent-router that aggregates transport rails (it composes Hyperlane and CCTP today; LayerZero and Wormhole are peer messaging layers in the same neutral set, not Eco partners). Across, LI.FI, Squid, and Jumper are peer aggregators with their own routing logic and rail coverage. None of them substitute for MoneyGram's cash network or for MGUSD issuance. They sit upstream of the MoneyGram leg, doing the chain-to-chain hop before the stablecoin enters MoneyGram's surface.
​

Coverage and corridor support vary by product. The on-ramp covers 30+ countries and the off-ramp covers 170+ countries per MoneyGram's Ramps documentation. Standard C2C send reaches more than 200 countries and territories.
​

MoneyGram provides a sandbox at sandboxapi.moneygram.com for development and a separate production environment at api.moneygram.com. Sandbox credentials are issued at signup; production credentials follow certification of the integration. For MoneyGram Ramps specifically, sandbox setup is documented at approximately five minutes per the May 2025 launch coverage.
​

A typical onboarding path looks like this. Register on the developer portal. Get sandbox OAuth credentials. Build and test against the sandbox endpoints, including webhook subscriptions for transaction events. Submit the integration for certification. Receive production credentials and migrate the integration to the production base URL.
​

For Ramps integrations, MoneyGram documents a wallet-domain allowlist step so on-ramp and off-ramp endpoints work with the integrator's frontend. That step replaces the longer manual onboarding that preceded the May 2025 Ramps launch.
​

This article was assembled from MoneyGram's developer portal at developer.moneygram.com (consulted June 2026), the MoneyGram Ramps launch release (PR Newswire, May 2, 2025), PYMNTS coverage of the Ramps launch (May 2025), Electronic Payments International coverage of the Ramps launch (May 2025), and the MGUSD launch release (PR Newswire, June 2, 2026). Partner stack details for MGUSD (Bridge, M0, Fireblocks, Stellar Development Foundation) come from the June 2 launch release. Sandbox and production base URLs come from the developer portal's overview page. Where MGUSD's onchain mechanics are described, the framing follows the launch announcement; as of June 2026, limited public technical detail is available beyond what's in that release.
​