PayPal's dollar is now four wrappers deep

What Is PYUSDx, and How Many Wrappers Deep Is Your Dollar?

When a builder mints a branded dollar on PYUSDx, the token in a user's wallet sits four contractual layers above the Treasury bills that actually back it. Counting those layers is the whole exercise.

PYUSDx is an issuance platform, not a consumer stablecoin. A developer's custom ERC-20 is backed 1:1 by PYUSDx; PYUSDx is backed 1:1 by PayPal USD held by MoonPay Digital Assets Limited; PYUSD is issued by Paxos Trust Company against U.S. dollar deposits, Treasuries and cash equivalents — four layers from wallet to reserve . PayPal, M0 and MoonPay announced the platform on February 25, 2026 , deployed mainnet contracts on Ethereum and Arbitrum on June 2, 2026 and added Monad on August 12, 2026 , then ran the public ecosystem launch on September 9, 2026 with three live issuers and more than $100 million in combined processed volume . Read that as throughput, not market cap or circulating supply — the split is not disclosed .

The plumbing is deliberately uniform. Core contracts deploy at deterministic addresses that are identical across Ethereum, Arbitrum and Monad: the PYUSDx token at 0xeBDB0942cE16386Ab90718C7BD10C91CDb66b14d, SwapFacility at 0x0bC305e7e13113cAEd3f5486849e9518a1cC4173, and ExtensionFactory at 0x25c8aFfC5a63D8E047c12918C0438ABA5aA09c2A, with supply minted and burned through a time-delayed IssuerGateway operated by M0 .

The Four-Layer Reserve Chain, From Your Token to the Treasury Bill

A PYUSDx-derived token sits four layers above the actual dollar assets that back it, and each layer has a different holder, a different legal entity and a different disclosure standard. A builder's custom token is redeemable against PYUSDx; PYUSDx is redeemable against PYUSD; PYUSD is redeemable against a reserve of U.S. dollar deposits and Treasuries; and that reserve is what an auditor actually looks at. Only the bottom layer carries independent attestation . Everything above it inherits that reporting by reference, not by audit.

Layer 1 — the builder's extension token. This is whatever the issuing application calls its dollar: USDat, concUSD, cUSD, CUSD. It is deployed through M0's ExtensionFactory at a deterministic address in a single transaction and is backed 1:1 by PYUSDx held by the SwapFacility. Conversion runs through swapIn and swapOut, with a swapExtensions call moving directly between two custom tokens — no spread, and no separate liquidity pool for the builder to fund . The practical consequence is that a holder of a Layer 1 token depends on that builder's contract roles — freeze manager, pauser, version manager — remaining honest and uncompromised.

Layer 2 — PYUSDx. An upgradeable, non-rebasing ERC-20 with six decimals to match PYUSD, carrying per-account reward accrual. Yield accrues continuously on the underlying position but is only added to supply when claimed, so balances never rebase . The PYUSD backing PYUSDx is held by MoonPay Digital Assets Limited, a British Virgin Islands entity, which mints and burns the token . There is no monthly attestation of that holding equivalent to what exists one layer below.

Layer 3 — PYUSD. Issued by Paxos Trust Company, N.A. — not by PayPal, and not by Venmo. Paxos states PYUSD is backed 1:1, with reserves held entirely in U.S. dollar deposits, U.S. Treasuries and cash equivalents, segregated in bankruptcy-remote accounts . PYUSD itself dates to August 7, 2023 and reached 70 markets on March 17, 2026 .

Layer 4 — the reserve reporting. Paxos publishes monthly reserve reports with independent attestations: KPMG LLP for reports dated on or after February 28, 2025, and WithumSmith+Brown for earlier periods . That reporting covers PYUSD. A Layer 1 token is two wrappers removed from it — the attestation says nothing about whether MoonPay's BVI entity holds the PYUSD it claims, or whether a builder's extension supply matches its PYUSDx collateral.

The chain is only as strong as its weakest disclosure, and the weakest disclosure is not at the bottom. Independent commentators have made the same point about PayPal's dollar stack from the consumer side (video: Anthony Pompliano). For a trader sizing exposure, the question is not whether Treasuries back the structure — they do — but how many unattested balance sheets sit between your token and those Treasuries.

Who's Actually Liable If a Layer Breaks?

Liability in the PYUSDx stack is split across three separate legal entities, and none of them is PayPal. MoonPay Digital Assets Limited, a British Virgin Islands entity, is the named issuer of PYUSDx and holds the PYUSD that backs it . Paxos Trust Company, N.A. issues the underlying PYUSD . M0 writes and operates the contracts but never touches the reserve. The builder issuing the top-layer token is responsible for its own licensing. If something breaks, which entity you can make a claim against depends entirely on which layer failed — and on whether you were ever a counterparty to it in the first place.

M0's role is infrastructural. It controls the base PYUSDx token, the IssuerGateway that mints and burns supply under time-delayed operations, the SwapFacility, bridge adapters, template implementations, and the switch that enables yield accrual on a partner token . That is meaningful operational power over whether tokens move, wrap, and earn. It is not custody. A contract bug, a stalled bridge adapter, or a paused SwapFacility is an M0 surface; a shortfall in the PYUSD sitting behind PYUSDx is not.

The custody question lands on MoonPay, and its terms narrow who can act on it. Minting and redemption are restricted to accepted Eligible Counterparties — a downstream holder who acquired PYUSDx from someone else has no automatic direct redemption right against MoonPay . Redemption, when available, is 1:1 into PYUSD only, never into fiat or another asset, and may be declined or deferred for legal, operational, supported-chain, or third-party infrastructure reasons. MoonPay also reserves freeze, seizure, suspension, and chain-support powers, and caps its liability at the lesser of US$20,000 or the face value of the mint or redemption request at issue . For an institution moving eight figures, a $20,000 ceiling is a rounding error, not a remedy.

PayPal's position is the one most often misread. PayPal supplies the reserve asset and the brand gravity, but it is not the issuer at any layer — its own arrangement has always run through Paxos. The launch release is blunt about the boundary: PYUSDx tokens are "not PayPal USD, not PayPal products, and not affiliated with PayPal or Paxos," and cannot be stored, sent, or received in PayPal or Venmo accounts . The same terms bar issuers from calling PYUSDx a "payment stablecoin" under the GENIUS Act, permitting only "PYUSD-backed stablecoin" or another approved description .

"Licensing and regulatory treatment vary by jurisdiction and are the responsibility of the individual issuer," per the joint MoonPay, M0 and PayPal announcement (source: PR Newswire, 2026-02).

The practical takeaway: whatever comfort you draw from PayPal's consumer-facing dollar — the 70-market rollout of March 17, 2026 , the Paxos attestation cadence, the app-level dispute paths — does not travel up the stack. Extension tokens inherit the collateral, not the protections.

YieldToOne vs. MultiMint: Which Issuance Template Fits a Builder's Use Case

A builder issuing a PYUSDx-backed token picks one of two audited templates, and the choice comes down to a single question: does the product need to accept collateral other than PYUSDx? YieldToOne is the simpler template — it routes all reward yield accruing on the underlying PYUSDx to a single treasury address the partner selects . MultiMint does the same but additionally accepts approved alternative stablecoins as backing, each under its own per-asset cap . Both ship with the same compliance primitives: account freezing, forced transfer out of frozen accounts, and a global pause.

The yield mechanics are identical under both. Rewards accrue continuously on the underlying PYUSDx but are added to supply only when claimed, so holder balances never rebase — a design choice that keeps the token a plain non-rebasing ERC-20 with 6 decimals, matching PYUSD's precision . For a builder, that means the float is a treasury line item, not something distributed automatically to holders. Whether end users see any of it is a policy decision made off-contract.

The MultiMint asymmetry deserves attention before a builder commits: alternative stablecoins go in, but unwrapping through SwapFacility always returns PYUSDx. The template widens the on-ramp without widening the redemption path, which means the issuer absorbs any basis risk between the accepted assets and PYUSDx. Per-asset caps exist precisely to bound that exposure, and the asset cap manager role is the control surface for tuning it.

Deployment itself is short. ExtensionFactory deploys a partner token at a deterministic address in a single transaction . The prerequisites list is what actually gates timing: a funded deployer wallet, an admin address (preferably a multisig), operational role addresses, a treasury address for yield, testnet PYUSDx, and an initial call with M0 . That last item is the reason this is not pure self-service. The documented sequence runs: scope template, chains and reward structure with M0; assign the independent roles; deploy on testnet — Ethereum Sepolia, Arbitrum Sepolia or Monad Testnet; test wrap/unwrap, bridging, freeze, pause and reward claiming; share the token address with M0, which registers it as an earning contract so accrual switches on; then replicate to mainnet chain by chain. M0's own marketing frames this as "build to launch in days, not months" , and the contract work plausibly supports that — the registration handoff and the initial call do not.

Role separation is the substantive control the builder retains. Five independent roles are assigned under YieldToOne — admin, yield manager, freeze manager, pauser and version manager — with a sixth, asset cap manager, added for MultiMint . The division of authority is clean and worth stating plainly:

• Builder controls: role assignment, claim timing and destination, freeze and pause policy, upgrade pinning against the ExtensionBeacon registry, and MultiMint per-asset caps.
• M0 controls: the base PYUSDx token and its issuance through the time-delayed IssuerGateway, SwapFacility, bridge adapters (LayerZero is the first), template implementations, and yield enablement .

Version pinning is the item builders most often underweight. Because implementations sit behind a beacon registry, a template upgrade can change behavior under a live token unless the version manager pins deliberately. For a product holding user balances, that is a governance decision, not a maintenance chore — and it belongs in the same review cycle as the multisig policy on the admin address.

Three Live Issuers, $100M+ in Volume: What's Actually Working

Three issuers were live on PYUSDx as of September 9, 2026, together representing more than $100 million in processed volume . That number is throughput — value moved through the platform — not market capitalization and not revenue, and M0 has not disclosed how it splits between circulating supply and cumulative flow . For anyone sizing adoption, the per-issuer circulating figures are the more useful anchor.

• Saturn — USDat, roughly $65 million circulating. Saturn is a Bitcoin-backed structured finance protocol, and USDat is its everyday liquidity and settlement dollar. A companion token, sUSDat, carries exposure to STRC preferred equity rather than sitting flat .
• Cap — cUSD, roughly $92 million circulating. Cap runs a covered-credit platform and uses cUSD as its native platform currency, having migrated the token to PYUSD backing .
• Concrete — concUSD. Concrete supplies on-chain vault infrastructure; its flagship stable vault holds over $800 million in stablecoin strategies. concUSD is reward-bearing and can be deposited into vaults such as sconcUSD .

The common thread is that none of these are consumer payment dollars. All three are internal units of account for platforms that already had balance-sheet activity — credit, structured products, vault strategies — and that previously had to rent a stablecoin from someone else. The wrap-and-unwrap design gives them a branded token whose reward yield routes to their own treasury, without funding a liquidity pool to defend the peg. That is the specific problem PYUSDx solves well today, and it is narrower than "any business can issue a dollar."

"Stablecoin issuance is moving to the application layer," M0, MoonPay and PayPal argued when they introduced the platform in February 2026, pointing to an 89% rise during 2025 in the number of newly issued stablecoins carrying more than $10 million in supply (source: PR Newswire, 2026-02).

Two more names sit in the pipeline rather than in the live count. USD.AI, the first developer named at preview stage, is building an application-specific dollar for AI infrastructure financing and is migrating its USDai token to PYUSDx. Fairblock is building Confidential USD (CUSD), which supports both confidential and public transfers . Neither has published circulating supply, so treat them as announced intent.

The backdrop matters for calibration. Stablecoin circulation first crossed $300 billion in October 2025 and monthly transfer volume reached roughly $7.2 trillion in early 2026 . Against that, $100 million in processed volume is a rounding error — under 0.002% of a single month's transfers. Retail traders watching for a PYUSD demand impulse should note that base PYUSD supply moved the other way over the same window: third-party trackers put it near $4.09 billion around March 18, 2026, then roughly 31% lower near $2.76 billion in late August 2026, though those are aggregator estimates and Paxos's own transparency page is the authoritative source . Extension issuance is not yet large enough to reverse that trend.

Decision Framework: Launch a PYUSDx Extension, Hold PYUSD, or Skip Both?

The right choice depends on which of three roles you occupy: builder, holder, or consumer. Launch a PYUSDx extension if you run an application that already moves dollars on-chain and wants branded settlement rails plus the float yield. Hold PYUSD if you want the shorter reserve chain and the in-app rewards rate. Skip both if you need regulated-stablecoin consumer protections — M0's own documentation does not describe PYUSDx as a regulated stablecoin, and MoonPay's terms explicitly prohibit calling it a "payment stablecoin" under the GENIUS Act .

Launch an extension if: the economics point one layer out. M0's framing of the platform is that float economics which historically accrued to the stablecoin issuer now sit with the builder — the entity that deploys the token, chooses the treasury address, and decides when yield gets claimed . That only converts into real revenue if your product generates persistent balances rather than transient ones. Concrete checks before committing: you can staff six independent role addresses (admin, yield manager, freeze manager, pauser, version manager, and an asset cap manager for MultiMint) ; you are not headquartered in a Restricted Jurisdiction, a list that includes the United States, EEA member states, Canada, India and Australia ; and you accept that licensing is the individual issuer's responsibility, not MoonPay's or PayPal's .

Hold PYUSD directly if: you want fewer counterparties between you and the collateral. Base PYUSD is issued by Paxos Trust Company with reserves in U.S. dollar deposits, Treasuries and cash equivalents held in segregated, bankruptcy-remote accounts, with monthly attestations from KPMG for reports dated on or after February 28, 2025 . It is also the only layer of the stack that PayPal and Venmo accounts actually recognize — PYUSDx and extension tokens cannot be stored, sent or received there . PayPal extended PYUSD access to 70 markets on March 17, 2026, with eligible users earning rewards on holdings . Rewards rates are variable and jurisdiction-dependent; verify the current figure in-app rather than assuming a headline number holds.

Skip both if: you are a downstream consumer expecting redemption rights. Minting and redemption are limited to accepted Eligible Counterparties, redemption is 1:1 into PYUSD only — never fiat — and requests may be declined or deferred for legal, operational or chain-support reasons . Freeze, forced transfer and global pause are configurable roles held by the builder, not by PayPal or Paxos . Skeptics have been arguing for years that centralized freeze authority is the material risk in bank-adjacent dollar tokens (video: Crypto Tips); the extension model does not remove that authority, it distributes it to more parties.

The metric to watch is velocity, not supply. M0's own yardstick is blunt: if a PYUSDx token's velocity is still at DeFi levels a year out, it has not left the building. Extension tokens circulating mainly between vaults and lending markets are collateral wrappers; extension tokens moving through payroll, merchant settlement or remittance corridors are payment rails. Today's cohort — USDat near $65 million, cUSD near $92 million, and more than $100 million in processed volume as of September 9, 2026 — sits firmly in the first category. Revisit this decision when a named issuer publishes transaction counts rather than balances.

Why PayPal Needed a Platform, Not Just a Token

PayPal built an issuance platform because the single-token strategy stopped compounding. PYUSD circulation sat near $2.76 billion in late August 2026, down roughly 31–35% from a peak above $4.09 billion around March 18, 2026, according to third-party trackers — aggregator figures, with Paxos's transparency page the authoritative source. A shrinking float on a consumer-distributed asset argues for changing the distribution model, not the reserve.

The original thesis was reach. When PayPal launched PYUSD on Ethereum on August 7, 2023, the pitch rested on roughly 426–430 million active PayPal accounts as a built-in wallet base . Three years later that arithmetic had not converted. PayPal kept widening the surface — Arbitrum as the first Layer 2 on July 17, 2025, with transaction costs typically under $0.01 , then availability across 70 markets in Asia-Pacific, Europe, Latin America and North America on March 17, 2026, including Colombia, Peru, Singapore and the UK . Geographic expansion moved the footprint; it did not durably move the float, which contracted through Q2 2026 anyway.

The organizational signal matched the product one. PayPal reorganized crypto into a dedicated business unit in August 2026, weeks before the PYUSDx commercial launch on September 9, 2026 . May Zabaneh, PayPal's SVP and GM of Crypto, framed the shift in terms that concede the point directly:

"The stablecoin market is maturing fast. What separates the next phase from the last isn't the asset. It's what companies can do with it," — May Zabaneh, SVP and GM of Crypto, PayPal (source: Chainwire, 2026-09).

Read structurally, that is an admission that PYUSD lost the commodity-stablecoin race and is repositioning as reserve collateral for other people's tokens. The supporting market data points the same way: the number of newly issued stablecoins holding more than $10 million in supply rose 89% during 2025 , while stablecoin circulation crossed $300 billion in October 2025 and monthly transfer volume reached about $7.2 trillion in early 2026 . Issuance fragmented; demand did not consolidate around a third consumer dollar.

For a trader, the practical consequence is that PYUSD's demand driver changes shape. Under the old model, PYUSD supply tracked PayPal and Venmo user uptake — a metric outside crypto's view. Under the platform model, supply tracks how much collateral builders lock to back extension tokens, which is observable on-chain through the M0 PYUSDx contracts. Skeptical takes on the consumer-side proposition remain worth hearing before assuming distribution alone solves adoption (video: Anthony Pompliano). The open question is whether B2B collateral demand refills a float that lost roughly $1.3 billion in five months.

The Fine Print: What PYUSDx Tokens Are Not

PYUSDx tokens are not PayPal products. The launch release states plainly that tokens issued through the platform are "not PayPal USD, not PayPal products, and not affiliated with PayPal or Paxos," and that they cannot be stored, sent or received in PayPal or Venmo accounts . M0 says official PayPal integrations will open as circulation grows , but nothing of the sort exists today. A builder token wrapping PYUSDx sits two layers away from anything a PayPal consumer account recognizes.

Attestation coverage stops well short of the full chain. Paxos publishes monthly reserve reports on PYUSD with independent attestations — KPMG LLP for reports dated on or after February 28, 2025, and WithumSmith+Brown for earlier periods . That covers layer four. It does not cover MoonPay Digital Assets Limited's PYUSD holdings behind PYUSDx, and it does not cover whatever a builder does with its own extension token. Per-token reporting varies by issuer and implementation; there is no single attestation spanning builder token → PYUSDx → PYUSD → Treasuries. Treat reserve transparency as four separate disclosure regimes, not one.

The compliance primitives are real and configurable. Both audited templates ship with account freezing, forced transfer out of frozen accounts, and a global pause, assigned to distinct roles a builder controls . Above that, MoonPay's terms (last updated August 5, 2026) reserve broad freeze, seizure, suspension and chain-support powers, cap liability at the lesser of US$20,000 or the face value of the mint/redemption request, restrict mint and redeem to accepted Eligible Counterparties, and prohibit describing PYUSDx as a "payment stablecoin" under the GENIUS Act . Restricted Jurisdictions in those terms include the United States, EEA member states, Canada, India and Australia .

The concrete takeaway: read the layer you actually hold. If you hold PYUSD in a PayPal or Venmo account across the 70 markets PayPal opened on March 17, 2026 , PayPal's terms and Paxos's attestations govern you. If you hold a builder's extension token, they do not — your recourse runs through that builder's disclosures and MoonPay's counterparty terms. Before touching any PYUSDx-derived token, confirm three things: who can freeze your balance, whether you have a direct redemption right, and where the reserve report for your specific layer is published.

Watch / Sources

• Anthony Pompliano — Watch This BEFORE Using PayPal Stablecoin
• Crypto Tips — PayPal's Stablecoin Is DANGEROUS! Here's Why
• CBS News — PayPal expanding cryptocurrency offerings with new stablecoin, PYUSD

Frequently asked questions

Is PYUSDx the same as PYUSD?

No. They are separate tokens with separate issuers. PayPal USD (PYUSD) is issued by Paxos Trust Company, N.A. and carries PayPal's brand; it is the reserve asset at the base of the chain . PYUSDx is minted and burned by MoonPay Digital Assets Limited, a British Virgin Islands entity that holds the PYUSD backing it, and it exists to back third-party builder tokens rather than to be held as a consumer dollar . The full stack runs four layers deep: a builder's custom ERC-20 → PYUSDx (MoonPay) → PYUSD (Paxos) → U.S. dollar deposits, Treasuries and cash equivalents. The launch release is explicit that PYUSDx-based tokens are "not PayPal USD, not PayPal products, and not affiliated with PayPal or Paxos" .

Who backs a PYUSDx-based token if the issuer fails?

Backing is a chain, and each link has a different obligor. A builder token is backed 1:1 by PYUSDx held by that builder; PYUSDx is backed 1:1 by PYUSD held by MoonPay Digital Assets Limited; PYUSD is backed by Paxos, which states reserves are held 100% in U.S. dollar deposits, U.S. Treasuries and cash equivalents in segregated, bankruptcy-remote accounts . Paxos publishes monthly reserve reports with independent attestations — KPMG LLP for reports dated on or after February 28, 2025, and WithumSmith+Brown for earlier ones . What that chain does not give you is a direct claim upward. MoonPay's terms restrict minting and redemption to accepted Eligible Counterparties, so a downstream holder who acquired PYUSDx through a counterparty has no automatic mint or redeem right against MoonPay, and redemption is 1:1 into PYUSD only — never fiat or another asset . Builder-layer tokens are covered by the builder's own terms, not PayPal's or Paxos's.

Can I hold PYUSDx or a PYUSDx-derived token in my PayPal or Venmo wallet?

No. PYUSDx and tokens built on it cannot be stored, sent or received in PayPal or Venmo accounts — that exclusion is stated directly in the launch materials . Only PYUSD itself functions inside PayPal and Venmo, and PayPal extended PYUSD availability to 70 markets across Asia-Pacific, Europe, Latin America and North America on March 17, 2026, with eligible users earning rewards on holdings . M0 has said official PayPal integrations will open as circulation grows, but no such support exists today . Treat consumer-wallet compatibility as a future possibility, not a current feature.

What's the difference between YieldToOne and MultiMint templates?

Both are audited issuance templates documented by M0, and both mint a partner token backed 1:1 by PYUSDx with the same compliance primitives — account freezing, forced transfer out of frozen accounts, and a global pause . YieldToOne routes all reward yield accruing on the underlying PYUSDx to a single treasury address the partner chooses. MultiMint does the same but additionally accepts other approved stablecoins as backing under per-asset caps managed by a dedicated asset cap manager role, which is why MultiMint deployments require six independent role addresses rather than five . In both cases unwrapping goes back to PYUSDx through the SwapFacility at 1:1 with no spread and no separate liquidity pool to fund, and yield never rebases holder balances — it is added to supply only when claimed .

How fast can a business launch a branded stablecoin on PYUSDx?

M0 markets the platform as "build to launch in days, not months," and the deployment step itself is a single transaction: deployYieldToOne or deployMultiMint through the ExtensionFactory, which places the token at a deterministic address . The full sequence is longer than one call, though, and it is not fully self-service. Prerequisites are a funded deployer wallet, an admin address (preferably a multisig), operational role addresses, a treasury address for yield, testnet PYUSDx, and an initial scoping call with M0. After testnet deployment on Ethereum Sepolia, Arbitrum Sepolia or Monad Testnet, the builder tests wrap/unwrap, bridging, freeze, pause and reward claiming, then shares the token address with M0, which must register it as an earning contract before yield accrual switches on — a managed gate, not an automated one . Mainnet replication then happens chain by chain across Ethereum, Arbitrum and Monad. One more constraint often missed: MoonPay's terms list Restricted Jurisdictions including the United States, EEA member states, Canada, India and Australia, and licensing is the individual issuer's responsibility .

Last updated: 2026-09-11. Reviewed against MoonPay's PYUSDx terms (updated August 5, 2026), M0's platform documentation, and Paxos transparency disclosures.

Enjoyed this article? Subscribe to get new stories by email whenever they're published.

Subscribe