# Sub-Accounts Onboarding

## Overview

This section provides a comprehensive guide for Main Account holders to onboard Sub-Accounts onto the Ryft platform. It covers the necessary steps and considerations for successfully integrating vendors into the Ryft payment processing system.

Onboarding Sub-Accounts is an integral part of the online marketplace model. Therefore, it is essential to be aware of the following key points:

- The Main Account holder is always responsible for onboarding each Sub-Account.
- This process differs based on the specific onboarding flow chosen by the Main Account holder.


At Ryft, we offer two distinct onboarding flows for Sub-Accounts: **Hosted onboarding** and **Non-Hosted (or API) onboarding**. Each flow has its own set of requirements and processes, which are detailed below.

## Hosted Onboarding

The **Hosted onboarding** flow allows Ryft to handle the collection of Sub-Account details on behalf of the Main Account Holder. In this process, Sub-Accounts are directed to the Ryft portal where they can create their own login. Once registered, using the Ryft portal Sub-Accounts will be able to:

- Enter their business and personal information.
- Upload their Bank Account details for payouts.
- Select a payout schedule.
- Visualise all their customers and transactions.


The main benefit of this approach is a reduced integration effort for the Main Account holder.

## Non-Hosted (API) Onboarding

The **Non-Hosted** onboarding flow gives the Main Account holder full control over the onboarding process of Sub-Accounts. In this flow, the Main Account holder is responsible for collecting all necessary information from Sub-Accounts and submitting it to Ryft via API calls.

This approach requires more technical resources and integration effort from the Main Account holder, but allows for greater customization and flexibility in the onboarding process.

Benefits of this approach include:

- **Less friction**: Sub-Accounts won't be required to create a Ryft account.
- **White-labeling**: The Main Account holder can fully customise the onboarding experience to match their brand.
- **Full access to Sub-Account information**: The Main Account holder can decide when and how to collect information such as Business and Personal details, Bank Account information and KYC/KYB documents for verification.
- **Sub-Accounts Payout Management**: The Main Account holder can manage the payout settings and schedules for each Sub-Account.


## Should You Choose Hosted or Non-Hosted Onboarding ?

The choice between Hosted and Non-Hosted onboarding depends on the specific needs and resources of the Main Account holder. Here are some considerations to help you decide:

- **Hosted Onboarding** is ideal for Main Account holders who prefer a simpler integration process and are comfortable with Ryft managing the onboarding experience for Sub-Accounts. It is particularly suitable for those who want to minimize development effort and leverage Ryft's existing infrastructure.
- **Non-Hosted Onboarding** is best for Main Account holders who require greater control over the onboarding process and are willing to invest in the necessary technical resources. This option is suitable for those who want to fully customise the onboarding experience and manage Sub-Account information directly. It is also a good choice for Main Account holders who want to manage the payout settings and schedules for their Sub-Accounts.


## Further Reading

Hosted Onboarding
Learn more about the Hosted onboarding flow, including the steps involved and how to guide Sub-Accounts through the process.

Non-Hosted (API) Onboarding
Discover the Non-Hosted onboarding flow, including API endpoints, required information, and best practices for integrating Sub-Accounts.

Verification of Sub-Accounts
Understand the KYC/KYB verification process for Sub-Accounts, including required documents and compliance requirements.

Payouts
Explore how payouts are managed for Sub-Accounts.

Terms And Conditions
Review the terms and conditions that apply to Sub-Accounts on the Ryft platform.