---
title: "Validate Sender Aadhaar OTP API Reference"
description: "Verify the Aadhaar OTP for a DMT Levin sender to complete identity validation."
canonical: "https://eps.eko.in/docs/aadhaar-dmt-levin-verify-otp"
---


> **Canonical URL:** https://eps.eko.in/docs/aadhaar-dmt-levin-verify-otp
> 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.

# Validate Sender Aadhaar OTP API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/dmt-levin/sender/{customer_id}/aadhaar/otp/verify`

Verify the Aadhaar OTP for a DMT Levin sender to complete identity validation.

Validates the OTP received on the sender's Aadhaar-linked mobile number in the DMT Levin flow. Use `intent_id: 20` for Aadhaar validation (as opposed to `intent_id: 19` for sender onboarding). On success, the sender's identity is confirmed and their DMT Levin wallet profile is updated.

> View product & pricing details: [Domestic Money Transfer (DMT)](https://eps.eko.in/products/dmt-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| customer_id | string | yes | Sender's mobile number. e.g. 9876543210 |

## Body parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| user_code | string | yes | User code of the retailer/agent the service is run for. e.g. 20810200 |
| client_ref_id | string | no | Unique reference id per API call, generated by your system. e.g. REQ-20260101-001 |
| otp | integer | no | OTP received on the Aadhaar-linked mobile number. e.g. 123456 |
| otp_ref_id | integer | yes | Reference ID from the Validate Aadhaar (DMT Levin) response. e.g. 93847201 |
| intent_id | string | no | Set to "19" for sender onboarding or "20" for Aadhaar validation. e.g. 20 |
| additional_info | string | no | Additional info flag. Defaults to 1. e.g. 1 |

## 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.verified ⭐ | boolean | True if Aadhaar OTP validation was successful. |
| data.name ⭐ | string | Verified sender name from Aadhaar. |
| data.gender ⭐ | string | Gender from Aadhaar record. |
| data.dob ⭐ | string | Date of birth from Aadhaar. |
| data.masked_aadhaar ⭐ | string | Aadhaar number with first 8 digits masked. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "otp": 123456,
  "otp_ref_id": 93847201,
  "intent_id": "20",
  "additional_info": "1"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Aadhaar OTP verified successfully",
  "response_type_id": 1388,
  "data": {
    "verified": true,
    "name": "Arjun Mehta",
    "gender": "M",
    "dob": "10-01-1988",
    "masked_aadhaar": "XXXX-XXXX-3456"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Wrong OTP |
| 200 | OTP expired |