MGUSD is the US dollar stablecoin MoneyGram launched on June 2, 2026 to move through its existing global payments network. The launch release names four technology partners: Bridge (a Stripe company) as issuer, M0 as smart-contract infrastructure, Stellar as the settlement network, and Fireblocks as the wallet infrastructure. This article focuses on the Fireblocks piece and what the launch announcement does and does not specify about MGUSD's custody configuration.
​

Per the launch release, Fireblocks manages the wallets MoneyGram uses to send MGUSD to customer wallets embedded inside the MoneyGram app. That single sentence is the entire public description of the Fireblocks role as of June 2026. Everything beyond it comes from Fireblocks' general product documentation or is flagged as not yet publicly detailed.
​

Fireblocks is an institutional digital-asset infrastructure platform founded in 2018, offering MPC-based wallet custody, a policy and approval engine, treasury controls, and a connectivity layer called the Fireblocks Network. The platform serves banks, fintechs, exchanges, and stablecoin issuers, and is named in MoneyGram's June 2, 2026 launch release as the wallet infrastructure for MGUSD.
​

The company's public material describes the platform as digital-asset infrastructure for institutions that need to hold, move, and tokenize assets onchain without taking on raw key custody themselves. Fireblocks' general customer set spans banks like ABN AMRO, fintechs like Revolut, stablecoin issuers, and payment companies. Bridge, the issuer named in the MGUSD launch release, is itself listed in Fireblocks' public customer set, which gives the partnership a pre-existing infrastructure relationship beyond the MGUSD launch.
​

Fireblocks groups its product surface into a handful of layers. Wallet infrastructure and custody at the base, a policy engine for governance and approval workflows on top, treasury and operations tools alongside, and a Network layer for connectivity to other Fireblocks-using institutions. The Fireblocks Network explainer covers that connectivity layer in more depth and is the right place to read about settlement between Fireblocks customers.
​

Fireblocks uses multi-party computation, or MPC, to generate and use private keys without ever assembling the whole key in one place. Key shards live across separate hosts. Transaction signatures are produced through cooperative computation between shards. The platform layers a policy engine on top, so institutions can codify approval workflows, transfer limits, allowlists, and operational controls.
​

The MPC approach contrasts with traditional hardware-wallet or single-signer models. There is no single private key sitting on one device or in one HSM that an attacker could compromise to drain a wallet. Fireblocks describes the architecture in its public material as combining software and hardware defenses to remove a single point of compromise. For a stablecoin issuer or distributor, that matters most where reserves and operational floats sit, since those wallets are high-value targets.
​

The policy engine sits beside the key infrastructure. Institutions configure rules like "transfers over $1 million require two approvers from the treasury team," "this wallet can only send to allowlisted addresses," or "no transfers can be initiated outside business hours from this country." These rules are enforced at the platform layer before transactions are ever signed. The launch release does not specify what policy configuration MoneyGram uses for MGUSD wallets, so the specific approval workflows are not yet publicly described.
​

Per the June 2, 2026 launch announcement, Fireblocks manages the wallets MoneyGram uses to send MGUSD to customer wallets in the MoneyGram app. The release does not break out separate reserve, treasury, or operational wallets by name. It frames Fireblocks as the wallet infrastructure layer for MGUSD distribution out of MoneyGram's stack.
​

In practice, an institutional stablecoin stack distinguishes a few wallet roles. Issuer reserve wallets hold the assets backing the stablecoin. Operational wallets handle day-to-day movement. End-user wallets sit inside consumer apps and hold balances on behalf of customers. The launch release describes the third role explicitly: Fireblocks wallets used by MoneyGram to send tokens into customer wallets in the MoneyGram app. The issuer reserve side falls on Bridge, named in the release as the "regulated, GENIUS Act-ready issuer" of MGUSD (the release's own phrasing, attributed). M0 provides the mint and burn contract layer. Stellar is the settlement chain.
​

Stablecoin stacks typically separate wallets by role. Issuer reserve wallets hold the assets backing every outstanding token. Operational wallets handle distribution, redemption, and partner payouts. End-user wallets sit in consumer apps. Each role has different security, access, and policy needs, and a platform like Fireblocks lets the configuration differ wallet by wallet.
​

Issuer reserve wallets are the most security-sensitive piece. If reserves move improperly, the peg breaks. For MGUSD, the issuer is Bridge, so reserve attestations would come from Bridge under the GENIUS Act framing described in the release. The Fireblocks layer applies to the wallets MoneyGram uses on the distribution side, not to Bridge's issuer reserves directly. Operational wallets sit in the middle, receiving tokens from the issuer side and pushing them out to end users in the MoneyGram app. The policy engine matters most here. The launch release does not describe MoneyGram's specific policy configuration, so the exact rules around MGUSD operational movement are not publicly detailed as of June 2026.
​

The MGUSD stack splits four roles across four partners. Bridge issues, meaning it is the legal entity behind every minted token. M0 supplies the mint and burn smart contracts. Stellar hosts the asset and settles transfers. Fireblocks manages the wallets MoneyGram uses to send MGUSD into customer wallets in the MoneyGram app.
​

This kind of role separation is common for institutionally distributed stablecoins. Circle issues USDC and uses external custody and settlement partners for different functions. Paxos issues PYUSD for PayPal under a similar split of responsibilities. The advantage of separating roles is that each partner brings specialized infrastructure: regulatory standing from the issuer, programmable mint and burn from the contract layer, settlement and pathfinding from the chain, and institutional wallet security from the custody platform.

The Eco Routes intent router sits at a different layer entirely. It is a stablecoin cross-chain intent router that aggregates underlying transport rails. It is not part of the MGUSD issuance stack and is mentioned here only to clarify the layer split: issuance, contracts, settlement chain, and custody on one side; cross-chain intent routing on the other. The Eco Routes overview covers the routing layer in more depth.
​

The release names Fireblocks as the wallet infrastructure for MGUSD and describes the role in one sentence: Fireblocks manages the wallets MoneyGram uses to send tokens to customer wallets in the MoneyGram app. It does not break out reserve wallets, policy configuration, custody attestations, or insurance details. Anything beyond that is not yet publicly detailed.
​

The release leaves open which specific Fireblocks product configuration MoneyGram uses. It does not name MPC-CMP, policy-engine settings, treasury controls, or Network connectivity as discrete components. Whether MoneyGram operates issuer-side wallets at all, or only operational and distribution wallets while Bridge handles the reserve side, is also not stated. The reasonable read, given Fireblocks' general product set and the language in the release, is that MoneyGram uses Fireblocks for operational and distribution wallets on its side of the stack, while Bridge handles issuer-side responsibilities including the reserve relationship. Anything more granular has to wait for further public disclosure.
​

Stablecoin custody configurations vary by issuer and distributor. USDC's reserves sit with regulated financial institutions per Circle's public material. PYUSD is issued by Paxos under New York Department of Financial Services oversight. The MGUSD configuration described in the launch release uses Fireblocks for distribution wallets on the MoneyGram side, with Bridge as the issuer named in the release.
​

The structural similarity across these configurations is the separation of issuance, custody, and distribution. Where they differ is in which entity holds which role, and which infrastructure they use. The MGUSD release puts Fireblocks in the distribution-wallet seat on MoneyGram's side. For the GENIUS Act framing specifically, the release describes Bridge as a "regulated, GENIUS Act-ready issuer" of MGUSD. That phrasing is the release's own. The wallet infrastructure layer is a separate question from issuer regulatory standing. Fireblocks supplies infrastructure; it is not the legal issuer of MGUSD or of any other stablecoin it supports.
​

MGUSD's wallet configuration is one specific instance of a broader pattern: institutionally distributed stablecoins typically separate issuance, smart-contract logic, settlement, and wallet infrastructure across specialized partners. Fireblocks fits the wallet-infrastructure seat on MoneyGram's side. The release does not frame this as the only configuration; it is the one MoneyGram chose.
​

For institutions evaluating similar stacks, custody providers like Fireblocks, BitGo, and Anchorage each offer different feature sets and regulatory postures. The Fireblocks Network, a connectivity layer between member institutions, is one of the more visible pieces of the Fireblocks product set, though the launch release does not specifically mention Network involvement in MGUSD distribution. Whether MoneyGram uses Network connectivity for partner settlement is not publicly detailed as of June 2026. The broader pattern of stablecoin infrastructure providers sitting between issuers and end-user-facing applications applies here: the four-partner MGUSD stack is one expression of it, with each layer specialized and composed into a single stablecoin operating on a global distribution network.
​

Sources and methodology. Primary source: the MoneyGram MGUSD launch release, PRNewswire, June 2, 2026. Secondary sources: Fireblocks public product documentation (general custody and Network mechanics, not MGUSD specifics). Distinctions between launch-release specifics and Fireblocks' general product set are flagged inline throughout. As of June 2026, MGUSD-specific custody mechanics beyond the release's one-sentence Fireblocks description are not yet publicly detailed.
​