---
title: "Send Transaction OTP API Reference"
description: "Request an OTP to the sender's mobile to authorise a DigiKhata transfer."
canonical: "https://eps.eko.in/docs/ppi-digikhata-send-transaction-otp"
---


> **Canonical URL:** https://eps.eko.in/docs/ppi-digikhata-send-transaction-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/ppi-digikhata/otp`

Request an OTP to the sender's mobile to authorise a DigiKhata transfer.

Dispatches an OTP to the sender for an upcoming transfer to a given recipient and amount. Returns an `otp_ref_id` to pass, with the OTP, into Initiate Transaction.

> View product & pricing details: [PPI Wallet](https://eps.eko.in/products/ppi-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 | integer | yes | Unique ID generated while adding the recipient. e.g. 10017740 |
| amount | integer | yes | Amount to be transferred (INR). e.g. 110 |
| customer_id | string | yes | Sender's 10-digit mobile number. e.g. 8617567988 |
| service_code | integer | no | Fixed service code. Send 80. e.g. 80 |
| beneficiary_id | string | no | Beneficiary ID generated when adding the recipient's bank. e.g. 4202888 |

## 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 | OTP session reference — pass to Initiate Transaction. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "recipient_id": 10017740,
  "amount": 110,
  "customer_id": "8617567988",
  "service_code": 80,
  "beneficiary_id": "4202888"
}
```

## Example response

```json
{
  "response_status_id": 1,
  "data": {
    "otp_ref_id": "zCISyglexo0Pjqp4YrS2ssweuD9v1c3aLKGxjTW8wU7An8Wem1UyNws5830yh7q/sf5J4R3BY="
  },
  "response_type_id": 2133,
  "message": "Send OTP",
  "status": 2133
}
```