Onboarding on io.network

How a principal member onboards a client, from published identity to an allowlisted address

Clients join io.network through a principal member. There is no self-service sign-up. Onboarding takes a client from invitation to an io.chain address that can hold and transfer the principal member's tokens.

Onboarding flow

%%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E8EEFB", "primaryTextColor": "#07112B", "primaryBorderColor": "#003EB7", "lineColor": "#8A96B4", "actorBkg": "#07112B", "actorTextColor": "#FFFFFF", "actorBorder": "#07112B", "actorLineColor": "#8A96B4", "signalColor": "#003EB7", "signalTextColor": "#07112B", "noteBkgColor": "#E3F4EF", "noteBorderColor": "#0E7C66", "noteTextColor": "#07112B", "activationBkgColor": "#E8EEFB", "sequenceNumberColor": "#FFFFFF", "fontSize": "14px"}}}%%
sequenceDiagram
    autonumber
    participant PM as Principal member
    participant V as io.vault
    participant C as Client

    PM->>V: Publish identity
    PM->>V: Invite client by email
    opt Validation check
        V->>PM: Check client against core banking or KYC
        PM-->>V: Approve
    end
    V->>C: Send invitation
    C->>V: Accept and sign in
    Note over V: Client organisation created
    C->>V: Create and activate vault
    Note over V: io.chain address provisioned and monitored
    V->>PM: Add address to network directory (hidden)
    V-->>PM: Notify that the client's first vault is ready
    PM->>V: Allowlist address on currency token
    Note over PM,C: Client can hold and transfer tokens

1. Publish an identity

The principal member publishes the identity its clients see when they're invited, and that other members see in the network directory. io.finnet sets up each principal member's network configuration before this step.

2. Send the invitation

The principal member invites the client by email. The invitation creates a new organisation for the client, on the principal member's plan.

If the principal member has set up a validation check, io.vault first asks the principal member's core banking or Know Your Customer (KYC) system to approve the client. If the check rejects the client, or can't be reached, the invitation isn't sent. KYC and client eligibility stay with the principal member: io.vault doesn't perform them.

Invitation statusMeaning
provisioningThe client's organisation is being created.
pendingSent, and waiting for the client to accept.
acceptedThe client has joined.
revokedThe principal member withdrew the invitation.
failedThe invitation couldn't be set up.

An invitation that isn't accepted expires after 30 days by default.

3. Accept and create a vault

The client accepts the invitation, signs in to its new organisation, and creates a vault with its own signers and threshold. See Vaults, signers, and thresholds.

When the vault is activated, Treasury provisions its io.chain address and monitors it. The client doesn't need to register the network or start monitoring.

4. Directory entry

io.vault adds the new address to the principal member's network directory, hidden by default, and notifies the principal member that the client's first vault is ready. The principal member decides whether to make the address visible to other members.

5. Allowlist the address

Before the client can hold the principal member's currency tokens, the principal member adds the client's address to the token's allowlist. Like any token control, this is a transaction from the principal member's vault, approved by its signers. See Tokens on io.network.

The client can then receive, hold, and transfer the tokens. See Send and receive.

What clients can't change

On io.chain, Treasury manages addresses for you:

  • You can't start or stop monitoring io.chain addresses, or create hierarchical deterministic (HD) addresses on io.chain.
  • You can't remove io.chain from a vault while its primary address is monitored.

Did this page help you?