Eko Platform Services Logo

    POSTAePS Fingpay — Biometric eKYC

    Complete one-time AePS Fingpay eKYC by submitting the agent's Aadhaar and live biometric fingerprint capture.

    POST/customer/aeps/fingpay/kyc/biometric

    The final step in the one-time AePS Fingpay eKYC flow, called after OTP verification. Submits the agent's Aadhaar and biometric PID data to UIDAI for identity verification. On success, the agent's eKYC is marked complete and they can start performing AePS transactions (subject to completing daily 2FA each day). This step uses the same RSA-encrypted Aadhaar and PID XML format as the transaction APIs.

    Body parameters

    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

    aadhaarstringRequired

    RSA-encrypted, Base64-encoded Aadhaar number of the agent.

    example: BASE64_ENCRYPTED_AADHAAR

    piddatastringRequired

    PID XML string from the UIDAI-certified biometric device (fType=2, Data type='X', mc in DeviceInfo).

    example: <?xml version='1.0'?><PidData><Data type='X'>...</Data><DeviceInfo mc='...' /></PidData>

    otp_ref_idstringRequired

    Reference ID returned by the Send OTP (eKYC) API, linking this biometric capture to the verified OTP session.

    example: OTPREF20240101001

    Headers

    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.

      • kyc_statusstring

        Result of the eKYC verification. 'completed' means the agent is now KYC-verified for AePS.

      • aadhaar_ref_numstring

        UIDAI authentication reference number for the biometric capture.