Client Accounts

Client Accounts are the main account structure in Rialto's API. They are the accounts that request trades on the platform. Below are a few points to note about Client Accounts.

Individual vs. Entity Accounts

Client accounts can be owned by either an individual person, or a legal entity. Processes differ a bit between the two accounts. In particular:

• Onboarding is different, individuals will have to undergo Know Your Customer checks (KYC), while entities will have to go through Know Your Business (KYB) checks. The documents to provide and the analysis depth vary from case to case, but the onboarding process is overall expected to be longer for entities.

• Entity accounts can be managed by multiple persons from the entity organization. Entity Team Members can have two roles: Operators and Authorized Signatories. Operators are allowed to fill the onboarding and request trades, but not sign anything. Authorized Signatoriess can do the same as Operators, but can also sign Rialto's Terms and Conditions and confirm trade requests.

Owned Account vs. Managed Account

Client accounts can be created 2 ways, either by Rialto's admin team themselves, or by an Accounts Manager account. The difference are the following:

• Managed Client Accounts will never have access to API settings.

• Managed Client Accounts might not have access to Rialto's UI, depending on the desired settings of their Accounts Manager. Accounts that can't access Rialto's application are often meant to be used via API only, to be integrated directly into the Accounts Manager's own product.

API Access

Client Accounts have access to a dedicated Rialto's API in order to manage their transactions, bank accounts and blockchain wallets. The Client API does not include the onboarding process.

Clients Accounts will always have to complete their KYC/KYB checks on Rialto's application directly. When their account is verified, Client Accounts may request API access to automate their transaction request process.

Onboarding will typically have to be completed once for Client Accounts, hence the choice to not expose this part of the API.

Typical use cases for the Rialto's API for Client Accounts include Virtual Assets Service Providers (VASP) using Rialto's products for the benefit of their own clients. When dealing with regulated entities, Rialto can rely on their own Anti Money Laundering policies to facilitate the end client onboarding and transaction flow.