# No-code KYC

Hosted KYC lets you run uqudo’s onboarding flow without building your own onboarding user interface. You create and manage the setup in the **Customer Portal**, while uqudo hosts the onboarding journey for your end-users.

### How Hosted KYC works

1. Create a Hosted KYC configuration in the Customer Portal.
2. Choose how end-users will complete onboarding:
   * **Mobile Browser**
   * **Mobile App**
3. Configure the workflow, text, branding, onboarding settings, and delivery settings.
4. Share the generated onboarding link with your end-users.
5. The end-user completes the onboarding journey on a mobile phone.
6. uqudo sends the result to your configured webhook, makes the session available in the Customer Portal, and can also send a notification email.
7. If a return URL is configured, the end-user is redirected back to your website or application.

<figure><img src="https://1201843429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0JZZSvL3DmX19a9SgDAt%2Fuploads%2FP5Bf64yUSdjXeIkJV2RW%2FScreenshot%202026-04-01%20112257.png?alt=media&#x26;token=9b192670-5e32-490f-847a-88fe43bc639e" alt=""><figcaption></figcaption></figure>

### Before you start

Before creating your Hosted KYC configuration, decide:

* which documents you want to accept
* whether you need **Face Authentication**
* whether you need **Background Screening**
* whether you need **Lookup** or **NFC**
* whether you want to receive results automatically through a webhook
* whether you want a notification email for your operations team
* whether you want the end-user to return to a specific page after completion

If you are not sure whether a feature is enabled for your account, contact your uqudo representative.

### Create a configuration

1. Open the **Customer Portal**.
2. Go to [**No-Code KYC**](https://portal.uqudo.com/no-code-integration).
3. Click **Create Configuration**.
4. Choose one of the available onboarding channels:
   * **Mobile Browser**
   * **Mobile App**
5. Enter a clear configuration name.
6. Save the configuration.

After the configuration is created, continue with the setup pages inside that configuration.

<div align="left" data-full-width="false"><figure><img src="https://1201843429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0JZZSvL3DmX19a9SgDAt%2Fuploads%2FGza5hTEwEdEkeLi2Ntfp%2Fimage.png?alt=media&#x26;token=6a25f89d-76c0-4453-bc7f-12d30cd12401" alt="" width="292"><figcaption></figcaption></figure> <figure><img src="https://1201843429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0JZZSvL3DmX19a9SgDAt%2Fuploads%2FGPrKtqYaBcHqpWaotT2O%2FScreenshot%202026-04-01%20121053.png?alt=media&#x26;token=9edd48e8-2e2a-4ce7-bf83-d99482e7dfd5" alt="" width="563"><figcaption></figcaption></figure></div>

### Choose the onboarding channel

#### Mobile Browser

Choose **Mobile Browser** when you want the end-user to complete onboarding in the mobile browser using the phone camera and uqudo Web SDK.

This is usually the fastest option to launch because the user can stay in the browser throughout the journey.

#### Mobile App

Choose **Mobile App** when your onboarding requires the uqudo KYC app (Mobile SDK), such as journeys that require **NFC** on supported documents.

This option is commonly used when you need app-based capabilities as part of the onboarding.

### What you can configure

Each Hosted KYC configuration includes the following pages:

* **Workflow Settings:** Define the onboarding steps, accepted documents, and optional checks.
* **Text Settings:** Edit the instructions and messages shown to end-users.
* **Onboarding Settings:** Control onboarding link behaviour.
* **Other Settings:** Configure branding, webhook delivery, return URL, and notification email.
* **Onboard Users:** Copy and share the onboarding link and add a transaction nonce when needed.

### End-user journey at a glance

#### If the link is opened on mobile

The user starts the onboarding directly on the mobile phone.

* In a **Mobile Browser** flow, the user stays in the mobile browser.
* In a **Mobile App** flow, the user continues in the mobile app.

**Note:** If the end-user doesn't have the **uqudo KYC app** in a **Mobile App** flow, then they will be redirected to app store to download the app and then continue the onboarding seamlessly.

#### If the link is opened on desktop

The user sees a QR code and continues the onboarding on mobile after scanning it.

<figure><img src="https://1201843429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0JZZSvL3DmX19a9SgDAt%2Fuploads%2FJvos8U1uHgzGjdVdDQNu%2FScreenshot%202026-04-01%20144041.png?alt=media&#x26;token=c603ac9b-a3d2-4621-83c9-0aaa46586293" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1201843429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0JZZSvL3DmX19a9SgDAt%2Fuploads%2FnnH2acqxi9IN6RKFBfEm%2FScreenshot%202026-04-01%20121356.png?alt=media&#x26;token=7be2d120-5f62-4469-b29f-64cd219d7cf9" alt=""><figcaption></figcaption></figure>

#### After completion

Once the onboarding is completed:

* the result is sent to your webhook, if configured
* the session is visible in the Customer Portal
* the notification email is sent, if configured
* the user is redirected to your return URL, if configured