Fintech APIs & Platform for KYC, Verification & Transactions in India | Eko Platform Services
Eko Platform Services Logo
Open in ChatGPTOpen in ClaudeView as Markdown
Get Postman CollectionDownload OpenAPI

PUTSender eKYC (Biometric)

Initiate biometric Aadhaar eKYC to verify and upgrade a DMT sender's account.

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

Performs biometric Aadhaar eKYC for a DMT-Fino sender. The agent captures a live fingerprint at their terminal; the resulting PID XML and the sender's Aadhaar number are submitted here. On success an OTP is dispatched for confirmation — call Validate eKYC OTP next. A successful eKYC raises the sender's monthly limit from ₹5,000 to ₹25,000.

Biometric (PID) capture

Capture is done client-side against an RD-service device on ports 11100–11112. Supported RD services include Mantra, Morpho, SecuGen (Level 0), Precision, Startek FM220, and NEXT.

Note

New to RDService? The Aadhaar Biometric Authentication guide covers the full capture flow — driver discovery, PidOptions, error codes — for Web and Android, and includes an in-browser device tester.

The captured PidData XML uses these parameters:

xml
<PidOptions ver="1.0">
  <Opts fCount="1" fType="2" pidVer="2.0" timeout="10000" env="P" wadh="E0jzJ/P8UopUHAieZn8CKqS4WPMi5ZSYXgfnlfkWjrc=" />
</PidOptions>
Important

When generating the PID block with custom code, you must include the wadh value above alongside fCount and fType. Validate the device response's errCode before submitting.

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

customer_idstringRequired

Sender's 10-digit mobile number.

example: 9123456789

Body parameters

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

aadharstringRequired

12-digit Aadhaar number of the sender.

example: 234567890123

piddatastringRequired

XML-encoded biometric PID data captured from a certified biometric device (fingerprint scanner).

example: <PidData><Resp errCode="0" errInfo="Capture Success" .../></PidData>

Response types

response_type_idMeaningNext step
2129OTP sent — proceed to Validate eKYC OTPValidate eKYC OTP

Responses

2129OTP sent — proceed to Validate eKYC OTPNext:Validate eKYC OTP

  • 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 associated with the KYC request.

    • intent_idstring

      Reserved intent identifier (empty in the standard flow).

    • kyc_request_idstring

      Unique identifier for this KYC request. Required for the Validate eKYC OTP step.

    • otp_ref_idstring

      Reference ID for the OTP sent to the sender's Aadhaar-linked mobile. Required for the Validate eKYC OTP step.

Next steps

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

Related