---
title: "Activate AePS Fingpay for Agent API Reference"
description: "Enable AePS Fingpay service for your agent by submitting their biometric device details and KYC documents."
canonical: "https://eps.eko.in/docs/activate-aeps-fingpay"
---


> **Canonical URL:** https://eps.eko.in/docs/activate-aeps-fingpay
> 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.

# Activate AePS Fingpay for Agent API Reference

`PUT https://staging.eko.in/ekoapi/v3/admin/network/agent/{user_code}/aeps-fingpay/activate`

Enable AePS Fingpay service for your agent by submitting their biometric device details and KYC documents.

This API enables an agent (identified by their `user_code`) to use the AePS Fingpay service. It accepts the agent's biometric device model, serial number, address proofs, and KYC documents (PAN card, Aadhaar front and back) as a multipart form submission. After submission, the activation enters a 'pending' state and is approved within 2–3 business days. Only activated agents can perform AePS transactions. File uploads must be JPEG/JPG/PDF format, each under 1 MB; PNG is not accepted.

> [!NOTE]
> This API must be called after onboarding your agent using the [**Onboard User API**](/docs/onboard-user).

> [!WARNING]
> The approval may take 1-2 business days.

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

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| user_code | string | yes | Unique code of the agent for whom AePS Fingpay service is being activated. e.g. 20810200 |

## 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 |
| modelname | string | yes | Model name/designation of the UIDAI-certified biometric device (e.g., Morpho 1300E3, Mantra MFS100). e.g. Morpho 1300E3 |
| devicenumber | string | yes | Serial number of the biometric device as printed on the device or its packaging. e.g. SN1234567890 |
| shop_type | number | yes | The shop-type ID of the Agent. Use `Get Shop Types` API for a list of shop-types and corresponding IDs e.g. 4215 |
| office_address | object | yes | Agent's current office/operating address as a JSON object with keys: line, city, state, state_id, pincode. To get state_id, see the `Get States` API e.g. [object Object] |
| address_as_per_proof | object | yes | Agent's address exactly as it appears on the submitted address proof document. JSON object with keys: line, city, state, sate_id, pincode. To get state_id, see the `Get States` API e.g. [object Object] |
| pan_card | file | yes | PAN card document upload (multipart/form-data). Accepted formats: JPEG, JPG, PDF. Max size: 1 MB. PNG not accepted. e.g. <binary file> |
| aadhar | string | yes | 12-digit Aadhaar number of the sender. e.g. 123456789012 |
| aadhar_front | file | yes | Front side of the Aadhaar card (multipart/form-data). Accepted formats: JPEG, JPG, PDF. Max size: 1 MB. e.g. <binary file> |
| aadhar_back | file | yes | Back side of the Aadhaar card (multipart/form-data). Accepted formats: JPEG, JPG, PDF. Max size: 1 MB. e.g. <binary file> |
| latlong | string | yes | GPS coordinates of the agent for whom AePS Fingpay service is being activated. Format: <latitude,longitude> e.g. 28.6139,77.2090 |

## 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 | multipart/form-data — let your HTTP client set this header itself (it generates the required boundary); do not hardcode the value. e.g. multipart/form-data |

## 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.service_status_desc ⭐ | string | Current state of the AePS Fingpay activation request. 'pending' means documents are submitted and under review. |
| data.service_status ⭐ | number | State-id of the AePS Fingpay activation request. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 1259 | AePS Registration Successful | [dmt-onboard-sender](https://eps.eko.in/docs/dmt-onboard-sender.md) |
| 1297 | User does not exist | [onboard-user](https://eps.eko.in/docs/onboard-user.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "modelname": "Morpho 1300E3",
  "devicenumber": "SN1234567890",
  "shop_type": 4215,
  "office_address": {
    "line": "Shop No. 5, Gandhi Market",
    "city": "Gurgaon",
    "state": "Haryana",
    "state_id": 23,
    "pincode": "122003"
  },
  "address_as_per_proof": {
    "line": "Shop No. 5, Gandhi Market",
    "city": "Gurgaon",
    "state": "Haryana",
    "state_id": 23,
    "pincode": "122003"
  },
  "pan_card": "<binary file>",
  "aadhar": "123456789012",
  "aadhar_front": "<binary file>",
  "aadhar_back": "<binary file>",
  "latlong": "28.6139,77.2090"
}
```

## Example response

`response_type_id` `1259` — AePS Registration Successful. Next step: [dmt-onboard-sender](https://eps.eko.in/docs/dmt-onboard-sender.md).

```json
{
  "status": 0,
  "response_status_id": 0,
  "response_type_id": 1259,
  "message": "AePS Registration Successful",
  "data": {
    "service_status_desc": "Activated",
    "balance": "",
    "user_code": "37659001",
    "initiator_id": "7042769383",
    "service_status": "1",
    "service_code": "43",
    "remarks": ""
  }
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 200 | `1297` — User does not exist | Agent not onboarded |