Skip to main content

​
KYC verification levels

Swipelux uses three policy tiers of identity verification. The applicable tier depends on customer risk, jurisdiction, expected transaction volume, and regulatory requirements.
These tiers describe policy classifications rather than current API enums. Current tasks determine the requirements for a specific customer.

​
Simplified KYC

Simplified KYC is used for approved low-risk, low-value flows.

​
Required information

  • First name
  • Last name
  • Date of birth

​
When it is used

  • Transaction amounts are below applicable simplified thresholds
  • The customer is in a low-risk jurisdiction

​
Standard KYC

Standard KYC verifies identity with a government-issued document and a selfie or liveness check.

​
Required documents

  • Government-issued ID
  • Selfie or liveness check

​
Accepted ID documents

  • Passport
  • Driver’s license
  • National ID card

​
Enhanced KYC (enhanced due diligence)

Enhanced KYC adds address and funds evidence for higher-risk scenarios.

​
Required documents

  • Everything required for Standard KYC
  • Proof of address
  • Proof of funds

​
Triggers for enhanced KYC

  • Transaction volume exceeds standard thresholds
  • High-risk jurisdiction
  • Compliance-team flag based on risk assessment
  • Regulatory requirements

​
Proof of address requirements

​
Proof of funds requirements

​
Policy tiers and current tasks

The current task detail remains the source of truth for the next API action. It can provide a first-party hosted session, request answers through a submission, or request document evidence. For new individual intake tasks, the hosted identity session covers the requirements listed in coveredRequirementIds: the ID document, selfie, and, where the task requires it, proof of address. Proof of funds is not collected in the hosted session for new individual intake tasks. The task requests it as a document requirement. Upload the document, submit it with the task, and wait for Swipelux to review it. The task stays open until Swipelux accepts the proof of funds. If you already verified the customer in your own account with Swipelux’s identity verification provider, you can import that verification with a share token instead of sending the customer through the hosted session. The import covers the requirements listed in coveredRequirementIds: the ID document, selfie, and, where the task requires it, proof of address. Swipelux reruns the checks against its own requirements. See Import an existing identity verification. For some enhanced reviews, the compliance team may also contact the customer’s registered email address. Treat that contact as policy review coordination, not a substitute for reading current API resources. See individual onboarding, Capabilities and tasks, and the Integration Documents guide.