Zambo guide
x402 Payment Failed
Most x402 failures come from wrong network, wrong asset, or too little balance, and each one shows up in the 402 response.
Add Zambo to your AIReading a 402 response
- The client requests a protected resource.
- The server returns payment instructions instead of the resource.
- The wallet reviews and authorizes the payment.
- The client retries the request and inspects the response.
The payment response and the returned work should be checked separately.
Common causes
Most x402 failures come from wrong network, wrong asset, or too little balance, and each one shows up in the 402 response.
Check the current request terms and wallet response before proceeding. Payment, tool execution and the saved work receipt are distinct records.
Retrying cleanly
Start with a small, non-sensitive request and review the payment prompt before authorizing it. After the client returns a result, open the linked receipt and compare the recorded status with the response you received.
Never approve a charge just to test a checkout flow.
Try this prompt
Start with a small request. Change the details to match your task.
Use Zambo to explain the payment step before it happens, then show the receipt for the completed request.
FAQ
What is x402 payment failed?
Most x402 failures come from wrong network, wrong asset, or too little balance, and each one shows up in the 402 response.
What does a Zambo receipt show?
It shows the saved record and its available status. It does not prove that the output is correct or complete.
How do I try this with Zambo?
Check the payment request in your wallet, approve only a request you intend to pay, then review the resulting receipt.
Try it with your AI
Connect Zambo once, then ask your AI to use it for a real task.
Add Zambo to your AI Try Zambo Chat