Pago402 payer cockpit (anvil staging)

Config

API base URL Anvil RPC URL (reachable from this browser) Forked network (must match the fork profile the stack runs) Settlement asset (deposit rail — must match the invoice currency) Settlement token (blank = canonical contract for network + asset) x402 slug (paywalled resource / payment link) Payment-link slug (hosted crypto pay) Stream slug (resource group or streamable link) Subscription plan id (uuid) Tenant API key (subscription panel only) Test wallet

1 · x402 paywall pay

GET the 402 challenge, sign an EIP-3009 transferWithAuthorization over its terms, POST it back, collect the signed receipt.

Prereqs (operator, once)

2 · Payment-link crypto pay

Resolve → redeem into an invoice → initialize a payment on the network and asset set in Config → send that amount to the deposit address from the test wallet. The asset must match the invoice currency. To pay an invoice that already exists — one raised from the dashboard, say — skip the first two buttons and paste its id (or its pay.pago402.com/invoice/… URL) into Invoice id. Leave Amount to send blank to pay exactly what Init quoted, or put a figure in it to underpay or overpay the invoice on purpose.

Prereqs (operator, once)

Deposit detection is Moralis-webhook driven and Moralis cannot see a fork, so anvil-deposit-watcher relays the transfer into the real /webhook/stream and mines to the confirmation depth. The invoice does reach PAID — but only on the Polygon profile, and only while the watcher's WATCHER_TOKENS lists the token being sent. Without it the transfer mines and is never relayed: the money is gone and the invoice sits PENDING.

Invoice id Amount to send

3 · Superfluid stream open / close

Quote → grant the operator flow permissions on the CFAv1Forwarder → sign the StreamIntent → open → watch runway → close. Uses the wallet's USDCx (seeded for wallet #0).

Prereqs (operator, once)

Stream id Stream key

4 · Subscription crypto allowance

Create a subscription on a CRYPTO_ALLOWANCE plan, read the mandate instructions, approve the USDC allowance, confirm.

payerAddress at confirm must equal the subscription's payerReference. This page always subscribes with the selected wallet's address as payerReference, so keep the same wallet selected from create through confirm.

Prereqs (operator, once)

Subscription id

5 · Faucet — fund any wallet

The four panels above pay from the dev accounts. To pay from a wallet you hold — MetaMask, an SDK, a script — give it gas and stablecoins here. This writes the fork's storage directly, the way the seeder funds the dev accounts; it refuses to run against anything that is not anvil. The tokens funded are the settlement asset from Config plus, on Polygon, the other stablecoins the deposit rail accepts.

Use a wallet that holds nothing on the real Polygon. The sandbox keeps Polygon's chain id 137 and its real token contracts, so to your wallet it is Polygon:

a payment you sign here is also a valid instruction on the real chain, and anyone who sees it could submit it there;
MetaMask merges this network into its existing Polygon entry and may send through the real Polygon RPC — a "sandbox" transfer from a funded account then moves real money;
an address you use here exists on the real chain too, so never send anything real to it.

Make a fresh account for the sandbox, fund it only here, and never fund or use it on the real Polygon — not now, not later: a transfer you send here stays valid there. The sandbox resets at 03:00 UTC; balances minted here are gone by morning.

Wallet address

Stablecoins per token Gas