This module covers the end-to-end process of registering new users and verifying identity. It guides account creation, document submission (via API or hosted page), and final account activation.Key Stages#
1.
User Registration: Create the base account.
2.
Identity Verification (KYC): Submit identity documents using one of two methods.
3.
Proof of Address (POA): Conditional step required only for specific jurisdictions.
4.
Finalization: Trigger verification review once all required documents are ready.
Core Endpoints#
Create User Account
Initiates the process by creating a new user account. Returns poaRequiredForExtended when the extended POA path is required.Add User Verification
Submits all data for review. Required to finalize both hosted and API flows.Add POA File
Upload proof of address only if required by user country response.Method A: API File Upload#
Choose this method if you collect documents in your own UI (white-label solution).Add KYC File
Upload user identity document directly via API.Method B: Hosted Verification#
Choose this method if you want Fintegence to handle document collection via a secure hosted page.Create KYC Verification
Initialize a hosted verification session.Redirect to Verification
Generate redirect URL for the user.Get KYC Status
Check status of hosted verification session.
Typical Workflows#
Select the verification method that best fits your integration model.1. Registration (Common Start)#
Pay attention to poaRequiredForExtended in response. It determines whether you must complete the POA branch before final verification.
2. Identity Verification (Choose Method)#
Method A: API File Upload (White Label)#
Use this flow if you have your own mobile/web UI for collecting documents.1.
Collect document (ID card/passport) in your app.
3.
If poaRequiredForExtended is not set to true, finalize by calling Add User Verification to submit files for review. Method B: Hosted Verification#
Use this flow to offload verification UI to hosted flow.4.
If poaRequiredForExtended is not set to true, finalize by calling Add User Verification to lock data and start review. 3. Proof of Address (Conditional)#
If Create User Account returns poaRequiredForExtended: true:1.
Complete identity document collection using Method A or Method B.
Proof of Address (POA) Details#
Proof of address confirms user residential address and is a regulatory requirement for specific countries.When Is POA Required?#
API indicates requirement during account creation with "poaRequiredForExtended": true.
Document Requirements#
Must include user full name and current address.
Must be recently issued (typically within last 3 months).
Must be legible and valid.
Commonly Accepted Documents#
Utility bill (electricity, water, gas, internet).
Government-issued official letter.