Tokenised KYC (TKYC) is a secure, consent-driven identity verification platform that allows regulated institutions to fetch verified KYC data directly from trusted sources—instantly, digitally, and compliantly. No paperwork. No duplication. No delays.
TKYC is built for any organisation in India that is required to verify customer identity under regulatory frameworks:
Banks & NBFCs – Accounts, loans, deposits
Payment Apps & Wallets – Digital payments
Fintech Platforms – Online onboarding, lending
Stock Brokers & Investment Firms – Demat, trading, mutual funds
Insurance Companies – Policy issuance & servicing
Pension Providers – Retirement accounts
Central KYC Registries – KYC reuse across services
Aadhaar e-KYC Providers – Instant identity verification
Banking Agents – Assisted or in-person onboarding
Educational Institutions – Admissions & student verification
Government Departments – Exams, scholarships, certificates & public services
All verifications operate under Indian regulations including RBI, SEBI, IRDAI, UIDAI, PMLA, and Government of India systems.
Fetch verified KYC directly from the source
Complete KYC instantly with user consent
Eliminate document collection and re-verification
Define granular access (mandatory, optional, or blocked fields)
Track KYC status in real time
Stay compliant by design
In short: faster onboarding, lower risk, and better user experience.
TKYC API Integration Overview
The TKYC API enables secure, cross-platform and inter-institutional interoperability using open standards, standardized APIs, and common data exchange protocols. This allows organizations to fetch KYC documents directly from trusted sources, with explicit user consent, and complete KYC instantly across participating institutions.
Below is a brief overview of the available APIs:
Request API
Initiates the user journey by creating a KYC request. This step captures user consent and triggers document retrieval from the user’s TKYC account across integrated platforms.
Returns a unique request ID used to track the request throughout the lifecycle.
Status API
Provides real-time visibility into the progress of a KYC request by querying the request ID. This API can be invoked at any stage of the journey.
Fetch API
Retrieves the KYC data and documents that the user has consented to share, exchanged through standardized formats to ensure interoperability.
Documents are made available as secure file URLs for download.
1. Request API
The TKYC Request API initiates a KYC request for a user. Each request is tied to a requester_id provided by TKYC after register. The API allows specifying the purpose, duration of access, and granular permissions for each KYC data item (mandatory, optional, or block).
Endpoint:
POST /request/{requester_id}
Path Parameter:
requester_id (string, required): Unique ID assigned to the requester by TKYC.
Authentication:
API Key / OAuth 2.0 Bearer Token
HTTPS is required
Request Headers:
Authorization (string, required): Bearer token
Content-Type (string, required): application/json
X-Request-ID (string, optional): Idempotency key
Request Body (JSON format):
{
"member_token": "rs123456789",
"purpose": "MFI Loan KYC verification",
"access_duration": "17532h",
"kyc_data": {
"aadhaar": {
"number": "mandatory",
"name": "mandatory",
"dob": "mandatory",
"address": "mandatory",
"gender": "mandatory",
"mobile_number": "optional",
"email_address": "optional",
"relationship_status": "optional",
"document": "block"
},
"pan": {
"number": "mandatory",
"full_name": "mandatory",
"father_name": "mandatory",
"dob_or_incorporation_date": "mandatory",
"photograph": "optional",
"signature": "optional",
"qr_code": "optional",
"document": "block"
},
{.........},
},
"callback_url": "https://example.com/tkyc/callback"
}
Request Body Fields:
member_token (string, required): Unique ID of the user in your system.
purpose (string, required): Reason for requesting KYC data.
access_duration (string, required): Duration until access expires (e.g., "24h", "48h").
kyc_data (object, required): Granular KYC permissions per document type.
Each field can be "mandatory" (must return if user consents), "optional" (return if user consents), or "block" (never return).
Example:
aadhaar.name - mandatory
aadhaar.photo - optional
aadhaar.document - block
callback_url (string, optional): URL to receive asynchronous status updates.
Success Response (HTTP 201 Created):
{
"member_token": "string",
"token_id": "123456789",
"status": "INITIATED",
"message": "The request has been created successfully and is awaiting user action or consent.",
"request_on": "2025-12-20T10:00:00Z"
"request_till": "2025-12-21T10:00:00Z"
}
Error Responses:
400 INVALID_REQUEST → Missing required fields or invalid permissions
401 UNAUTHORIZED → Invalid or missing authentication
403 FORBIDDEN → Requester not authorized
500 INTERNAL_ERROR → Server error
INITIATED – The request has been created successfully and is awaiting user action or consent.
FAILED – An error occurred during processing and the request could not be completed.
2. Status API
The TKYC Status API provides real-time visibility into the progress of a KYC request. By querying the token_id, the requester can check the current state of the KYC journey at any stage.
Endpoint
GET /status/{token_id}
Path Parameter:
token_id (string, required): Unique identifier returned when the TKYC request was created.
Authentication:
API Key / OAuth 2.0 Bearer Token
HTTPS is mandatory
Request Headers:
Authorization (string, required): Bearer token
Content-Type (string, required): application/json
Request Body (JSON format):
GET /status/123456789
Success Response (HTTP 201 Created):
{
"member_token": "rs123456789",
"token_id": "123456789",
"status": "APPROVED",
"message": "User consent received and request approved; data can be fetched.",
"request_on": "2025-12-20T10:00:00Z"
"request_till": "2025-12-20T10:00:00Z"
"approve_on": "2025-12-20T10:00:00Z"
"approve_till": "2027-12-20T10:00:00Z"
"kyc_data": {
"aadhaar": {
"number": "approved",
"name": "approved",
"dob": "approved",
"address": "approved",
"gender": "approved",
"mobile_number": "approved",
"email_address": "rejected",
"relationship_status": "rejected",
"document": "block"
},
"pan": {
"number": "approved",
"full_name": "approved",
"father_name": "approved",
"dob_or_incorporation_date": "approved",
"photograph": "rejected",
"signature": "optional",
"qr_code": "not_available",
"document": "block"
},
{.........},
}
}
Response Fields:
token_id: Unique identifier of the TKYC request.
status: Current status of the KYC request.
last_updated: Timestamp of the last status update.
Possible Status Values:
INITIATED – Request created successfully; user journey has started.
PENDING_APPROVAL – Awaiting user consent or system approval.
APPROVED – User consent received and request approved; data can be fetched.
REJECTED – Request denied by the user or TKYC system.
TIMEDOUT – Request expired due to no action within the allowed duration.
FAILED – Request failed due to a system or processing error.
Error Responses:
400 INVALID_REQUEST → Invalid or missing request ID
401 UNAUTHORIZED → Authentication failed
403 FORBIDDEN → Access to the request is not allowed
404 NOT_FOUND → Request ID does not exist
500 INTERNAL_ERROR → Internal server error
The TKYC Fetch API retrieves the KYC data and documents that a user has consented to share for an approved request. This API can only be invoked after the request reaches the APPROVED status. Data returned strictly follows the permissions defined during the request creation (mandatory, optional, block).
Endpoint:
GET /fetch/{request_id}
Path Parameter:
request_id (string, required): Unique identifier of the approved TKYC request.
Authentication:
API Key / OAuth 2.0 Bearer Token
HTTPS is mandatory
Request Headers:
Authorization (string, required): Bearer token
Content-Type (string, required): application/json
Sample Request:
GET /fetch/123456789
Success Response (HTTP 200 OK):
{
"token_id": "123456789",
"status": "APPROVED",
"message": "User consent received and request approved; data can be fetched.",
"request_on": "2025-12-20T10:00:00Z"
"request_till": "2025-12-20T10:00:00Z"
"approve_on": "2025-12-20T10:00:00Z"
"approve_till": "2027-12-20T10:00:00Z"
"kyc_data": {
"aadhaar": {
"number": "1234-5678-9012",
"name": "Rahul Sharma",
"dob": "1995-06-15",
"address": "Flat 12, MG Road, Bengaluru, Karnataka, 560001",
"gender": "Male",
"mobile_number": "+91XXXXXXXXXX",
"email_address": null,
"relationship_status": null,
"document": bull
},
"pan": {
"number": "ABCDE1234F",
"full_name": "Rahul Sharma",
"father_name": "Ramesh Sharma",
"dob_or_incorporation_date": "1995-06-15",
"photograph": null,
"signature": "https://tkyc.io/rs123456789/pan_signature.png",
"qr_code": null,
"document": null
},
{.........},
}
}
Response Fields:
token_id: Unique identifier of the TKYC request.
status: Current status of the request (always APPROVED for successful fetch).
kyc_data: Structured KYC data returned based on granted permissions.
documents: Secure, time-limited URL to download the document.
approve_till: Expiry time of the KYCs and document URL.
Permission Enforcement Rules:
Fields marked as mandatory are always returned after approval.
Fields marked as optional are returned only if the user consents.
Fields marked as block are never returned, even if user consents.
Error Responses:
400 INVALID_REQUEST → Invalid or missing request ID
401 UNAUTHORIZED → Authentication failed
403 FORBIDDEN → Request not approved or access expired
404 NOT_FOUND → Request ID does not exist
410 GONE → Access duration expired
500 INTERNAL_ERROR → Internal server error
