KYC API
The KYC (Know Your Customer) API enables identity verification for user onboarding. This API supports a streamlined verification flow with optional prefill capabilities to reduce friction for users.Verification Workflow
The KYC process follows this general flow:Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /v1/kyc/prefill | Start KYC prefill process |
POST | /v1/kyc/prefill/otp | Submit OTP for prefill verification |
POST | /v1/kyc/start | Start KYC verification |
GET | /v1/kyc/status | Get current KYC status |
POST | /v1/kyc/webhook | Register webhook URL for status notifications |
POST | /v1/kyc/referral-codes | Create partner referral code |
GET | /v1/kyc/referral-codes | List referral codes |
GET | /v1/kyc/referral-codes/{code} | Validate a referral code |
Quick Start
Option 1: With Prefill (Recommended)
Prefill allows users to auto-populate their information using their phone number, reducing manual data entry.- Start Prefill
- Submit OTP (sent to user’s phone)
- Start Verification (with prefilled data)
Option 2: Direct Verification
Skip prefill and go directly to verification:Check Status
Use theuser_id you provided in the start request:
KYC Status
The status response contains:| Field | Description |
|---|---|
decision | Final decision: ACCEPT, REJECT, REVIEW, or empty (not started) |
status | Current status: NOT_STARTED, OPEN, ON_HOLD, CLOSED |
subStatus | Detailed sub-status (e.g., Document Request Initiated) |
externalId | The user_id you provided |
participantId | EP3 participant ID (populated after approval) |
account | EP3 account ID (populated after approval) |
Document Verification (DocV)
If additional document verification is required, theStartKYCVerification response will include DocV details:
| Field | Description |
|---|---|
docvTransactionToken | Token for document verification |
eventId | Event identifier |
qrCode | QR code for mobile document capture |
url | URL for web-based document capture |

