---
title: "Send Transaction OTP API Reference"
description: "Request an OTP to the sender's mobile number to authorise an upcoming DMT-Levin transfer."
canonical: "https://eps.eko.in/docs/dmt-levin-send-otp"
---


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

# Send Transaction OTP API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/dmt-levin/otp`

Request an OTP to the sender's mobile number to authorise an upcoming DMT-Levin transfer.

> [!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.

Generates an OTP and delivers it to the sender's registered mobile number as a pre-authorisation step before the money transfer. Provide the recipient_id, the transfer amount, and the sender's customer_id. The returned otp_ref_id must be passed to the transfer call along with the OTP entered by the customer.

> View product & pricing details: [Domestic Money Transfer (DMT)](https://eps.eko.in/products/dmt-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 (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 | User code value of the retailer from whom the request is coming. e.g. 99080253 |
| recipient_id | integer | yes | Unique recipient ID returned by Add Recipient or Get Recipients. e.g. 116456986 |
| amount | integer | yes | Transfer amount in INR. e.g. 500 |
| customer_id | string | yes | Sender's 10-digit mobile number. e.g. 9999999999 |
| beneficiary_id | string | no | Unique ID generated when adding the recipient's bank details (see Get Recipients). e.g. 40378 |

## 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. |
| data.otp_ref_id ⭐ | string | Reference ID for the OTP sent. Pass it to the transfer call along with the customer-entered OTP. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 2133 | Transaction OTP sent — proceed to Initiate Transaction | [dmt-levin-initiate-transfer](https://eps.eko.in/docs/dmt-levin-initiate-transfer.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "user_code": "99080253",
  "recipient_id": 116456986,
  "amount": 500,
  "customer_id": "9999999999",
  "beneficiary_id": "40378"
}
```

## Example response

`response_type_id` `2133` — Transaction OTP sent — proceed to Initiate Transaction. Next step: [dmt-levin-initiate-transfer](https://eps.eko.in/docs/dmt-levin-initiate-transfer.md).

```json
{
  "response_status_id": 0,
  "data": {
    "otp_ref_id": "0ac275d7-2919-44ec-a64d-3a7ee0958563"
  },
  "response_type_id": 2133,
  "message": "Send OTP",
  "status": 0
}
```
