PUTValidate eKYC OTP

Confirm sender eKYC by verifying the OTP sent to the Aadhaar-linked mobile.

PUT/customer/payment/dmt-fino/sender/{customer_id}/otp/verify

Final step of the sender eKYC flow. Submit the OTP received on the Aadhaar-linked mobile number along with the otp_ref_id and kyc_request_id from the Sender eKYC response. On success the sender's account is upgraded to fully KYC-verified status with a ₹25,000 monthly limit.

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.e.g. 9123456789

customer_idstringRequired

Sender's 10-digit mobile number.

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
`otp`	string	required	One-time password received on the sender's Aadhaar-linked mobile number.e.g. 784512
`otp_ref_id`	string	required	OTP reference ID returned by the Sender eKYC (or Onboard Sender) API call.e.g. OTPREF20240101001
`kyc_request_id`	string	required	KYC request identifier returned by the Sender eKYC API call.e.g. KYC20240101001

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

otpstringRequired

One-time password received on the sender's Aadhaar-linked mobile number.

example: 784512

otp_ref_idstringRequired

OTP reference ID returned by the Sender eKYC (or Onboard Sender) API call.

example: OTPREF20240101001

kyc_request_idstringRequired

KYC request identifier returned by the Sender eKYC API call.

example: KYC20240101001

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

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.
- user_codestring
  Agent user code for the now KYC-verified sender. eKYC is complete on success.

PUTValidate eKYC OTP

Request

Path parameters

Body parameters

Responses

Next steps

Related