POSTOnboard Sender

POST/customer/payment/dmt-fino/sender/{customer_id}

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.

Tip

This endpoint is one step in a complete workflow:

DMT (Fino) — Send Money — Full Fino DMT money-transfer flow: look up the sender, onboard and biometric-eKYC them if new, pick or add the recipient, then send an OTP-verified transfer.

Request

Path parameters

Field	Type	Required	Description
`customer_id`	string	required	Sender's 10-digit mobile number (used as customer identifier).e.g. 9123456789

customer_idstringRequired

Sender's 10-digit mobile number (used as customer identifier).

example: 9123456789

Body parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`client_ref_id`	string	optional	Unique reference ID per API call, generated by your system (max 20 characters).e.g. 2026010100123456789
`name`	string	required	Full name of the sender as per their ID proof.e.g. Ramesh Kumar
`dob`	string	required	Date of birth in YYYY-MM-DD format.e.g. 1990-05-15
`residence_address`	string	required	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"}

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

client_ref_idstringoptional

Unique reference ID per API call, generated by your system (max 20 characters).

example: 2026010100123456789

namestringRequired

Full name of the sender as per their ID proof.

example: Ramesh Kumar

dobstringRequired

Date of birth in YYYY-MM-DD format.

example: 1990-05-15

residence_addressstringRequired

Customer's residence address as a JSON-encoded object with keys: line, city, state, pincode, district, area.

example: {"line":"India","city":"Indore","state":"Madhya Pradesh","pincode":"226024","district":"Indore","area":"gita bhavan"}

These headers authenticate and sign every request. See How Auth Works for details.

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Response types

response_type_id	Meaning	Next step
`2134`	Onboarded, KYC pending — proceed to Sender eKYC	Sender eKYC (Biometric)
`300`	Already onboarded, KYC pending — re-check stage with Get Sender Profile	Get Sender Profile
`309`	Already onboarded on Fino — KYC complete, proceed to Recipients	Get Recipients

Responses

2134Onboarded, KYC pending — proceed to Sender eKYCNext:Sender eKYC (Biometric)

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- otp_ref_idstring
  OTP reference placeholder returned with the KYC-pending status. Empty until eKYC is initiated via Sender eKYC.

Next steps

NextPUTSender eKYC (Biometric)Initiate biometric Aadhaar eKYC to verify and upgrade a DMT sender's account.