SubEtha v2
Your x402 customers keep paying the same way. The public chain stops showing a stream of payments into your address.
Customers pay zUSDC (wrapped USDC) with the unmodified official x402 client. Each order uses a
different receiving address instead of one fixed payTo. Payer, amount, token and transaction
time stay public. The zERC20 v2 SDK is designed not to link that address directly to the
merchant’s shielded funds on chain; this property has not been independently quantified, and
correlation remains possible.
SubEtha v2 is offered as testnet design-partner work. This page is the overview; the Provider guide, the buyer page and the status page carry the details and the dated records.
What this means for buyers
Section titled “What this means for buyers”A purchase method that makes it harder to tell, from public payments, which service a customer uses. The buyer keeps the unmodified official x402 client; no SubEtha client is required to pay.
What this may mean for Providers
Section titled “What this may mean for Providers”These are hypotheses, not measured results:
- Customers who care about this may prefer you, or keep using you, over a service whose inflows are visible as a stream into one address.
- Your revenue stream and customer mix may be less exposed on the public chain, because no
single fixed
payTocollects every order.
What the documented integration keeps and what it changes is listed on the Provider guide.
How a purchase works
Section titled “How a purchase works”- The wire is standard x402 v2
exact. The 402 advertisesscheme: "exact", the payment network, the asset, the amount andpayTo. The buyer signs a standard EIP-3009transferWithAuthorizationwith the unmodified official client (@x402/fetchand@x402/evm2.28.0). No SubEtha client is required to pay. payTois a fresh per-order address. For every 402 the facilitator obtains a new burn-sale address from the zERC20 v2PointOfSaleand binds the order to it. The payment is a public zUSDC transfer from the payer to that address.- Delivery on the mined receipt; chain finality later. The body is released after the
facilitator re-validates the mined receipt: one
AuthorizationUsed, one transfer of the order amount to the order’s address, on time by block time. Chain finality is later and separate from delivery. On the hosted testnet, delivery follows the mined receipt without a finality gate; a reorg or an ASP rejection can occur after delivery, so body delivery does not guarantee merchant credit or spendability. - Recovery needs no second payment. The order id and a recovery URL travel in
extensions.subetha.info. The wallet that paid recovers with the official SIWX extension; the recovery route accepts no payment. Recovery depends on retained order state, and the hosted service promises no retention.
Buyer Provider Facilitator x402 relay public chain(official x402 client) (official middleware + extension) (POS key only) (delegated) | | | | | |-- GET paid resource ----->|-- create order -------------------->| per-order address | | |<- 402: exact, zUSDC, |<-- orderId + requirements ----------| from the POS key | | | payTo = that address | | | | |-- sign EIP-3009, retry -->|-- verify -------------------------->| | | | | your handler runs; output is held | | | | |-- settle -------------------------->|-- relay signed auth ->|-- broadcast -->| payer -> per-order | |<-- release after the mined receipt -|<-- mined receipt -----| | burn address |<- 200 + body + receipt ---| is re-validated | | | (public zUSDC transfer)Configuration shown: hosted testnet (since 2026-11-09). The facilitator holds only each Provider’s POS key and signs no transaction (what the operator sees and can still do is stated in full under Who sees what); settlement is relayed to a delegated x402 facilitator, which broadcasts and pays gas; delivery follows the mined receipt with no finality gate. A self-run facilitator is a different configuration and is described separately below and on the Provider guide.
Two different “v2”s. “SubEtha v2” is the product. “x402 v2” is the wire version of the official x402 packages. “zERC20 v2” is the settlement SDK deployment. The numbers are unrelated.
Who sees what
Section titled “Who sees what”| What | Who sees it |
|---|---|
| Payer address, amount, token, the per-order burn address, time of the settle transaction | Everyone (public chain) |
| Which API was bought, and by which wallet | The buyer, for its own purchases. The Provider, for its own orders, including the authorization identity. |
| Which merchant’s shielded funds a per-order burn address feeds | Not directly linked on the public chain. This is a property of the zERC20 v2 SDK design and is not independently quantified. |
| Public withdrawals from the shielded funds | Everyone (public chain) |
Hosted testnet. The facilitator operator sees, per order, the payer address, amount,
transaction, digest and Provider. It holds only each Provider’s POS key: it can derive addresses,
write that Provider’s lane, and know which addresses are the Provider’s. It cannot spend. It holds
no seed and no view key. The Provider trusts the payTo the facilitator hands out at 402 time and
audits afterwards with its own view key. The operator could still withhold orders, attribute an
order to another Provider, or hand out an address that is not the Provider’s; the audit finds this
after the fact.
Self-run facilitator. The operator holds the merchant and broadcaster keys and sees the merchant wallet’s whole activity.
Correlation remains. Timing, amounts, the merchant’s other activity and the size of the anonymity set can suggest a link between a per-order address and a merchant. The evidence does not quantify identification accuracy. Public withdrawals from the shielded funds are public.
About amounts. zERC20 also has a separate send path with different properties for the paid amount; those properties do not carry over to the burn-sale path used here, where the amount is public.
What you need
Section titled “What you need”- Customers need zUSDC (wrapped USDC). Wrapping is a public step; on the hosted testnet it is
test USDC wrapped on Base Sepolia (
eip155:84532). See What buyers do. - Providers keep the official Express middleware and mount the SubEtha extension around an existing handler; the documented integration is Express on Node. See For Providers.
- The extension and the Provider tools install from the npm registry at exact versions, checked against the integrity values on Register and run a Provider; approved applicants also receive them as tarballs with their invite code, and design partners can get an authorized checkout on request. See source access and licence.
Where it stands
Section titled “Where it stands”The repository’s own records, by date: two bounded public Sepolia runs on 2026-10-31 and 2026-11-01; a capacity measurement on 2026-11-08; the switch to the multi-Provider Base Sepolia hosted configuration on 2026-11-09 with one public purchase verifying relay, delivery and recovery. These are historical records, not a current availability check. The status page lists them with their verification limits.
SubEtha and the Router
Section titled “SubEtha and the Router”The SubEtha Router is a separate product with its own page: per that page, an MCP server that lets an agent pay on one testnet rail and reach a paid API on another, testnet-only and unaudited. The Provider-side path described on this page is not the Router.
Nothing on these pages establishes privacy properties for purchases made through the Router, including any effect of buying an ordinary Provider through the Router on the visibility of that Provider’s upstream settlement. Router purchase results are not evidence for the Provider-side property described here.
Router integration with SubEtha v2 is outside the verification scope of the documented path; no integration or roadmap promise is made.
- For Providers: adopt alongside x402
- What buyers do
- Status and verification
- The landing page: for Providers and contact
Reviewed 2026-11-16 against the product repository at e972064; re-read on 2026-11-18 against 68e061b, which changes only the quickstart’s and the operations notes’ funding and probe text. Evidence is the product
repository’s own records; this site made no payment for this page.