Deposit addresses · BNB
BNB deposit addresses for your users.
Give every one of your users a permanent BNB address they can deposit to any time. It is computed in advance, it has no private key, and we sweep it and pay the network fee to do so. BNB Chain's native coin, on the chain with our cheapest sweeps.
BNB on 1 chain.
Enable the ones your users need. Each gives that user their own address, and enabling a new one later gives it to the users you already have.
- BNB on BNB Chain
- USDT and USDC have 18 decimals on BNB Chain, where they have 6 almost everywhere else. Read decimals from the API rather than writing 6 into your code — getting it wrong is a silent error of twelve orders of magnitude.
Issuing a BNB address.
Create the customer
One POST with your own user id as the reference. This is the record everything else hangs off.
Ask for an address per chain
One per (customer, chain), and it does not change. The address is computed in advance from the customer's salt, so the same customer has the same address on every EVM chain — and you can show it again tomorrow without calling us.
Credit on deposit.confirmed
We watch every block, sweep what lands, and pay the network fee to do it. Sweeps are visible to you and read-only: they never change what you are owed.
curl https://api.molnpay.com/v1/customers \ -H "Authorization: Bearer $MOLNPAY_SECRET_KEY" \ -H "Idempotency-Key: user_4471" \ -d reference_id="user_4471"
What you do not have to do.
- Hold a BNB wallet, or guard a seed phrase for one. Every address is a contract with no key.
- Keep gas on hand. Our operator wallet funds the sweep on every chain BNB settles on.
- Re-issue an address. One per user, per chain, and it does not change.
- Run a watcher that must never miss a block, or reconcile a reorg by hand.
Taking BNB payments instead?
Same API, same keys, same balance — the difference is whether the address belongs to an invoice or to one of your users.
Accept BNB payments