Skip to main content

Individual onboarding (KYC)

Individual customers complete KYC before they can transact. The verification level depends on jurisdiction, transaction volume, risk assessment, and regulatory requirements.
Requirements vary by customer, jurisdiction, capability, and review. Current tasks and generated schemas control what you must submit.

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

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, Capabilities and tasks, and the individual API workflow map.

Support

For KYC policy questions, contact compliance@swipelux.com. For API implementation issues, contact support@swipelux.com.