Menu

Customer accounts and subaccounts

Connect customer structure to operations

Institutions work with different customers and different structures. HOLD OS keeps that structure inside the system, so every wallet, trade and contract is connected to the right account.

Request a product walkthrough All capabilities
  1. Institution Frame, rules and authority
    1. Customer Private account created by the institution
      1. Subaccount Controlled account within the customer
Explanatory diagram

Institution and customer

HOLD OS is institution-first: the institution sets the frame of work, and customers hold accounts inside it. Each account has its own wallets, trades and contracts.

This structure helps your team know at every moment which customer and which account they are working with, and keeps each customer’s records apart from every other customer’s.

Private, institution-managed onboarding

HOLD OS has no public signup. Accounts are created by the institution’s own decision and process.

  1. Institution decides

    The institution decides who should have an account.

  2. Create the account

    The account is created through a private, managed process.

  3. Sign in

    The account holder signs in with a username and password and can enable a personal Authenticator.

  4. Authority is separate

    Creating an account moves no money and grants no financial authority; operational authority is set separately.

Controlled subaccounts

Subaccounts let an institution keep a customer’s related activities in separate, controlled parts. A subaccount sits within the same authority frame as the institution and the customer.

Who can perform operations in a subaccount depends, as with any account, on the role, the current account and the asset concerned.

Customer bank destination enrollment and review

A customer can enroll a bank destination they own, and the institution reviews it. This is a manual review workflow: HOLD OS does not connect to banks and does not verify bank accounts automatically.

The review helps the institution confirm, using its own procedure, that a bank destination belongs to that customer before it is used.

  1. Enroll The customer enters their own bank destination
  2. Manual review The institution reviews it with its own procedure
  3. Review outcome Recorded for that same customer
Explanatory diagram

Access without automatic financial authority

Having an account and having authority are two different things. HOLD OS keeps them apart.

What to evaluateHow HOLD OS approaches it
Account createdAccess to the system; no money moved and no financial authority.
Signed inSees what the user’s role allows.
Performing an operationOnly when role, account and asset all permit it.
Access control

Review your institution’s customer structure

In a walkthrough we look at how your customers and subaccounts would take shape in HOLD OS.

Request a product walkthrough View pricing