---
title: "Send OTP (eKYC) API Reference"
description: "Initiate AePS Fingpay eKYC by sending an OTP to the agent's registered Aadhaar-linked mobile number."
canonical: "https://eps.eko.in/docs/aeps-fingpay-send-otp-kyc"
---


> **Canonical URL:** https://eps.eko.in/docs/aeps-fingpay-send-otp-kyc
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Send OTP (eKYC) API Reference

`POST https://staging.eko.in/ekoapi/v3/user/collection/aeps-fingpay/kyc/otp`

Initiate AePS Fingpay eKYC by sending an OTP to the agent's registered Aadhaar-linked mobile number.

First-time KYC follows three steps in order: `Send OTP` → `Verify OTP` → `Biometric`. On subsequent days, use the Daily KYC (biometric-only) endpoint.

This is the first step in the one-time AePS Fingpay eKYC flow. The OTP is delivered to the number passed in `customer_id`. The eKYC flow — Send OTP → Verify OTP → Biometric — must be completed once per agent before they can perform any AePS transactions. This step is a prerequisite; do not confuse it with the Daily KYC which is required on each calendar day.

> View product & pricing details: [AePS Cashout](https://eps.eko.in/products/aeps-api.md)

## Body parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| client_ref_id | string | no | Unique reference ID per API call, generated by your system (max 20 characters). e.g. 2026010100123456789 |
| user_code | string | yes | Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your users e.g. 20810200 |
| aadhar | string | yes | RSA-encrypted, Base64-encoded Aadhaar number of the agent undergoing eKYC. e.g. BASE64_ENCRYPTED_AADHAAR |
| customer_id | string | yes | Registered mobile number of the agent/merchant undergoing eKYC. The OTP is delivered to this number. e.g. 9123456789 |
| latlong | string | yes | Agent's GPS coordinates as `latitude,longitude`. Required for security and fraud prevention. e.g. 28.6139,77.2090 |

## Headers

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| developer_key | string | yes | Static API key issued to your account after KYC. |
| secret-key | string | yes | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
| secret-key-timestamp | string | yes | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
| content-type | string | yes | application/json e.g. application/json |

## Response

⭐ marks fields highlighted as verifiable.

| Field | Type | Description |
| --- | --- | --- |
| status | number | Primary success indicator (0 = success). |
| message | string | Human-readable response / error message. |
| response_status_id | number | Granular status id; see the shared error-codes table. |
| response_type_id | number | A unique id for every possible response shape (success or error) — useful for client logic branching and analytics. |
| data | object | API-specific response payload. |
| data.reference_tid ⭐ | string | Transaction reference ID for this eKYC session. Must be passed to the Verify OTP API. |
| data.otp_ref_id ⭐ | string | Reference ID for the OTP session. Must be passed to the Verify OTP API. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 1600 | OTP request has been sent | [aeps-fingpay-verify-otp-kyc](https://eps.eko.in/docs/aeps-fingpay-verify-otp-kyc.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "user_code": "20810200",
  "aadhar": "BASE64_ENCRYPTED_AADHAAR",
  "customer_id": "9123456789",
  "latlong": "28.6139,77.2090"
}
```

## Example response

`response_type_id` `1600` — OTP request has been sent. Next step: [aeps-fingpay-verify-otp-kyc](https://eps.eko.in/docs/aeps-fingpay-verify-otp-kyc.md).

```json
{
  "response_status_id": 0,
  "data": {
    "reference_tid": "EKYKF4719702240123152147525I",
    "otp_ref_id": "2465238"
  },
  "response_type_id": 1600,
  "message": "OTP request has been sent",
  "status": 0
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `346` | AePS Fingpay service not activated for this agent |
| 200 | `-1` | Incorrectly encrypted Aadhaar |