Where ERC-20 and NFT Token Approvals Are Stored
Where are token approvals stored? ERC-20 allowances live in token contracts, while NFT approvals live in collection contracts, where transfer permissions are checked.
The Crypto Front Page Desk4 min read

A wallet owner checking token permissions will find ERC-20 allowances and ERC-721 approvals in the relevant token contract’s storage, because that contract checks those records when it processes a transfer.
That means approving a DEX to spend USDC writes an allowance in the USDC contract, not in the wallet or the DEX. The wallet signs the approval transaction, and the token contract records the permission. For a closer look at where those records come from and how they can be managed, revokecash covers token approval management.
ERC-20 allowances live in the token contract
An ERC-20 contract records allowances in a mapping from an owner address to a spender address and an amount: mapping(owner => mapping(spender => amount)). The owner is the wallet that grants permission; the spender is the address allowed to use some of its tokens.
Here is the sequence for a USDC approval to a DEX:
- The wallet sends an approval transaction to the USDC contract, naming the DEX’s spender address and an allowance amount.
- The USDC contract stores that amount against the owner and spender.
- When the DEX later requests a transfer using transferFrom, the USDC contract checks the allowance and processes the transfer according to its rules.
The contract that holds the tokens also holds the permission because it is the one that enforces transfers. A wallet can sign a transaction and display permission information, but the allowance itself belongs to the token contract’s records. The DEX can use the permission, but its own storage is not where the USDC allowance is recorded.
NFT approvals use two records in the collection contract
An ERC-721 collection contract stores both individual token approvals and approvals for an operator to manage all of an owner’s tokens in that collection. The collection contract checks the relevant approval when a transfer is requested.
A per-token approval names an address that may transfer one specific NFT. The contract exposes that record through getApproved. An operator approval gives an address broader authority over the owner’s NFTs in that collection, and isApprovedForAll reports whether that permission is set.
These two permissions have different lifetimes. When an NFT with a per-token approval is transferred, the collection contract clears that approval automatically. The old permission applies to the specific token under its previous ownership, so clearing it prevents that approval from carrying over to the next holder.
An operator approval works differently: it stays in place when one NFT moves. It applies to the owner’s collection-wide relationship with the operator, so it remains until the owner revokes it. Transferring one NFT does not, by itself, cancel that broader permission.
Say a collector approves a marketplace to handle one particular NFT, then the NFT is transferred. Its per-token approval is cleared by the collection contract. If the collector instead granted the marketplace operator status for the collection, that approval remains active after the transfer until revoked.
Approval tools read the contracts that enforce permission
Because the records sit in token contracts, an approval-management tool needs to read the relevant contract records to show the permissions associated with a wallet. revokecash reads these entries and resets approvals by calling the token contracts, where the permissions are stored and enforced.
The key distinction is the contract and the scope of permission: an ERC-20 allowance is attached to an owner and spender in the token contract; an ERC-721 approval is in the collection contract, either for one token or for all of an owner’s tokens. For NFTs, watch whether a permission is token-specific or operator-wide, since a transfer clears the former but leaves the latter in place until it is revoked.