Token standard
BEP-20 Token Standard
BEP-20 is the BSC version of Ethereum’s most common standard, ERC-20. BEP-20 is a technical specification providing a flexible format for developers to create a range of different tokens. Using BNB Smart Chain development, BEP-20 token transfers are fueled with BNB.
Work with BEP-20 tokens via the CryptoAPIs API
Read BEP-20 token transfers, balances, and metadata across the chains CryptoAPIs supports — through one unified REST API, with no node to run.
Token transfers
List full BEP-20 token transfer history for any token contract or address, with pagination and real-time updates.
Token balances
Read current BEP-20 token holdings for any address in a single call.
Contract metadata
Get token contract details — symbol, name, decimals, and total supply — for any supported token.
BEP-20 in use
BEP-20 follows the ERC-20 of Ethereum but enjoys lower fees. Tokens made to the BEP-20 standard can include utility tokens, stablecoins, security tokens, or “Peggy Coins”, tokens built using the BEP20 standard and pegged to different assets.
ERC-20
ERC-721
TRC-20
TRC-721Frequently Asked Questions
Which blockchain does BEP-20 run on?
BEP-20 settles on BNB Smart Chain. BEP-20 is deliberately ERC-20 compatible, so the same contract calls work — the practical difference is the chain it settles on, and therefore the endpoint's chain parameter rather than its shape.
What kind of token standard is BEP-20?
It is a fungible-token interface, BSC's counterpart to ERC-20.
Can I test BEP-20 without spending real funds?
Yes — the same endpoints serve BNB Smart Chain's BSC testnet testnet, so you can build and verify an integration end to end before you touch mainnet.
How do I read BEP-20 balances and transfers?
Use Address Latest for current state and recent activity — it needs no setup and answers for roughly the last 14 days. For a full history, Address History requires the address to be synced first, which then bills per address per day for as long as it stays synced.
What does reading BEP-20 data cost?
It depends on the endpoint family rather than on BEP-20 itself: single-record calls are charged per request, while list endpoints are charged per page returned, and a synced address adds a daily monitoring charge. The pricing calculator has the current per-chain figures.
Build with BEP-20 tokens on CryptoAPIs
Now that you know what BEP-20 is, integrate it: read BEP-20 token transfers, balances, and contract metadata across supported chains through one REST API.