walletpermissions
Agent permissions · x402 protocol v2; ERC-3009

An x402 pay-per-request payment vs a standing allowance

An agent pays for one API request by signing a single, exact transfer. Compare that with an approval that lets a service charge you again and again.

Request: x402 PAYMENT-SIGNATURE (exact scheme on EVM)

Education only: this page does not assess any real request, wallet or app, and is not advice to sign or not sign. Checked against the sources below on November 4, 2026. Drafted with AI assistance and awaiting human review against the cited standards. Markdown version

What to read

  • x402 flow: a server answers with a payment required signal, and the client “submits a signed payment authorization in the subsequent request.”
  • In the exact scheme with ERC-3009, the authorization names from, to, value, validAfter, validBefore and a unique nonce.
  • The asset transfer method. The exact scheme lists ERC-3009, Permit2 and ERC-7710.

What the limit covers

  • For ERC-3009 and Permit2 in the exact scheme, the spec lists the usage as “One-time use”, and says “the Facilitator cannot modify the amount or destination.”
  • The upto scheme is different: the client “authorizes a maximum amount”, and the server settles “for the actual amount used”, up to that maximum.

What it does not cover

  • The Permit2 method needs a one-time ERC-20 approval of the Permit2 contract first. That approval is a standing allowance, separate from each payment.
  • The ERC-7710 method in the exact scheme is listed as “One-time use and multi-use”. Read which one you are granting.
  • Whether the response was worth paying for. The signature pays; it does not judge the result.

How to stop it

  • An unused one-time authorization stops working after validBefore.
  • A standing allowance, including an approval of Permit2, stays until you set it to 0. Check with Revoke.cash or Etherscan’s token approval checker.
Fictional practice

Practice question

Your fictional research agent pays a fictional API 0.01 DOLLR for one answer, using x402’s exact scheme with ERC-3009.

Fictional request card
Scheme
exact (EVM, eip3009)
to
Datawell API payee (fictional)
value
0.01 DOLLR
validBefore
60 seconds from now
nonce
unique

Can Datawell use this same signature to charge another 0.01 DOLLR tomorrow?

Show the answer

Answer: No. The authorization is for one transfer, with a unique nonce and a short validity window. A second charge needs a new signature. A standing allowance would not need one.

Check your real account elsewhere

This site never connects to a wallet and never asks for an address. To see or remove approvals on a real account, use an established tool:

Independent tools, not affiliated with this site. Linking is not an endorsement or a safety assessment.

Sources

  1. x402 protocol specification, version 2. x402 on GitHub. Protocol version 2; main branch on the check date. Checked 2026-11-04.
  2. x402 scheme: exact on EVM. x402 on GitHub. Last changed 2026-10-15. Checked 2026-11-04.
  3. x402 scheme: upto on EVM. x402 on GitHub. main branch on the check date. Checked 2026-11-04.
  4. ERC-3009: Transfer With Authorization. Ethereum ERCs. Draft; created 2020-09-28. Checked 2026-11-04.

Quotes are from these sources. Found an error? Corrections are logged publicly on the changelog.