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

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
`user_code`	string	required	User code of the retailer/agent the service is run for.e.g. 20810200
`client_ref_id`	string	optional	Unique reference id per API call, generated by your system.e.g. REQ-20260101-001
`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 array of address lines.e.g. ["123 Main Street", "Connaught Place", "New Delhi", "110001"]

initiator_idstringRequired

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

example: 9962981729

user_codestringRequired

User code of the retailer/agent the service is run for.

example: 20810200

client_ref_idstringoptional

Unique reference id per API call, generated by your system.

example: REQ-20260101-001

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 array of address lines.

example: ["123 Main Street", "Connaught Place", "New Delhi", "110001"]

Headers

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

Responses

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