---
title: "Onboard Sender API Reference"
description: "Register a new customer as a DMT-Fino sender using basic KYC details."
canonical: "https://eps.eko.in/docs/dmt-onboard-sender"
---


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

# Onboard Sender API Reference

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

Register a new customer as a DMT-Fino sender using basic KYC details.

Registers a new customer in the DMT-Fino system. Provide the customer's name, date of birth, and residence address. On success the sender is created in a pending state; biometric eKYC (via Sender KYC) must follow to activate full monthly limits. An OTP is dispatched to the customer's mobile number for confirmation.

> 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 (used as customer identifier). 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 |
| 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 |
| name | string | yes | Full name of the sender as per their ID proof. e.g. Ramesh Kumar |
| dob | string | yes | Date of birth in YYYY-MM-DD format. e.g. 1990-05-15 |
| residence_address | string | yes | Customer's residence address as a JSON-encoded array of address lines. e.g. ["123 Main Street", "Connaught Place", "New Delhi", "110001"] |

## 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.customer_id ⭐ | string | Mobile number of the newly registered sender. |
| data.state | number | Account state: 10=Pending KYC verification. |
| data.otp_ref_id | string | Reference ID for the OTP sent to the sender's mobile. Used in the Validate eKYC OTP step. |
| data.available_limit | number | Initial transfer limit before eKYC (in INR). Typically ₹5,000. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "name": "Ramesh Kumar",
  "dob": "1990-05-15",
  "residence_address": "[\"123 Main Street\", \"Connaught Place\", \"New Delhi\", \"110001\"]"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Customer registered successfully",
  "response_type_id": 1388,
  "data": {
    "customer_id": "9123456789",
    "state": 10,
    "otp_ref_id": "OTP20240101001",
    "available_limit": 5000
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Sender already exists in the system |