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

# Individual onboarding overview

> Understand the KYC policy scope, verification levels, information reviewed, and current implementation path.

## Individual onboarding (KYC)

Individual customers complete KYC before they can transact. The verification level depends on jurisdiction, transaction volume, risk assessment, and regulatory requirements.

<Warning>
  Requirements vary by customer, jurisdiction, capability, and review. Current
  tasks and generated schemas control what you must submit.
</Warning>

## What KYC covers

KYC confirms a customer's identity and can add address, liveness, financial-profile, or source-of-funds review as risk and regulatory requirements increase. Requirements can vary by jurisdiction, transaction volume, and use case.

## KYC verification levels

| Level      | Requirements                                              | Typical use case                                  |
| ---------- | --------------------------------------------------------- | ------------------------------------------------- |
| Simplified | Name, surname, and date of birth                          | Approved low-value flows                          |
| Standard   | Government-issued ID and selfie/liveness check            | Regular transactions within standard limits       |
| Enhanced   | ID, selfie/liveness, proof of address, and proof of funds | High-value transactions or elevated-risk profiles |

Simplified, Standard, and Enhanced are policy tiers, not current API status values.

## Information collected

Depending on the current review, Swipelux can request:

* Legal name and date of birth
* Contact details
* Residential address when required
* Government-issued identity evidence and liveness evidence
* Financial-profile information, including expected activity and source of funds, when required

Do not treat this list as a universal request body. The current customer schema and task detail determine the information required for a particular capability.

## Current implementation

Create the individual customer, discover and request an eligible capability, then follow current tasks. A task can provide first-party hosted verification sessions or require a task submission. Upload documents only when that task asks for them.

Follow the [individual onboarding guide](/integration/onboarding/customers#individual-customers), [Capabilities and tasks](/integration/onboarding/capabilities-and-requirements#complete-current-tasks), and the [individual API workflow map](/knowledge-base/individual-onboarding/api-workflow).

## Support

For KYC policy questions, contact [compliance@swipelux.com](mailto:compliance@swipelux.com). For API implementation issues, contact [support@swipelux.com](mailto:support@swipelux.com).


## Related topics

- [Business onboarding overview](/knowledge-base/business-onboarding/overview.md)
- [Individual onboarding API workflow](/knowledge-base/individual-onboarding/api-workflow.md)
- [Overview](/knowledge-base/compliance/overview.md)
- [Integration overview](/integration/overview.md)
- [Business onboarding FAQ](/knowledge-base/business-onboarding/faq.md)