> ## Documentation Index
> Fetch the complete documentation index at: https://developer.uphold.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User onboarding overview — KYC, KYB, and capabilities

> Establish user eligibility and compliance readiness with Uphold's onboarding model. Compare KYC and KYB methods, verification responsibility, and capabilities.

Onboarding establishes users' **eligibility** and **compliance readiness** so they can access regulated financial actions on the Uphold Platform.

## Implementation decisions

Before you start building, you must make two key decisions that define your system architecture, compliance responsibilities, and operational complexity:

1. **Which onboarding method you'll use**
2. **Who is responsible for verifying user information**

## 1. Choose your implementation method

<CardGroup cols={3}>
  <Card title="API" icon="code">
    * You want to maintain control over the UI
    * You have specific branding requirements
    * You need a deep system integration
  </Card>

  <Card title="Connector" icon="plug">
    * You want to maintain control over the UI
    * You already use Sumsub or Veriff
    * You don't want to modify your existing onboarding flows
  </Card>

  <Card title="Widget" icon="puzzle-piece">
    * You're comfortable with a managed UI
    * You need the fastest time-to-market
    * You have limited development resources
  </Card>
</CardGroup>

### Compare implementation methods

| Characteristics | API | Connector | Widget |
| - | - | - | - |
| **What you build** | Complete UI + backend orchestration using Core APIs | UI + provider integration | Embed widget component |
| **Development time** | High (weeks-months) | Medium (1-2 weeks) | Low (days-weeks) |
| **UX control** | Full control | Full control | Limited (Uphold-managed UI) |
| **Maintenance** | You maintain all components | You maintain the UI, Uphold maintains the connector | Uphold maintains the widget |
| **Customization** | Full UI customization | Full UI customization | Widget configuration only |

## 2. Choose verification responsibility

When onboarding users, you must also decide who will be responsible for verifying the information collected.

### Verification models

| Comparison | **Uphold-verified** | **Partner-verified** |
| - | - | - |
| Description | You collect the user data and Uphold verifies it. | You collect and verify user data, then submit the results to Uphold. |
| Best if | You don't want to build or maintain verification systems. | You have existing onboarding infrastructure, or want full control over the user experience. |
| Compliance | Uphold is responsible for compliance as the verifier. | Your organization is responsible for compliance as the verifier. |
| Approvals | No approvals needed. | The Uphold compliance team must approve your verification processes. |

## Supported regions

The Enterprise API Suite currently supports users in the following regions:

* **United Kingdom**
* **United States of America**
* **European Union** <Badge color="green" size="xs">Coming soon</Badge>
* **Rest of the world** <Badge color="green" size="xs">Coming soon</Badge>

Contact your Account Manager to have more details about EU and rest of the world.

## Next Steps

<CardGroup cols={2}>
  <Card title="Individuals" icon="user" href="/developer-guides/user-onboarding/individual/overview">
    Complete step-by-step guide for Individual user verification.
  </Card>

  <Card title={ <>Businesses <Badge color="green" size="xs">Preview</Badge></> } icon="briefcase" href="/developer-guides/user-onboarding/business/overview">
    KYB API reference and preview availability for Business user verification.
  </Card>
</CardGroup>