Can I get a refund on an x402 payment?
Short answer
Not automatically. A standard x402 payment is a push payment, and the x402 documentation calls it irreversible once executed. There is no chargeback. A refund happens only if the seller sends the money back as a new transfer. Two newer schemes, batch-settlement and auth-capture, define refunds and holds, but they are not yet in wide use.
Why there is no "undo"
With a card, the bank sits between you and the shop and can pull a payment back. With the exact scheme, which almost every x402 endpoint uses, nobody sits in between. Your signature authorizes a token transfer from your wallet to the seller's, and once the blockchain has processed it, it is done.
The x402 FAQ puts it this way: the exact scheme is a push payment and is "irreversible once executed".
The facilitator cannot reverse it either. It never holds the money.
What a refund looks like
The seller sends a new transfer back to the address that paid. That is the whole mechanism. It depends on the seller agreeing.
So the practical question is not "can x402 refund me?" but "will this seller refund me?"
If you paid and got nothing useful
- Check that the payment settled. The
PAYMENT-RESPONSEheader on the reply is your receipt. It says whether settlement succeeded and gives the transaction reference. If the payment failed, no money moved. See x402 error codes. - Keep the receipt. The transaction reference and the paying address are what a seller needs to find your payment.
- Contact the seller. Look for a support address in their documentation or terms.
- Limit the next one. If a seller does not respond, stop calling it. Losses in x402 are usually small because prices are small, but an agent in a loop can repeat a bad purchase many times.
Schemes that build in refunds
| Scheme | What it offers | Availability |
|---|---|---|
exact | Nothing. Refunds are a separate transfer from the seller | Everywhere |
batch-settlement | The buyer funds a balance. The FAQ says it defines cooperative refunds and timed withdrawals on EVM | EVM and Solana in the SDKs |
auth-capture | A hold that the seller can capture, void or refund | Specified for EVM only |
See payment schemes for how each works.
For sellers
- Decide your policy and publish it. Buyers and agents have no other way to know.
- Refund to the payer address shown in your settlement record, in the same token and on the same network.
- Do not charge for failures you caused. In the default flow you verify, deliver, then settle. If your handler fails, you can decline to settle, and the buyer is never charged.
- Consider
uptofor work with an unknown cost. The buyer authorizes a ceiling and you settle only what was used, which removes one common reason for refunds.
Reducing the need for refunds
- Check the price and recipient first with the 402 checker.
- Set a maximum price per request in your client.
- Prefer sellers that name their operator and publish terms.
- Keep only a small balance in the wallet an agent uses. More in is x402 safe?
Sources
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.