How x402 Payments Work

x402 lets a service charge for a request at the moment you use it. You do not need a subscription or an API key for a Marketplace request.

The payment flow

1. You request a paid resource, such as a market-data endpoint.
2. Naven returns a 402 Payment Required response with the exact payment terms.
3. Your wallet shows the network, token, recipient, and maximum amount.
4. After you approve, your client signs the payment and repeats the request automatically.
5. Naven verifies the payment, settles it, and returns the requested result.

Only approve a payment when the wallet shows the expected Naven resource, network, token, and price.

What you need

• A wallet connected to the network requested by the product.
• Enough of the displayed payment token to cover the request.
• A small amount of the network's native token for transaction fees when your wallet requires it.

For Marketplace and Genesis, Naven currently requests USDG on Robinhood Chain. The payment request in your wallet is the source of truth for the amount and recipient.

If a request does not complete

• Confirm that your wallet is connected to the requested network.
• Check that you have enough USDG and native gas token.
• Reject any payment request whose resource or amount differs from what you selected.
• Retry the request after reconnecting the wallet if the wallet approval window was closed.

For a developer integration, see the Buyer/Client Guide. For a ready-to-use interface, open the Naven Marketplace.