BNB Smart Chain addresses

BEP20 Address: Format, Validation and Creating One via API

A BEP20 address is the 42-character, 0x-prefixed hexadecimal identifier of an account on BNB Smart Chain. One address holds BNB and every BEP-20 token. It has the same format as an Ethereum address because BSC is EVM-compatible, and it is not the same as a BEP-2 address, which starts with bnb1.

7-day free trial — no card, no KYC to start Non-custodial — private keys stay under your control Plans start at €49/month (€490/year) — view plans and rate limits

To get a BEP20 address, generate a key pair in a wallet or call POST /api/v2/bsc/addresses. The result is a 0x string of 42 characters. You can publish it to receive deposits, because it is derived from the public key and only the private key can spend from it.

This page explains the format, how BEP-20 differs from BEP-2, and how to create and watch addresses over REST. The BEP20 address guide on the blog goes deeper on checksums.

What does a BEP20 address look like?

A BEP20 address looks like 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed: the prefix 0x followed by 40 hexadecimal characters. Those 40 characters are 20 bytes. Per the ethereum.org accounts documentation, an externally owned account address is the last 20 bytes of the Keccak-256 hash of its public key, written with a 0x in front. BNB Smart Chain runs the Ethereum Virtual Machine, so it reuses this scheme unchanged.

Mixed upper and lower case is deliberate. EIP-55 defines a checksum that capitalizes some of the letters, so a wallet can detect most typing errors. An all-lowercase address is still valid, it simply carries no checksum.

0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed 1 2 3
  1. The 0x prefix marks the value as hexadecimal.
  2. The 40 hexadecimal characters are 20 bytes: the last 20 bytes of the Keccak-256 hash of the public key.
  3. 42 characters in total. The mix of upper and lower case letters is the EIP-55 checksum.
Anatomy of an EVM address. BNB Smart Chain and Ethereum share this layout.

How does BEP-20 differ from BEP-2 and ERC-20?

BEP-20 is the token standard of BNB Smart Chain. The BEP-20 specification says it is derived from Ethereum's ERC-20 and adds support for transfers between BNB Beacon Chain and BNB Smart Chain. The functions are the same ones: balanceOf, transfer, approve and the related events.

BEP-2 is a different standard. It belongs to BNB Beacon Chain, formerly Binance Chain, and its addresses start with bnb1 instead of 0x. A BEP-2 asset cannot be sent to a 0x address directly. Moving value between the two chains takes a cross-chain transfer, so check which network a deposit screen asks for.

An Ethereum address and a BEP20 address look identical, yet they live on different networks. The same private key controls the same string on both chains. A transfer only reaches the chain it was broadcast to.

Does one BEP20 address hold BNB and every BEP-20 token?

Yes. One address is one account on BNB Smart Chain, and it holds native BNB and every BEP-20 token at the same time. A token balance is not stored on the address itself. The token's smart contract keeps a mapping from address to balance, and balanceOf(address) reads it.

Do not confuse a wallet address with a token contract address. Both are 42-character 0x strings, and nothing in the string tells them apart. The contract address identifies which token moves, and it must never be the destination of a transfer. Tokens sent to a contract address are in most cases lost.

A wallet that holds BEP-20 tokens also needs a little BNB. Gas on BNB Smart Chain is paid in BNB, so a token balance alone cannot move.

Create and watch a BEP20 address over REST

Instead of generating an address in a wallet app and copying it into your backend, the BSC API creates and imports addresses directly. A webhook then tells you when a deposit lands.

EndpointWhat it does
POST /api/v2/bsc/addressesGenerate a new BEP20 address
POST /api/v2/bsc/addresses/importImport an existing private key so the API can sign for that address
GET /api/v2/bsc/addressesList the addresses stored in your account
GET /api/v2/bsc/balances/{address}BNB balance of the address
GET /api/v2/bsc/balances/{address}/bep20/{contract_address}Balance of one BEP-20 token
POST /api/v2/bsc/webhooksRegister a webhook so a deposit to the address triggers an HMAC-signed callback
GET /api/v2/bsc/webhooks/notificationsList past deposit notifications for reconciliation

Watching an address needs no private key. Only sending from it does. Keep your deposit addresses watch-only and import a key only for the hot wallet that pays out. The API documents address fields as 0x followed by exactly 40 hexadecimal characters, so a malformed string is rejected.

Create an address and watch it for BEP-20 deposits

Both calls need a Bearer token. Add X-Network: testnet to rehearse on BSC testnet first.

cURL
curl -X POST https://app.chaingateway.io/api/v2/bsc/addresses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"password": "a-strong-password-per-wallet"}'

curl -X POST https://app.chaingateway.io/api/v2/bsc/webhooks \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-backend.example/hooks/bsc",
    "to": "0xYourDepositAddress",
    "type": "BEP20",
    "contractaddress": "0xTokenContract",
    "reference": "customer-4711"
  }'

How do I validate a BEP20 address before sending?

Run three checks before you broadcast a payout. First, match the string against ^0x[a-fA-F0-9]{40}$, which rejects wrong lengths and stray characters. Second, if the address contains both upper and lower case letters, verify the EIP-55 checksum, because a single wrong letter then fails the check.

Third, confirm the network. A 0x address is valid on every EVM chain, so the format check cannot tell you whether the recipient expects BSC, Ethereum or Polygon. Ask the user for the network explicitly, and send a small first transfer to any new payout address.

The address validator runs the format and checksum checks in the browser if you want to test a single address by hand.

Sources

Checked on 5 November 2026.

Need addresses at scale rather than one at a time? Create a free account and generate a batch of BEP20 addresses in testnet — 7-day trial, no card, no KYC.

FAQ: BEP20 addresses

A 42-character, 0x-prefixed hexadecimal string that identifies an account on BNB Smart Chain, holding BNB and any BEP-20 token. It's derived the same way as an Ethereum address, which is why the two chains share the same format.

A BEP20 address is BNB Smart Chain's address format (0x-prefixed, EVM-style). BEP-2 is a separate, older standard on BNB Beacon Chain with addresses that start with bnb1. They are not interchangeable — check which chain a deposit request is actually asking for before sending.

The format is identical, but the network is not. The same private key produces the same-looking 0x address on both Ethereum and BSC, yet funds sent on one chain don't exist on the other — you need to broadcast the transaction on the chain the recipient actually expects.

POST /api/v2/bsc/addresses generates one over the API. Registering a webhook on that address means your backend gets an HMAC-signed notification the moment a BNB or BEP-20 deposit arrives, with no polling required.

Yes. One BEP20 address holds native BNB and every BEP-20 token — USDT, USDC, a project's own token — at the same address. Balances per token are tracked by each token's smart contract, not by the address itself.

Ready to build on BNB Smart Chain?

Create an account and generate a testnet BEP20 address in minutes — 7-day trial, no card, no KYC. Full endpoint reference in the BSC API docs, or cover all seven chains with the multi-chain blockchain API.

Reviewed by Maurice Sobiera How we write these pages