GETGet Sender Profile

Fetch the DMT-Fino profile of a registered sender by mobile number.

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

The first step in the DMT flow. Call this to check whether a customer is already registered as a DMT sender. If the sender exists, the response returns their profile and remaining transfer limits so you can skip registration. If not found (response_status_id 463), proceed to Onboard Sender.

Path parameters

Field	Type	Required	Description
`customer_id`	string	required	Sender's 10-digit mobile number.e.g. 9123456789

customer_idstringRequired

Sender's 10-digit mobile number.

example: 9123456789

Query 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

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

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
  Sender's mobile number (echoed back).
- namestring
  Registered name of the sender.
- dobstring
  Date of birth in YYYY-MM-DD format.
- kyc_verifiedboolean
  Whether the sender has completed eKYC verification.
- available_limitnumber
  Remaining transfer limit for the current month (in INR).
- used_limitnumber
  Transfer amount already used this month (in INR).
- monthly_limitnumber
  Total allowed monthly transfer limit for this sender (in INR).
- statenumber
  Sender account state: 0=Active, 10=Pending verification.