PYUSDx custom stablecoins: anyone can issue a dollar now — merchants should accept one, not mint one

What PayPal, M0 and MoonPay launched on September 9

The facts, as reported by Crowdfund Insider and confirmed against the partners' own materials. PYUSDx is not a stablecoin. It is an issuance framework: a company plugs into it and gets a custom, branded, on-chain dollar token, fully backed one-to-one by PayPal USD (PYUSD), without building its own reserves, issuance, liquidity or attestation stack. The platform was first announced on February 27, 2026; on September 9 it opened to any developer.

The roles are precise. M0 built the programmable token infrastructure, where an issuer configures each component instead of accepting a fixed model. MoonPay Digital Assets Limited issues the PYUSDx-layer tokens and holds the PYUSD that backs them. PayPal supplies the ecosystem connection through PYUSD, which remains a Paxos-issued stablecoin reserved with dollar deposits, US Treasuries and cash equivalents under New York Department of Financial Services oversight.

What a builder can set: token name and symbol, reward distribution, freeze and administrative controls, compliance rules, reserve composition and revenue-sharing on the backing assets, plus cross-chain deployment. The partners say a token can go from concept to live "in days rather than months". Three issuers are already live: Saturn, whose USDat token settles Bitcoin-backed credit; Concrete, whose ConcUSD is a reward-bearing token for on-chain vault allocation; and Cap, which migrated its cUSD onto the platform for covered-credit float. Together they have processed more than $100 million. Conversions between custom tokens happen at par through a shared swap facility, so no secondary market is needed.

PayPal's May Zabaneh summarised the pitch: "The stablecoin market is maturing fast. What separates the next phase isn't the asset. It's what companies can do with it." For context, PYUSD's own circulation sits near $2.8 billion, against roughly $183 billion for USDT and $75 billion for USDC. PYUSDx is PayPal's way of growing that footprint indirectly: every issuer that scales needs more PYUSD behind it.

Read the structure: a dollar backed by a dollar backed by a dollar

Strip the branding and the architecture has four layers. At the bottom, dollar assets at Paxos. Above them, PYUSD. Above that, PYUSDx tokens issued by MoonPay Digital Assets, which holds the PYUSD. At the top, the custom token a business puts its name on. Each layer is described as fully reserved by the layer below it, and the arithmetic holds. The economics and the obligations, however, change at each step.

Start with redemption. A holder of a branded token does not have a relationship with PayPal or Paxos. The partners' own disclaimer is explicit on this point: the tokens "are not PayPal USD issued by Paxos Trust Company, NA or PayPal, are not a PayPal product or service", and "cannot be used to transact on PayPal's or Venmo's platforms". To get to bank money, a holder redeems with the upper issuer first, which then redeems PYUSD at Paxos. As crypto.news put it on September 11, a full redemption "traverses two independent obligations, each with its own terms, timing, and operational capacity". In calm markets that is a formality. Under stress it is a queue.

Then the float. M0's CEO Luca Prosperi was candid about who benefits: "When you hold someone else's stablecoin, you use its programming and rulebook", and with PYUSDx the "float economics that historically belonged to the issuer now sit one layer out, with the builder". That is the commercial engine of the product. A company issuing its own dollar captures the reserve income and the rulebook. The holder of that dollar is the one who pays for the extra layer, in redemption distance and in counterparty exposure.

Regulation has not caught up with this shape. The GENIUS Act defines permitted reserve assets — currency, insured deposits, Treasuries, repos, money market funds — but says nothing about a stablecoin backed by a stablecoin issued by someone else. The statute takes effect on the earlier of January 18, 2027 or 120 days after final rules, and the agencies missed their July 2026 rulemaking deadline. The partners note that regulatory treatment of each PYUSDx token "varies by jurisdiction and sits with each issuer". Until rules land, a branded wrapper is exactly what the disclaimer says it is: a private token whose legal relationship runs to the upper issuer.

Why fragmentation is the merchant's problem, not the issuer's

Prosperi's other line is the one a business owner should read twice: "growing institutional participation is creating a more fragmented stablecoin ecosystem", and the middle layer exists to abstract that complexity. He is describing the world that PYUSDx accelerates. The 21-bank consortium coin is due in 2027. Open USD is being issued by a 140-company standard. Chime, U.S. Bank and PayPal are each fielding a dollar. Now any lending protocol, vault, gaming studio or loyalty programme can mint one in days.

For an issuer, fragmentation is a feature: each dollar is a moat with float income. For a merchant, every new dollar token is a new question at the register — do you take this one? — and every answer is a decision about counterparty risk you did not ask to make. Accept a wrapper and your proceeds are a claim two redemptions away from a bank. Refuse it and you turn away a customer whose money is, in every economic sense, a dollar. Neither is a good position for a business whose job is selling things.

The first customer who tries to pay you in a PYUSDx-issued token will probably be a crypto-native business, not a consumer. The tokens cannot be spent in PayPal or Venmo, so retail distribution is thin. The live issuers are all in on-chain credit and vaults, and the next two — USD.AI and Fairblock — are infrastructure. The merchant-facing effect for now is a longer list of dollar tokens circulating in the wallets of your B2B counterparties and, with each one, more variance in how safe "a dollar" actually is.

Should a merchant issue its own PYUSDx custom stablecoin?

The pitch will reach retailers and platforms eventually — a branded dollar for your marketplace, a loyalty coin that earns you float, a closed-loop token for your gig workers. Be honest about what you would be signing up for.

You would be taking on an issuer's obligations. Compliance rules, freeze decisions, reward distribution, reserve reporting and redemption operations all become yours to configure and to answer for. The platform removes the engineering; it does not remove the responsibility. The partners are explicit that regulatory treatment sits with each issuer.

You would be solving a distribution problem you do not have. Your customers already hold dollars on-chain: USDC and USDT dominate, with roughly $258 billion in circulation between them. A branded coin asks them to swap into your token before they can buy from you, then swap out afterwards. That is friction at the exact point where a payment method should disappear.

The float is smaller than it looks for a merchant. Reserve income accrues on balances that sit idle. A business's stablecoin balances do not sit idle; they pay suppliers, staff and rent. The issuers thriving on PYUSDx today are credit platforms and vaults whose whole business is holding float. A restaurant, an agency or an online store is not that business.

The correct reading of PYUSDx for a merchant is therefore not "now I can mint a dollar". It is "now everyone else can, so my acceptance policy has to be issuer-agnostic and my settlement has to be in a stablecoin I trust". Those are two product decisions, and both are already available.

How Payzum handles a fragmented stablecoin market

Payzum is a non-custodial, crypto-only payment processor. It never holds, pools or controls funds; each payment settles directly into wallets the merchant controls. That single design choice answers the two questions that PYUSDx raises for a business.

Which stablecoin do I accept? The one the customer has. Payzum accepts payments across Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche, and with optional auto-conversion a merchant settles in USDC or USDT regardless of what was paid. You choose the dollar you want to hold; the customer chooses the one they want to spend. The comparison in USDT vs USDC for payments covers how to pick, and which stablecoins US merchants can accept covers the regulatory side.

Who holds my money between the sale and my spending it? Nobody. There is no Payzum balance, no upper issuer, no custodian in the chain. A confirmed payment is settled — about 0.4 seconds on Solana, around 2 seconds on Base or Polygon — and it is final, so there are no chargebacks. If a payments provider in your stack disappears, as Kulipa's shutdown showed, your funds are unaffected because they were never with the provider. The same logic applies to a wrapper token's issuer: settle in USDC or USDT and the redemption chain of someone else's branded dollar is not your problem.

The ways to get paid cover every channel. Online: hosted checkout, payment links and buttons, the drop-in plugin, invoices with expiry and overpayment detection, and recurring subscriptions. In person: the Payzum POS, with a fresh QR code per sale, any phone as a terminal, PIN-protected cashiers and analytics per cashier and terminal. Paying out: mass payouts by CSV and EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche — the tool a logistics company would use to pay 2,300 contractors without issuing a coin of its own.

How it works, step by step

1. Connect wallets you control. You supply the destination addresses. From that moment there is no intermediary balance anywhere in the flow.
2. Set your acceptance policy. Choose the networks you accept on. Turn on auto-conversion so that whatever a customer pays with, you settle in USDC or USDT.
3. Choose how you get paid. Hosted checkout, links, plugin, invoices or subscriptions online; the POS at the counter; CSV or EVM payouts when you are the one paying.
4. Reconcile automatically. Signed webhooks fire on every payment, a REST API with API keys exposes the same events, and a full audit log records which sale settled, on which chain, in which asset.

Issuing a custom stablecoin vs accepting stablecoins — comparison

What PYUSDx offers a business, against what a merchant can switch on this week.

Fair objections

"A branded dollar would strengthen my marketplace's ecosystem."

For a platform whose users keep balances inside it — a credit protocol, a vault, a gaming economy — that may be true, and PYUSDx is built for exactly those cases. For a business that sells goods or services and pays suppliers, the balances leave too quickly for float to matter, and the swap-in requirement costs you conversions at checkout. Run the numbers on idle balance before you run them on reserve yield.

"If PayPal is behind it, isn't a PYUSDx token as safe as PYUSD?"

PYUSD is issued by Paxos under NYDFS supervision. A PYUSDx token is issued by MoonPay Digital Assets Limited and then by the upper issuer, and the partners state the token is not a PayPal or Paxos product and cannot be used inside PayPal or Venmo. It is a claim on the upper issuer, backed by a claim on MoonPay's PYUSD holdings. That is a different instrument, whatever the brand on the front. The framework in stablecoin payments counterparty risk applies layer by layer.

"We already accept USDC. Why does PYUSDx matter to us?"

Because your counterparties will increasingly hold something else. The number of new stablecoins reaching $10 million in supply rose 89% year over year in 2025, before PYUSDx made issuance a configuration task. An acceptance policy that only takes one asset on one chain will be renegotiated every quarter. Accept across networks and auto-convert into the one you want, and the policy never changes.