walletpermissions
Request types · Not part of ERC-20; OpenZeppelin 4.x extension

Increase allowance (increaseAllowance)

A function some tokens offer that adds to an existing allowance instead of replacing it. The number in the request is the amount added, not the new total.

Request: increaseAllowance(spender, addedValue)

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 in the prompt

  • The function name: increaseAllowance, not approve.
  • The amount: it is added on top of whatever the spender is already allowed.
  • The spender and the token, as with any approval.

What it lets the other party do

  • It raises the spender’s allowance. OpenZeppelin 4.x documents it as: “Atomically increases the allowance granted to spender by the caller.” The new total is the old allowance plus the added amount.
  • The spender can then use transferFrom up to that new total.

What it does not do

  • It is not in the ERC-20 standard. OpenZeppelin removed it in Contracts 5.0.0 (released 2023-10-05): “Removed the non-standard increaseAllowance and decreaseAllowance functions.” Older tokens built on 4.x can still have it; tokens without it reject the call.
  • It does not move tokens and does not set an expiry.

How long it lasts

  • Like any ERC-20 allowance: no expiry, until used up or replaced.

How to undo it

  • The standard route is approve(spender, 0), which sets the total to 0 whatever it was.
  • Check your real approvals with Revoke.cash or Etherscan’s token approval checker.

A pattern to recognise

  • A small number in an increaseAllowance prompt can sit on top of a large existing allowance. The small number is not the total.
Fictional practice

Practice question

Fictional Pebble Pass already has an allowance of 500 LEAF from you. It now asks for one more step.

Fictional request card
Request type
Transaction: increaseAllowance
Token
LEAF (fictional)
Spender
Pebble Pass Vault (fictional contract)
Amount in the call
20 LEAF
Existing allowance
500 LEAF

After this request, is Pebble Pass Vault limited to 20 LEAF?

Show the answer

Answer: No. increaseAllowance adds to the existing allowance. The vault would be allowed 520 LEAF in total.

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. OpenZeppelin Contracts changelog, 5.0.0 (2023-10-05). OpenZeppelin. 5.0.0 released 2023-10-05. Checked 2026-11-04.
  2. OpenZeppelin Contracts 4.9.6 ERC20.sol (increaseAllowance). OpenZeppelin. Tag v4.9.6. Checked 2026-11-04.
  3. ERC-20: Token Standard. Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04.

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