pandaPay-per-request services: how x402 works
Work through the four checks below, then use the related tools or contact support if an account-specific question remains.
Follow one request
A client requests a resource, receives payment requirements, decides whether to pay, and submits verifiable payment information. The service verifies it and delivers the resource. Networks and verification arrangements depend on the implementation.
Compare with subscriptions
Paying per request can reduce the need to buy a large plan in advance. It is not always cheaper: count requests, unit prices, network costs and retries, and establish refund or dispute arrangements.
Limit automated payments
Allow specific services and set per-request and total budgets. Verify the quoted asset, price and recipient. Instructions embedded in a webpage must not become wallet authorisation.
Ask before enabling it
What is delivered after payment? Are failed requests charged? Can a retry charge again? Who verifies payment and handles disputes? Resolve these questions before allowing unattended payments.
This is an independently written practical guide. Product availability, network support and exchange terms can change. Verify the relevant product screen before acting; examples are not live quotes.