This demo shows how NuOrbit lets a user pay in USDC / USDT from any supported chain and returns an x402 payment proof. Your app uses that proof to unlock access, credit usage, or mark an invoice as paid.
It’s built for SaaS, API and AI platforms, gaming, marketplaces, and token-gated products that want every chain’s users to be paying users – without building per-chain payment rails.
When the checkout opens, you’ll choose which chain to pay from. NuOrbit reads your USDC / USDT balance on that chain and prepares the payment.
In production, your app wouldn’t care which chain the user picked – it would only see the x402 proof that a valid payment happened.
You’ll need testnet USDC / USDT on the chain you plan to pay from. Once funded, the checkout will prompt for a one-time approval and then a payment.
These links are placeholders – replace them with your actual faucet URLs. You only need enough to cover a small demo payment. In production flows, you can abstract this away from users.
In a real product, these values would map to plans, SKUs, or entitlements. Here you can tweak them and see how the proof responds.
Leave any field blank to fall back to demo defaults. In production, this is where you pass your own plan IDs, user IDs, or invoice references.
Launch the checkout popup to start the payment. Inside the popup you can choose which chain to pay from, and NuOrbit will verify the stablecoin transfer on that chain.
In this mode, NuOrbit does not execute any target-chain contract. It only verifies payment and prepares the x402 receipt.
Your back-end can treat the proof as the canonical record of payment, regardless of which chain the user picked:
To see how the proof is structured and how it flows through the registry, check the technical demo / x402 page.