---
title: "Daily KYC API Reference"
description: "Perform the mandatory daily biometric re-verification that authorises an agent to carry out AePS transactions for the current calendar day."
canonical: "https://eps.eko.in/docs/aeps-fingpay-daily-auth"
---


> **Canonical URL:** https://eps.eko.in/docs/aeps-fingpay-daily-auth
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Daily KYC API Reference

`PUT https://staging.eko.in/ekoapi/v3/user/collection/aeps-fingpay/kyc/biometric/daily`

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

Biometric-only re-verification for the days after the one-time eKYC — no OTP step is required. AePS Fingpay requires every agent to re-authenticate themselves biometrically at the start of each working day, before their first transaction of the day.

If this fails with reason `Please complete bank eKYC to process the transaction.`, re-run the full first-time eKYC sequence — Send OTP → Verify OTP → Biometric — before retrying.

To capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).

> View product & pricing details: [AePS Cashout](https://eps.eko.in/products/aeps-api.md)

## Body parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| client_ref_id | string | no | Unique reference ID per API call, generated by your system (max 20 characters). e.g. 2026010100123456789 |
| user_code | string | yes | Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your users e.g. 20810200 |
| aadhar | string | yes | RSA-encrypted, Base64-encoded Aadhaar number of the agent performing daily KYC. e.g. BASE64_ENCRYPTED_AADHAAR |
| customer_id | string | yes | Registered mobile number of the agent/merchant. e.g. 9123456789 |
| latlong | string | yes | GPS coordinates of the agent's location at the time of daily KYC. e.g. 28.6139,77.2090 |
| piddata | string | yes | 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. If you generate the PID block yourself, the value of `wadh` must be blank/empty for Daily KYC. e.g. <?xml version='1.0'?><PidData><Data type='X'>...</Data><DeviceInfo mc='...' /></PidData> |
| bank_code | string | yes | Eko bank code of the agent's bank. Resolve it using the [Get List of Banks](./get-banks) API. e.g. HDFC |

## Headers

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| developer_key | string | yes | Static API key issued to your account after KYC. |
| secret-key | string | yes | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
| secret-key-timestamp | string | yes | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
| content-type | string | yes | application/json e.g. application/json |

## Response

⭐ marks fields highlighted as verifiable.

| Field | Type | Description |
| --- | --- | --- |
| status | number | Primary success indicator (0 = success). |
| message | string | Human-readable response / error message. |
| response_status_id | number | Granular status id; see the shared error-codes table. |
| response_type_id | number | A unique id for every possible response shape (success or error) — useful for client logic branching and analytics. |
| data | object | API-specific response payload. |
| data.user_code ⭐ | string | User code of the agent whose daily KYC is now complete for the current calendar day. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 1713 | Daily KYC successful — the agent may transact today | — |
| 1714 | Daily KYC failed — if `data.reason` is 'Please complete bank eKYC to process the transaction.', re-run the full eKYC from Send OTP | [aeps-fingpay-send-otp-kyc](https://eps.eko.in/docs/aeps-fingpay-send-otp-kyc.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "user_code": "20810200",
  "aadhar": "BASE64_ENCRYPTED_AADHAAR",
  "customer_id": "9123456789",
  "latlong": "28.6139,77.2090",
  "piddata": "<?xml version='1.0'?><PidData><Data type='X'>...</Data><DeviceInfo mc='...' /></PidData>",
  "bank_code": "HDFC"
}
```

## Example response

`response_type_id` `1713` — Daily KYC successful — the agent may transact today.

```json
{
  "response_status_id": 0,
  "data": {
    "user_code": "20810200"
  },
  "response_type_id": 1713,
  "message": "KYC sucess",
  "status": 0
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `1714` — Daily KYC failed — if `data.reason` is 'Please complete bank eKYC to process the transaction.', re-run the full eKYC from Send OTP | KYC failed — no reason returned |
| 200 | `1714` — Daily KYC failed — if `data.reason` is 'Please complete bank eKYC to process the transaction.', re-run the full eKYC from Send OTP | Invalid biometric data — check the `wadh` value in the PID block |
| 200 | `1714` — Daily KYC failed — if `data.reason` is 'Please complete bank eKYC to process the transaction.', re-run the full eKYC from Send OTP | Bank eKYC pending — re-run Send OTP → Verify OTP → Biometric first |