Accept payments · USDE

Accept Ethena USDe payments.

Invoice in the currency you sell in, and let your customer pay in Ethena USDe. We give the invoice a keyless address on the chain they choose, watch it, and send you a signed webhook when the payment is final. A synthetic dollar backed by hedged collateral rather than by cash — on more of our chains than any coin except USDT and USDC.

Start building How accept payments works

USDE on 7 chains.

Your customer picks one at checkout. You choose which of them you are willing to accept.

EthereumERC-20

BNB ChainBEP-20

ArbitrumERC-20

BaseERC-20

OptimismERC-20

LineaERC-20

ScrollERC-20

USDE on Ethereum: Gas here is the highest of any chain on this list, so a payment has to clear a minimum amount to be worth collecting. The checkout shows that minimum to your payer before they choose Ethereum, and every other chain here is cheaper.
USDE 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.
USDE on Scroll: The USDC on Scroll is the bridged token, because Circle does not issue natively here. It spends the same way; the contract address is just not Circle's own.

Taking a Ethena USDe payment.

Create the invoice

One POST with an amount, a pricing currency and your own reference. You get back a checkout URL, one payment address per chain, and a locked amount in every coin you accept.

They pay, at a rate that stays honest

Your customer is never asked to commit to a chain first — one address serves every EVM chain, so whatever arrives is attributable. Stablecoins are quoted once. A volatile coin is re-quoted every two minutes, and the figure it replaces is still honoured for five, so nobody who did as they were told is told they underpaid.

You get a signed webhook

HMAC-SHA256, retried for about 46 hours, replayable from the dashboard. The payment is credited to your balance per asset.

POST /v1/invoices

curl https://api.molnpay.com/v1/invoices \
  -H "Authorization: Bearer $MOLNPAY_SECRET_KEY" \
  -H "Idempotency-Key: order_8812" \
  -d amount="49.90" \
  -d currency="USD" \
  -d reference_id="order_8812"

What you do not have to do.

Hold a USDE 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 USDE settles on.
Ask your customer to make an account. The hosted checkout needs nothing from them but a payment.
Run a watcher that must never miss a block, or reconcile a reorg by hand.

Holding USDE for your users instead?

Same API, same keys, same balance — the difference is whether the address belongs to an invoice or to one of your users.

Ethena USDe deposit addresses

Accept another asset

All chains and assets Pricing