Skip to main content
Every Finance API resource hangs off a party. Once the hierarchy clicks, the rest of the API is predictable: you create entities top-down, and most operations are scoped to an account.

The entities

EntityWhat it isKey relationships
PartyThe legal identity — an INDIVIDUAL or ORGANISATION. Carries KYC/KYB status.Linked to one or more accounts via party roles.
AccountThe container for money movement, pinned to one chain (BASE/AVALANCHE) at creation.Belongs to a party (or parties); holds wallets, VBAs, transfers, and payment requests.
Party roleThe link between a party and an account (ACCOUNT_HOLDER).Many parties can share one account (joint accounts).
WalletCustodial crypto wallet (VENLY_MANAGED or SELF_CUSTODY). Each account has an account wallet plus an escrow wallet.Belongs to an account; holds per-asset balances.
Virtual bank accountAn IBAN for receiving fiat (EUR SEPA), auto-converted to crypto.Belongs to an account.

How they’re created

You build top-down, and verification gates the money-movement steps:
1

Create a party

The root identity. KYC/KYB starts after creation — see Account verification.
2

Open an account

Link the party (partyId, or an inline party) and choose the chain. Venly provisions the wallets.
3

Get verified

A Venly admin moves the account to VERIFIED. Until then, money movement is blocked.
4

Add IBANs and move money

IDs and external IDs

Every entity has a Venly UUID id. You can also set your own externalId on parties and accounts and use it as a shortcut — for example receiverExternalId on a transfer, instead of looking up the Venly UUID.

Next steps

Getting started

Build the hierarchy end to end.

Glossary

Definitions for every entity and status.