Fintech APIs & Platform for KYC, Verification & Transactions in India | Eko Platform Services
Eko Platform Services Logo

POSTDaily Authentication (2FA)

Perform the mandatory daily biometric authentication that authorises an agent to carry out AePS transactions for the current calendar day.

POST/user/collection/aeps-fingpay/kyc/biometric/daily

AePS Fingpay requires every agent to authenticate themselves biometrically at the start of each working day. This daily 2FA must be completed before the first Cash Withdrawal transaction of the day (and is available only 3 or more days after the initial eKYC is completed). The API returns a reference_id that must be included in every subsequent Cash Withdrawal request as proof of daily authentication. Daily Auth does not need to be repeated for Balance Enquiry or Mini Statement within the same day.

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.

example: REQ-20260101-001

user_codestringRequired

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

example: 20810200

aadhaarstringRequired

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

example: BASE64_ENCRYPTED_AADHAAR

piddatastringRequired

PID XML string from the UIDAI-certified biometric device (fType=2, Data type='X', mc in DeviceInfo). This represents the agent's own fingerprint, not the customer's.

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

latlongstringRequired

GPS coordinates of the agent's location at the time of daily authentication.

example: 25.5941,85.1376

source_ipstringRequired

IP address of the agent's terminal/system.

example: 103.56.78.90

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.

    • reference_idstring

      Daily authentication reference ID. Pass this as the 'reference_id' parameter in every Cash Withdrawal request made during the current day. Valid for the current calendar day only.

    • auth_statusstring

      Result of the daily biometric authentication. 'success' means the agent is cleared to perform Cash Withdrawal transactions for the day.

    • valid_tillstring

      Expiry timestamp of this daily auth token (end of the current calendar day, IST).

Next steps

Related