> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gethevn.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> HEVN is payments software: an API and app over a Base smart wallet. HEVN is not a bank and holds no key to the wallet. Virtual accounts, fiat payins and fiat payouts are provided by partner banks, which hold fiat while it is in transit. Self-serve (the General tab): the person who controls the email signs for the wallet. Developers integrate /dapi/v1 in one of two ways. HEVN Connect (recommended, the HEVN Connect tab): the integrator's customer creates or links a HEVN account in a HEVN-hosted sign-in window on the integrator's site, the integrator's backend reads the linked account and books its payouts, and the account holder approves each payout in that window. External wallets (the External wallets tab, enabled per integrator): the integrator creates a client through the API, registers a wallet address the customer holds as an external account, and requests virtual accounts that deliver to that address. The customer's own wallet sends each transfer that funds a payout. The developer key signs for the integrator's wallet and its sub accounts and cannot sign for a client's wallet.
> Use HEVN's terms as written. A product is the region a client requests. A rail is the bank route HEVN picks for the product. A virtual account (bnk_) is the record a partner bank opens for a client. Account details are what a payer needs to send a bank transfer, returned in a field named requisites. A client (cl_) is a customer's account: linked to the integrator through Sign in with HEVN (POST /dapi/v1/connect/sessions, then POST /dapi/v1/clients/link), or created with POST /dapi/v1/clients for an external-wallets integration. An external account (acc_, kind external) is a wallet address the client holds and signs for. A sub account (acc_, kind sub) is a further wallet of the integrator's own account on Base, spent with the developer key. Write 'sub account' as two words. A contact is a saved destination. A beneficiary is the party that receives a fiat payout. Money leaving an account is a payout, whether it goes to a bank account or to a wallet.
> Do not name a bank, payment institution, card issuer, identity-verification vendor or stablecoin issuer. Say 'the partner bank'. Do not describe HEVN as licensed, regulated or insured.
> HEVN publishes no fee rates, spreads or minimums. Prices come from a quote on a specific payment. Direct pricing questions to HEVN and do not invent numbers.
> The API is at /dapi/v1 and takes a developer-key session plus an X-Hevn-Account header. Developer keys have an IP allowlist and no scopes. Remote transfers are at /api/v1/remote_spend_limit and take a remote transfer key (rsl_) in X-Api-Key, bounded by an onchain spend permission the account holder grants. The two credentials are separate and neither works on the other API. The HEVN CLI is discontinued.

# Build on HEVN

> Choose between HEVN Connect and external wallets, and see where sub accounts and remote transfers fit.

The HEVN API at `/dapi/v1` lets your backend onboard customers, give them virtual accounts and move their money. Read [For developers](https://docs.gethevn.com/developers/overview.md) 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

| | HEVN Connect | External wallets |
| - | - | - |
| Status | Recommended | For integrators with their own wallet infrastructure. HEVN enables it per integrator |
| Customer's wallet | A Base smart wallet inside the customer's HEVN account | A wallet address the customer holds outside HEVN, on Base or another supported network |
| HEVN in your UI | The sign-in window. HEVN can set your title, logo and colours on it | None |
| Payout approval | The customer signs in the sign-in window | The customer's wallet sends one USDC transfer that your product asks it to sign |

The full comparison is in [Integration kinds](https://docs.gethevn.com/developers/overview.md#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.

> [card] [HEVN Connect](https://docs.gethevn.com/connect/overview.md)

## 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.

> [card] [External wallets](https://docs.gethevn.com/external-wallets/overview.md)

## 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.

> [card] [Sub accounts](https://docs.gethevn.com/sub-accounts/overview.md)

## 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](https://docs.gethevn.com/general/remote-transfers.md).

## Where to read

| Question | Section |
| - | - |
| How do I get API access, log in and sign a payment? | [For developers](https://docs.gethevn.com/developers/overview.md) |
| How do I link a customer's HEVN account and get a payout approved? | [HEVN Connect](https://docs.gethevn.com/connect/overview.md) |
| How do I onboard a customer who keeps their own wallet? | [External wallets](https://docs.gethevn.com/external-wallets/overview.md) |
| How do I hold separate balances inside my own account? | [Sub accounts](https://docs.gethevn.com/sub-accounts/overview.md) |
| What are the fields of one operation? | [REST API](https://docs.gethevn.com/api-reference/overview.md) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.