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


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

Request an OTP to the sender's mobile number to authorise an upcoming money transfer.

Sends an OTP to the sender's registered mobile number as a pre-authorisation step before initiating the actual money transfer. Provide the recipient_id, the transfer amount, and the sender's customer_id. The returned otp_ref_id must be passed to Initiate Transfer 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 |
| 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 |
| recipient_id | number | yes | Unique recipient ID returned by Add Recipient or Get Recipients. e.g. 98765 |
| amount | number | yes | Transfer amount in INR (integer, no decimals). e.g. 500 |
| customer_id | string | yes | Sender's 10-digit mobile number. e.g. 9123456789 |

## 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.otp_ref_id ⭐ | string | Reference ID for the OTP sent. Must be passed to Initiate Transfer along with the customer-entered OTP. |
| data.mobile | string | Masked mobile number to which the OTP was sent (for display to agent/customer). |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "recipient_id": 98765,
  "amount": 500,
  "customer_id": "9123456789"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "OTP sent successfully",
  "response_type_id": 1388,
  "data": {
    "otp_ref_id": "TXNOTP20240101001",
    "mobile": "XXXXXX6789"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Sender monthly limit exhausted |