Compliance
End-User Identity Verification (KYC)
Identity verification paths and data protection for Swipelux users
End-User Identity Verification (KYC)
Swipelux mandates identity verification for all users interacting with the Orchestration flow. We offer two integration paths.
Path A: Standard KYC (Swipelux Hosted)
- Workflow: User is redirected (or sees an iframe) where Swipelux collects ID, Selfie, and Liveness data directly
- Best Value For: Sub-merchants who do not want to handle PII or do not have their own KYC solution
- Liability: Swipelux assumes full liability for verification
Path B: Sub-Merchant Reliance (Import KYC)
- Available only to regulated partners (Banks, Fintechs, etc)
- Workflow: Sub-merchant verifies the user in their own UX/UI. Merchant transmits verified PII (Name, DOB, Address, Doc ID) via secure API to Swipelux
- Requirement: Sub-merchant must hold a license in an equivalent jurisdiction (EU, UK, etc.) and pass a compliance audit
- Screening: Swipelux performs independent Sanctions/PEP screening on the data but does not re-collect documents from the user
Data Protection
Sub-merchants do not access user compliance data; all PII and documents remain in Swipelux's secure environment.