---
title: "Add Recipient API Reference"
description: "Register a new beneficiary under a sender's DMT-Fino account."
canonical: "https://eps.eko.in/docs/dmt-add-recipient"
---


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

# Add Recipient API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/dmt-fino/sender/{customer_id}/recipient`

Register a new beneficiary under a sender's DMT-Fino account.

Adds a new beneficiary to the sender's saved recipients list. Provide the recipient's full name, bank account number, IFSC code, and mobile number. On success a recipient_id is returned; use it in Send Transaction OTP and Execute Transaction. The system may validate the account via penny-drop before activating the recipient.

> 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. 9123456789 |

## 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 (max 20 characters). e.g. 2026010100123456789 |
| recipient_mobile | string | yes | Beneficiary's 10-digit mobile number. e.g. 9002331157 |
| recipient_name | string | yes | Full name of the beneficiary as it appears on their bank account. e.g. yashwant basnett |
| ifsc | string | yes | IFSC code of the beneficiary's bank branch. e.g. SBIN0007515 |
| account | string | yes | Beneficiary's bank account number. e.g. 38759149196 |

## 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.recipient_id ⭐ | number | Unique identifier assigned to the newly added recipient. Required for Send Transaction OTP and Execute Transaction. |
| data.customer_id | string | Sender's mobile number (echoed back). |
| data.recipient_mobile | string | Beneficiary mobile number (echoed back). |
| data.initiator_id | string | Partner initiator ID (echoed back). |
| data.pipes | object | Available settlement pipes for the new recipient. |
| data.otp_ref_id | string | OTP reference placeholder (empty on add). |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 43 | Recipient added — proceed to Send Transaction OTP | [dmt-send-otp](https://eps.eko.in/docs/dmt-send-otp.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "recipient_mobile": "9002331157",
  "recipient_name": "yashwant basnett",
  "ifsc": "SBIN0007515",
  "account": "38759149196"
}
```

## Example response

`response_type_id` `43` — Recipient added — proceed to Send Transaction OTP. Next step: [dmt-send-otp](https://eps.eko.in/docs/dmt-send-otp.md).

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Success!Please transact using Recipientid",
  "response_type_id": 43,
  "data": {
    "recipient_id": 117015428,
    "customer_id": "9155927131",
    "recipient_mobile": "9002331157",
    "initiator_id": "<initiator_id>",
    "pipes": {},
    "otp_ref_id": ""
  }
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `-1` | Recipient already registered for this sender |
| 200 | `-1` | Customer does not exist in system |