Glossary

What is Permit2?

Permit2 is Uniswap's contract for signature-based token approvals and transfers for any ERC-20. How it works, and its role as x402's fallback on EVM.

Permit2 is a contract from Uniswap that lets token holders authorise transfers and allowances with signatures, for any ERC-20 token, after a single on-chain approval of the Permit2 contract per token.

How does it work?

Uniswap describes Permit2 as two contracts in one. SignatureTransfer authorises a single transfer through one signature, scoped by a nonce, so the permission ends when that transfer runs; its nonces are unordered and tracked in a bitmap, so signatures can be used in any order. AllowanceTransfer sets a standing allowance for a spender, and unlike a plain ERC-20 allowance, each one carries an expiration after which it is invalid. Before either works, the holder approves the Permit2 contract through the token contract once. Permit2 works with any ERC-20, including tokens that will never support EIP-2612 permits, and Uniswap deploys it at the same address on every chain it supports except zkSync. x402's exact scheme on EVM networks names Permit2 as its universal fallback for tokens without EIP-3009. The client signs a permitWitnessTransferFrom message whose spender is x402's own proxy contract rather than the facilitator, and the proxy only sends funds to the recipient named in the signed witness data. If the payer hasn't approved Permit2 yet, the spec has the verifier return 412 Precondition Failed with PERMIT2_ALLOWANCE_REQUIRED, and describes ways to supply that approval, including a direct transaction or an EIP-2612 permit.

In practice

The one-time approval to Permit2 is a real allowance and deserves the same care as any other: it lets Permit2, and whoever holds a valid signature, move that token. After that, read each Permit2 signature request for the token, amount, spender, deadline and, for witness transfers, the recipient. Prefer short deadlines. Signature-based approvals are a common phishing route, because a signature costs nothing to give and looks less serious than a transaction.

What it does not mean

  • Signing a Permit2 message can move tokens even though no transaction appears in your wallet at that moment.
  • Permit2 isn't EIP-2612. EIP-2612 permits are built into a token; Permit2 is a separate contract that works with any ERC-20.
  • It isn't specific to Uniswap swaps. Any contract can integrate it, x402's proxy among them.
  • Revoking a Permit2 allowance doesn't remove your underlying approval of the Permit2 contract; that's a separate ERC-20 approval.

Where does Veyra fit?

Veyra doesn't use Permit2. Auto-pay on Pro and Team draws on a plain, capped ERC-20 USDC allowance from your wallet to Veyra's relayer on Base, which Veyra builds and your wallet signs and submits; it can be revoked by approving zero.

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.