BEP-20

Overview

Understand the idea

BEP-20 defines common functions and events for fungible tokens on BNB Smart Chain. Contracts expose balances, total supply, transfers, allowances, and approvals through an interface closely aligned with ERC-20, allowing wallets and decentralized applications to integrate tokens consistently.

Compatibility does not make every BEP-20 token trustworthy or economically equivalent. Contracts can contain minting, pausing, transfer restrictions, fees, proxies, blacklists, or malicious logic. Tokens with the same symbol may also exist at many unrelated contract addresses.

Payment systems should identify a token by chain ID and verified contract address, then confirm decimals and transfer behavior. Deposit monitoring must parse canonical Transfer events and final receipts. Approval flows should minimize allowances and warn users before granting a contract broad spending authority.

What actually happens

BEP-20 describes a fungible-token interface used on BNB Smart Chain, closely related to the ERC-20 conventions on Ethereum. Because both environments use EVM-style addresses, an identical address string can appear valid on both chains. That similarity is a convenience for wallet software but a recurring source of payment errors when a payer selects the wrong network.

A BEP-20 token contract keeps a ledger of balances and exposes methods such as transfer, balanceOf and allowance. A wallet signs a BNB Smart Chain transaction invoking that contract, and the gas fee is paid in the chain's native asset. Events help indexers discover successful transfers, but payment processors should also verify the transaction receipt and exact contract. Token supply, freeze permissions or transaction taxes depend on individual contracts, not on the BEP-20 label.

Decisions and failure cases

Some tokens are bridged representations, not the issuer's preferred native form. Test token decimals, fee-on-transfer behavior, upgradeability and contract authenticity. A wallet showing a balance does not prove that the merchant supports deposits for that contract and chain combination.

Related concepts

BEP-2, BEP-721, BEP-1155.

Further reading

BNB Chain developer documentation.