---
title: "DMT Customer KYC API Reference"
description: "Complete the one-time biometric eKYC of a DMT-Levin sender to finish registration."
canonical: "https://eps.eko.in/docs/dmt-levin-sender-ekyc"
---


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

# DMT Customer KYC API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/account/{customer_id}/dmt-levin/ekyc`

Complete the one-time biometric eKYC of a DMT-Levin sender to finish registration.

> [!WARNING]
> The UAT / Sandbox environment is not available for this API — requests to `https://staging.eko.in/ekoapi/v3` return an error response. Test it in Production.

One-time biometric eKYC using a fingerprint captured on an RD-service device, called after the sender's OTP is validated. Submit the `otp_ref_id` from Validate Sender Aadhaar OTP with the PID XML. On success (response_type_id 2132) the sender's registration is complete.

If you generate the PID block with your own code rather than the RD service default, set `wadh=E0jzJ/P8UopUHAieZn8CKqS4WPMi5ZSYXgfnlfkWjrc=` alongside `fCount`, `fType` and the other attributes.

To capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).

> 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 10-digit mobile number. e.g. 9911542536 |

## 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 (10–20 characters; 10 recommended). The SDKs generate one for every non-GET call when you don't. e.g. 2026010100123456789 |
| user_code | string | yes | 8-digit code of the registered user (partner's merchant), received in the user onboarding response. e.g. 99080253 |
| otp_ref_id | string | yes | OTP reference received in the Validate OTP response. e.g. Yd6uRIneZVJpTQRhqL6CZ1e46nmMhYYjxg40levn4pG4m+AWOZn5R29EUkNGljBEkwjW4GWlKNiPdQXFVtwHccxey5PZnPgz |
| piddata | string | yes | PID XML returned by the biometric device, passed as a string. e.g. <?xml version='1.0'?><PidData><Data type='X'>...</Data><DeviceInfo mc='...' /></PidData> |

## 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 | UI display hint only (-1/0 success, 1 failure, 2 initiated, 3 refund initiated, 4 refunded). Never branch on it — use `status` (and `tx_status` for financial APIs), or `response_type_id` where documented. |
| 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. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 2132 | Sender registration completed | [dmt-levin-get-recipients](https://eps.eko.in/docs/dmt-levin-get-recipients.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "user_code": "99080253",
  "otp_ref_id": "Yd6uRIneZVJpTQRhqL6CZ1e46nmMhYYjxg40levn4pG4m+AWOZn5R29EUkNGljBEkwjW4GWlKNiPdQXFVtwHccxey5PZnPgz",
  "piddata": "<?xml version='1.0'?><PidData><Data type='X'>...</Data><DeviceInfo mc='...' /></PidData>"
}
```

## Example response

`response_type_id` `2132` — Sender registration completed. Next step: [dmt-levin-get-recipients](https://eps.eko.in/docs/dmt-levin-get-recipients.md).

```json
{
  "response_status_id": 0,
  "response_type_id": 2132,
  "message": "Customer Registration Completed",
  "status": 0
}
```