Glossary

What is EIP-3009 transferWithAuthorization?

EIP-3009 lets a token holder sign one transfer that someone else submits and pays gas for. How it works, its nonces, and its role in x402.

EIP-3009 is an Ethereum token standard proposal that lets the holder of an ERC-20 token sign an authorisation for one specific transfer, which anyone can then submit on-chain with transferWithAuthorization.

How does it work?

Under plain ERC-20, moving tokens needs either a transaction from the holder, who must pay gas, or a standing allowance to a spender. EIP-3009 adds a third route. The holder signs an EIP-712 typed message naming from, to, value, a validity window (validAfter and validBefore) and a nonce. A relayer submits that signature with transferWithAuthorization and pays the gas. The token contract checks the signature, the window and the nonce, then moves exactly that amount to exactly that recipient. The signature's domain includes the token contract and chain ID, so it can't be replayed on another contract or network. The standard uses random 32-byte nonces rather than sequential ones, so a holder can sign several authorisations at once without them failing for being out of order; authorizationState reports whether a nonce has been used, and the optional cancelAuthorization lets a holder cancel one before it runs. It also defines receiveWithAuthorization, which only the payee may submit, to stop front-running when a contract is the recipient. EIP-3009 is still marked Draft on eips.ethereum.org, and only tokens that implement it support it; its text notes it is not meant for smart contract accounts, which can call transfer and approve directly. x402's exact scheme on EVM chains uses it. The client signs an EIP-3009 authorisation, a facilitator verifies it and calls transferWithAuthorization, and because the signature fixes the amount and recipient, the facilitator can't change either. The x402 spec recommends EIP-3009 for tokens that support it and makes it the default when the server doesn't name a transfer method.

In practice

For a payer, an EIP-3009 authorisation is narrower than an allowance: one amount, one recipient, one time window. Read all three before signing, and keep validBefore short. For a service accepting payments, it means you can receive tokens without the payer holding gas, as long as someone submits the authorisation; check the token supports it before relying on it.

What it does not mean

  • It isn't a standing allowance. Each signature authorises one transfer and its nonce can't be reused.
  • Signing isn't paying until someone submits it within the validity window.
  • Not every ERC-20 supports it. The token contract must implement the functions.
  • It isn't specific to x402; x402's exact scheme is one user of it.

Where does Veyra fit?

Veyra doesn't use EIP-3009 and isn't an x402 client or facilitator. On paid plans its auto-pay uses a capped ERC-20 allowance to its relayer, which is why it requires a recipient allowlist; otherwise you sign each payment in your own wallet from a one-tap approval link.

Veyra's spend policy for one agent endpoint: per-transaction limit, daily limit, auto-approve limit, ask-up-to limit and recipient allowlist
What this looks like in Veyra: one spend policy per agent endpoint, with a per-payment cap, a daily cap, an auto-approve band, an ask band and a recipient allowlist, all checked on the server. Try the free policy generator →

Sources

Guides that use this term

This page explains how agent payments and the related technology work. It is not financial, investment, legal or tax advice. Protocols and provider features change; check the linked official sources before relying on a detail.