Eko Platform Services Logo

    PUTVerify OTP (eKYC)

    Verify the eKYC OTP sent to the agent's Aadhaar-linked mobile number to advance the one-time AePS Fingpay eKYC.

    PUT/user/collection/aeps-fingpay/kyc/otp/verify

    The second step of the one-time AePS Fingpay eKYC flow (Send OTP → Verify OTP → Biometric Capture). Submits the OTP the agent received, together with the otp_ref_id and reference_tid returned by the Send OTP API, to validate the agent's identity before biometric capture. Aadhaar must be RSA-encrypted and Base64-encoded.

    Body parameters

    initiator_idstringRequired

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

    example: 9962981729

    user_codestringRequired

    Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your users

    example: 20810200

    customer_idstringRequired

    Registered mobile number of the agent/merchant undergoing eKYC.

    example: 9123456789

    aadhaarstringRequired

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

    example: BASE64_ENCRYPTED_AADHAAR

    otpstringRequired

    OTP received on the agent's Aadhaar-registered mobile number.

    example: 123456

    otp_ref_idstringRequired

    Reference ID returned by the Send OTP (eKYC) API.

    example: 2465238

    reference_tidstringRequired

    Transaction reference ID returned by the Send OTP (eKYC) API.

    example: EKYKF4719702240123152147525I

    latlongstringRequired

    Agent's GPS coordinates as `latitude,longitude`. Required for security and fraud prevention.

    example: 28.6139,77.2090

    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.

      • user_codestring

        User code of the agent whose eKYC was verified.

      • reference_tidstring

        Transaction reference ID for this eKYC verification.

      • otp_ref_idstring

        Reference ID of the OTP session. Carry forward to the Biometric eKYC step.