Individual Onboarding (KYC)

API Reference

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

KYC requirements can vary by jurisdiction, transaction volume, and use case. Contact support for jurisdiction-specific guidance.

KYC Verification Levels

Swipelux supports three KYC levels. Higher-risk or higher-volume flows require more information before money movement is enabled.

Level	Requirements	Typical Use Case
Simplified	Name, surname, date of birth	Approved low-value flows
Standard	ID document + selfie	Regular transactions within standard limits
Enhanced	ID + selfie + proof of address + proof of funds	High-value transactions, elevated risk profiles

Common Fields

You can create a customer with minimal information, then add more fields as the verification flow requires them:

Field	Type	Description
`firstName`	string	Customer's first name
`lastName`	string	Customer's last name
`middleName`	string	Customer's middle name
`email`	string	Customer's email address
`birthDate`	date	Date of birth (YYYY-MM-DD)
`phone`	string	Phone number in E.164 format (e.g., +12025551234)
`metadata`	object	Custom key-value pairs for your reference
`residentialAddress`	object	Customer's address (streetLine1, city, state, country required)
`identifyingInformation`	array	ID documents (type, issuingCountry, frontSideImage)

Quick Start

# 1. Create customer
POST /v1/customers
 
# 2. Initiate KYC verification
POST /v1/customers/{id}/kyc
 
# 3. Redirect customer to verification URL
 
# 4. Check status
GET /v1/customers/{id}

Overview

Individual Onboarding (KYC)

API Reference

KYC Verification Levels

Common Fields

Quick Start

On this page