On 9 July 2026, PayPal USD (PYUSD) became natively issued on Polygon through Paxos, and landed inside Polygon’s Open Money Stack. That combination matters more than another “stablecoin on chain X” headline: native issuance removes bridge risk, and the Open Money Stack turns the token into something payment teams can plug into without assembling wallets, ramps, and compliance from scratch.
This article explains what native issuance changes, how the Open Money Stack fits, and what builders should take from PayPal’s third major chain expansion after Ethereum and Solana.
Native issuance vs a bridged token
A bridged (or wrapped) stablecoin is a claim sitting on chain B that represents tokens locked on chain A. Users move value by locking and minting across a bridge. A natively issued stablecoin is minted and redeemed by the issuer on that chain directly.
| Property | Bridged PYUSD | Native PYUSD on Polygon |
|---|---|---|
| Who mints | Bridge / wrapper contract | Paxos under its OCC trust charter |
| Redemption path | Unwrap on origin chain, then redeem | Redeem with issuer on Polygon |
| Bridge failure mode | Locked collateral, stalled unwraps | Issuer operational / reserve risk only |
| Compliance story | Token + bridge + issuer | Token + issuer |
| Integration complexity | Extra hop for treasury and audits | Same rails as other Polygon stablecoins |
Think of a bridged token as a traveler’s cheque denominated in another country’s currency: useful, but you still depend on the issuing desk back home. Native issuance is opening a local branch — the same regulated dollar, minted where the payments run.
For institutional payment flows, “native” is not a marketing adjective. It is a shorter liability chain and a cleaner audit trail.
Polygon Labs has said the network settles more than $2.5 billion in stablecoin volume daily. PYUSD’s share on Polygon was still tiny relative to Ethereum and Solana at launch — DefiLlama figures around the announcement put Polygon near 0.4% of PYUSD supply. The bet is distribution through payment infrastructure, not existing on-chain inventory.
What the Open Money Stack actually is
Polygon’s Open Money Stack (OMS) packages the pieces payment products usually wire together separately: wallets, fiat on-ramps and off-ramps, compliance tooling, and cross-chain routing, exposed as a single integration surface.
With PYUSD native on that stack, a business can — in principle — take money in from a card, bank account, or exchange balance, hold and move PYUSD across borders, and cash out to local currency without stitching three vendors together for issuance, compliance, and settlement.
Paxos issues PYUSD under a national trust charter supervised by the OCC. That framing is deliberate: the product pitch to enterprises is “federally regulated dollar on a high-volume payments network,” not “another DeFi farm token.”
Marc Boiron (Polygon Labs) and Peter Jonas (Paxos) both leaned on the same idea in public remarks: a stablecoin is only as useful as the places it can go and what businesses can do when it arrives. Issuance without distribution is inventory. Distribution without a trusted issuer is a compliance headache.
Why PayPal keeps adding chains
PYUSD already lived on Ethereum and Solana, with further multichain expansion over 2024–2026. Polygon is the payments-oriented bet: lower fees and faster confirmation for the kinds of merchant and remittance flows PayPal already understands.
The strategic pattern matches what other regulated issuers do:
- Establish the regulatory wrapper (Paxos trust charter, dollar reserves).
- Issue where settlement volume already exists (Ethereum for depth, Solana for speed/cost, Polygon for payment stack density).
- Attach to developer tooling so fintechs do not rebuild ramps and KYC for every chain.
PayPal is not trying to win DeFi TVL rankings with PYUSD. It is trying to make a PayPal-branded dollar usable inside the rails where businesses already move stablecoins for payins and payouts.
What this means for builders
If you ship payments, wallets, or remittance products on Polygon:
- Prefer native PYUSD contracts and issuer redemption paths over any remaining bridged representation.
- Treat OMS as a product decision: one integration vs composing your own ramp + wallet + compliance stack.
- Design for issuer risk, not bridge risk — reserves, redemption SLAs, and OCC trust constraints become your operational assumptions.
- Do not assume Polygon PYUSD liquidity matches Ethereum or Solana yet; plan for inventory, market makers, and cash-out corridors explicitly.
If you are multichain already, add Polygon as a payments region, not as a speculative farm. The useful metric is settlement completion time and fiat conversion cost, not tweet volume on launch day.
Conclusion
Native PYUSD on Polygon is a distribution play for a regulated dollar: Paxos mints on the chain, and the Open Money Stack tries to make that dollar callable from ordinary payment software. Bridged tokens got ecosystems started; native issuance is what payment teams ask for when the money has to look institutional.
The story to watch next is not market-cap share on day one. It is whether merchants and fintechs already on Polygon’s payment tooling actually settle invoices and payouts in PYUSD — and whether redemption and fiat off-ramps keep up when they do.