Deposit addresses · BTC
Bitcoin deposit addresses for your users.
Give every one of your users a permanent Bitcoin 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. The asset customers ask for by name. Its own chain, its own address formats, no tokens.
BTC 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.
- BTC on Bitcoin
- Bitcoin has no token layer, so BTC is the only thing that can arrive. We offer four address formats so a sender whose wallet cannot pay a bech32 address is not stuck.
Issuing a Bitcoin 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 BTC 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 BTC 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 BTC 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 Bitcoin payments