How to revoke token approvals on BNB Chain for one token
To revoke token approvals on BNB Chain, select BNB Smart Chain, submit a wallet-signed revocation, then confirm the allowance is zero on-chain with BNB gas ready.
By Crypto Docket Newsroom#9ccc415 min read

A confirmed revocation sets the selected BEP-20 allowance on BNB Smart Chain to zero, replacing the wallet’s earlier permission for that token–spender pair. You need the wallet that granted the permission and enough BNB for gas; revoking one allowance leaves other permissions unchanged.
That distinction matters because BNB Smart Chain and opBNB keep separate approval states, even though both use BNB for gas. A permission granted on one network does not describe the wallet’s permission on the other, so match the network to the transaction history you want to change.
Revoke one allowance and verify the on-chain change
Start with the unwanted BNB Smart Chain allowance. Identify the token and the contract allowed to spend it before you submit anything. An allowance is a token-specific spending permission, so the same wallet can have separate permissions for different tokens and spenders. The revokecash checker is a concrete example of an approval-management tool: it lets you inspect BNB Chain approvals and revoke a selected permission.
Select the network and find the token–spender pair. Choose BNB Smart Chain, not opBNB, then load the wallet address whose permissions you want to review. BNB Smart Chain mainnet uses chain ID 56 and BNB for gas. The network choice sets which chain’s approval state you are inspecting; choosing opBNB would show a different state, even for the same wallet and token name.
Suppose Mira wants to remove an old permission for a BEP-20 token on BNB Smart Chain. She checks the wallet address, chooses BNB Smart Chain, and locates the row matching both the token and the spender contract. At this point, she has identified the permission but has not changed it.
Connect the wallet that owns the permission. Use the account that originally granted the allowance. A different wallet cannot change that account’s token permission. Before continuing, check that the wallet is connected to BNB Smart Chain and keep BNB available to pay the transaction’s gas. The revocation is an on-chain transaction, so the wallet must be able to sign it and the account must be able to submit it.
Mira connects the owning account and checks the selected token and spender again. This leaves the permission unchanged, but makes the right account available to authorize the transaction. If the wallet shows a different network, switch it to BNB Smart Chain before requesting revocation.
Review the allowance, then request revocation. Confirm that the selected entry is the unwanted token–spender permission. A single-token revocation changes that allowance; it does not revoke every permission for the wallet. Submit the revocation through the connected wallet and approve the transaction there. The permission remains in place while the transaction is pending. revokecash can help identify and manage the approval, while the owning wallet provides the signature that authorizes the change.
Mira reviews the pair once more and signs the request. The wallet now has a submitted transaction, but she waits for it to complete before treating the allowance as removed.
Verify success on BscScan and refresh the permission. Find the transaction on BscScan and confirm that its receipt shows success on BNB Smart Chain. A confirmed transaction changes the on-chain permission; a submitted or pending one does not yet establish the result. Then refresh the approval information and check that the same token–spender allowance reads zero. The zero value is the completion condition: the selected contract no longer has that allowance to spend.
Mira sees a successful receipt, refreshes the permission, and confirms that the chosen allowance is zero. Other token–spender entries may still have nonzero allowances, because her action targeted only this pair. If the receipt fails or the allowance remains nonzero after refresh, the task is not complete; inspect the transaction result and current network before trying again.
The result depends on three things being in place: the correct chain, the owning wallet’s signature, and a successful transaction. Each links the permission change to the intended account and network. The trade-off is straightforward: revocation removes the selected spending permission, while a later use of that contract may require a fresh approval and another transaction. Keep the network and the receipt status in view as you verify the change.
Related questions
How do I revoke NFT approvals on BNB Chain?
NFT collection operator permissions are separate from a BEP-20 token allowance. Use the corresponding NFT revocation for the collection permission you want to remove, then verify that permission on the relevant chain.
Does revoking an approval withdraw staked tokens?
No. Revocation changes a contract’s token-spending permission. Withdrawing staked assets follows the staking protocol’s separate process, so check its withdrawal conditions and use its withdrawal action if that is your goal.
Can I use a dapp after revoking an approval?
You may need to grant a new approval before the dapp can spend that token again. Revocation removes the existing permission; it does not prevent a later approval signed by the wallet.
- Select BNB Smart Chain and locate the intended token–spender allowance.
- Use the owning wallet, with BNB available for gas, to submit revocation.
- Confirm a successful BscScan receipt and a refreshed allowance of zero.