Refunds, and why there is no chargeback

What happens when you pay

Your agent signs an EIP-3009 transferWithAuthorization for an amount we quoted. A facilitator recovers your address from that signature, simulates the transfer and broadcasts it. USDC moves from the address that signed to our receiving address, on Base.

We never hold your key, never sign on your behalf, and cannot change the amount or the recipient: both sit inside what you signed. We also cannot take a second payment from your wallet on our own initiative. Every charge starts with a signature from you.

You pay no gas. The amount that leaves your wallet is the plan price exactly, as quoted in the 402.

There is no chargeback and no dispute button

A card payment can be pulled back by the card network months later. This one cannot be pulled back by anyone. The x402 exact scheme settles a token transfer on a public chain, and a settled transfer is final. There is no intermediary holding the funds and no arbitration step.

That cuts both ways, and we would rather say so plainly than let you discover it: we cannot take money back from you after a settlement either, and you cannot take it back from us. Anything below that looks like a refund is us deciding to send USDC back.

Your receipt is the transaction

A successful purchase returns a transaction field: the settlement’s on-chain identifier. Keep it. It is what lets us look up the same event you are looking at.

That field is present and empty in one case, and it is not an error. If your authorization had already been settled by an earlier attempt whose outcome we never learned, we grant the plan without a fresh receipt rather than charge you again. The purchase is complete — you have the key, the plan and the expiry — and the receipt is the transfer in your own wallet history: your address, our receiving address, the amount and the time. We never substitute a placeholder value there, because a fake hash is worse than an empty one.

What is not a double charge

Purchases are idempotent on the pair of your payer address and the nonce inside the authorization you signed. Retrying a purchase that timed out, with the same signed authorization, returns the original result and moves no further money. If a request appears to have failed, send the same authorization again rather than signing a new one, and do it promptly: the key comes back with that result only for a limited period after the purchase. This is a retry path for an agent whose response was lost. It is not a way to recover a key you have lost, and no such way exists.

Signing a new authorization is a new purchase, and it does move money:

• Sent with your API key, it buys another plan window for the team you already have. The windows stack, and the one expiring soonest is spent first.
• Sent without your API key, it creates a new team with its own key and its own sending address. It does not add capacity to the account you already own, and the two cannot be merged afterwards.

That second case is the most common way to spend money you did not mean to spend. If it happens, tell us — it is on the short list of things we will look at.

Nothing renews, so there is nothing to cancel

A plan is a fixed number of sends over a fixed window. It does not auto-renew, there is no overage bill, and no subscription exists to cancel. You stop by not buying again. When the window ends or the sends run out, the next call answers 402 with a fresh quote you are free to ignore.

Unused sends expire with the window. They are not credited, carried over or refunded.

What we will consider refunding

Refunds are discretionary and handled by a person, one at a time. We will look at a request where:

• a payment settled and the plan was never granted, and it stayed that way — the purchase path is built to re-drive this on its own, so tell us if it does not;
• our error caused a duplicate purchase, rather than a second authorization you signed;
• we suspended or terminated your account for a reason that turns out to be ours rather than yours.

We will not normally refund:

• a change of mind, or a plan bought by an agent you deployed;
• unused volume, or a window you let expire;
• an account suspended or terminated for breaching the acceptable use policy;
• a second purchase made without an API key that created a second team, where the volume was delivered as sold.

How to ask

Write to [SUPPORT EMAIL ADDRESS] with the payer address, the plan, the approximate time, and the transaction identifier if you have one. There is no refund button in the dashboard and no ticketing system behind that address. If we agree to a refund, it is a manual USDC transfer we send back.

We refund only to the address that paid. That address is the whole proof of purchase we have: there is no email on the account, no password and no name, so a request from any other address is one we cannot verify. If you no longer control the paying address, we cannot pay you back.

We do not promise a response time or a settlement time, and we will not pretend to. If mandatory consumer law where you live gives you rights this page does not offer, those rights apply and this page does not limit them.

Who this is with

The service is operated by [LEGAL ENTITY NAME], registered in [JURISDICTION] at [REGISTERED ADDRESS]. These refund terms form part of the terms of service.