---
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 opened on Eko but KYC on Fino is still pending — complete biometric eKYC (Sender eKYC → Validate eKYC OTP) next. If the sender was already onboarded on Fino externally, the response instead matches the KYC-complete profile from Get Sender Profile (response_type_id 309) and no eKYC is required. After onboarding, call Get Sender Profile to read the sender's current stage.

> 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 |
| client_ref_id | string | no | Unique reference ID per API call, generated by your system (max 20 characters). e.g. 2026010100123456789 |
| 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 object with keys: line, city, state, pincode, district, area. e.g. {"line":"India","city":"Indore","state":"Madhya Pradesh","pincode":"226024","district":"Indore","area":"gita bhavan"} |

## 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 reference placeholder returned with the KYC-pending status. Empty until eKYC is initiated via Sender eKYC. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 2134 | Onboarded, KYC pending — proceed to Sender eKYC | [dmt-fino-sender-ekyc](https://eps.eko.in/docs/dmt-fino-sender-ekyc.md) |
| 300 | Already onboarded, KYC pending — re-check stage with Get Sender Profile | [dmt-get-sender](https://eps.eko.in/docs/dmt-get-sender.md) |
| 309 | Already onboarded on Fino — KYC complete, proceed to Recipients | [dmt-get-recipients](https://eps.eko.in/docs/dmt-get-recipients.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "name": "Ramesh Kumar",
  "dob": "1990-05-15",
  "residence_address": "{\"line\":\"India\",\"city\":\"Indore\",\"state\":\"Madhya Pradesh\",\"pincode\":\"226024\",\"district\":\"Indore\",\"area\":\"gita bhavan\"}"
}
```

## Example response

`response_type_id` `2134` — Onboarded, KYC pending — proceed to Sender eKYC. Next step: [dmt-fino-sender-ekyc](https://eps.eko.in/docs/dmt-fino-sender-ekyc.md).

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Customer KYC Pending",
  "response_type_id": 2134,
  "data": {
    "otp_ref_id": ""
  }
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `300` — Already onboarded, KYC pending — re-check stage with Get Sender Profile | Alternate success — sender already onboarded on Eko, KYC pending |