Skip to main content
The HEVN API at /dapi/v1 lets your backend onboard customers, give them virtual accounts and move their money. Read For developers first, then pick one of the two integrations below. Both integrations use the same API, the same developer key and the same sandbox. They differ in who holds the customer’s wallet and how a payout is approved.

Integrations

The full comparison is in Integration kinds.

HEVN Connect

Your customer creates or links a HEVN account in a HEVN window that opens from your site. The account holds a non-custodial Base smart wallet, and the customer’s key signs each payout in that window. Choose it when you have no wallet infrastructure of your own. HEVN provides the wallet and the signing screen.

HEVN Connect

External wallets

Your backend creates each client through the API and registers a wallet address the customer holds as an external account. Virtual accounts requested on it deliver USDC to that address. A payout from it is funded by a transfer the customer’s wallet sends. Choose it when your product already gives each customer a wallet and you want no HEVN screen in the flow. Before HEVN enables it, you show that your customers hold the keys to those wallets.

External wallets

Sub accounts

A sub account is a further wallet of your own HEVN account on Base, with its own address, balance, ledger and virtual accounts. Your developer key signs for it, as it does for your main wallet. Use sub accounts to run many balances inside your own account, for example one per customer or per project. They are a feature of your integrator account and work with either integration. You cannot open or spend a sub account on an account you operate for a customer.

Sub accounts

Remote transfers

A remote transfer key sends USDC from your own HEVN account within an onchain allowance you grant. It is a separate credential on a separate API and needs no developer key. See Remote transfers.

Where to read