---
title: "Onboarding models"
description: "Compare the ways in which Nodu receives a customer's information: from the customer on Nodu's pages, from you through the API, or copied from your Sumsub account."
url: "/guides/customers/onboarding-models/"
index: "/llms.txt"
---

# Onboarding models

An onboarding model is the way in which Nodu receives the information about a customer. The customer enters it on Nodu's pages, you send it through the API, or Nodu copies it from your own Sumsub account. The models also differ in what the customer sees and in what you build. [How onboarding works, and customer statuses](/guides/customers/how-onboarding-works/index.md) explains the terms acceptance and verification steps that all models share.

## The models

In the table, an application is the set of information and documents that Nodu reviews for one customer.

| Model | How Nodu receives the information | What the customer sees | What you build | When it applies |
|---|---|---|---|---|
| [Hosted onboarding](/guides/customers/hosted-onboarding/index.md) | The customer enters their information and documents on Nodu's verification page. | Nodu's terms page and verification page. | Two redirects to Nodu's pages, and screens for progress and the outcome. | You do not want to collect verification data yourself. Whether you can use hosted onboarding depends on your integration agreement with Nodu. |
| [API onboarding](/guides/customers/api-onboarding/create-a-customer-with-a-full-application/index.md) | You collect the information and documents in your own interface. You send them to Nodu through the API, as an application. | Your interface only. | Forms for the data and the documents, the calls that create, submit and correct an application, and screens for errors, progress and the outcome. | You already collect this data, or you want to control the whole interface. Whether you can use API onboarding depends on your integration agreement with Nodu. |
| [API onboarding with Sumsub sharing](/guides/customers/api-onboarding/sumsub-sharing/index.md) | Nodu copies the information and documents from your own Sumsub account, with a share token. You send what Nodu still needs through the API. | Your interface only. The customer does not verify their identity a second time. | A call that generates a share token, then the same calls as API onboarding. | You have already verified the customer in your own Sumsub account. Whether you can use Sumsub sharing and API onboarding depends on your integration agreement with Nodu. You need both. |

Sumsub sharing is not a separate model. It lets you start API onboarding with the information that you already hold for the customer in your Sumsub account. You do not collect it again.

## What is the same in every model

- **One customer object.** You create the customer with [Create a customer](/api/tag/customers/post-v1-customers.md) in every model. The statuses and the webhook events are the same.
- **One result.** The customer can transact when the customer has `status=active`.
- **Corrections.** Nodu can ask for more information or reject a customer. [Resubmission and rejection](/guides/customers/resubmission-and-rejection/index.md) describes what you do in each model.

## Acceptance of the terms

With hosted onboarding, the customer accepts the terms on a Nodu page. With API onboarding, you choose one of two ways:

- Present the terms in your own interface, through the process agreed with Nodu. Record when the customer accepts the terms. Send that time with the application.
- Redirect the customer to Nodu's terms page, as in hosted onboarding.

The first way depends on your integration agreement with Nodu.

## What your integration agreement decides

- **Which models you can use.** When a model is not included, Nodu refuses the request with a business rule violation. For application data, `rule=reliance_application_not_permitted`. For a share token, `rule=applicant_import_not_permitted`.
- **Which customers you can onboard.** Agree with Nodu whether you onboard individuals, businesses or both.
- **What an application needs.** The information and documents you need depend on the Nodu entity you integrate with and on your integration agreement with Nodu. Nodu supplies these requirements to you as a separate document.

## Next steps

- [Hosted onboarding](/guides/customers/hosted-onboarding/index.md): the steps when the customer uses Nodu's pages.
- [Create a customer with a full application](/guides/customers/api-onboarding/create-a-customer-with-a-full-application/index.md): the steps of API onboarding.
- [Onboarding with Sumsub sharing](/guides/customers/api-onboarding/sumsub-sharing/index.md): start API onboarding with verification data you already hold for the customer.
- [Test onboarding in the sandbox](/guides/sandbox/test-onboarding/index.md): try each model in the test environment.
