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


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

Onboard an agent for AePS Fingpay service by submitting their biometric device details and KYC documents.

This onboarding API registers an agent (identified by their user_code) for 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.

> 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 |
| 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 |
| office_address | object | yes | Agent's current office/operating address as a JSON object with keys: line, city, state, pincode. 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, pincode. e.g. [object Object] |
| pan_card | string | 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_front | string | 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 | string | yes | Back side of the Aadhaar card (multipart/form-data). Accepted formats: JPEG, JPG, PDF. Max size: 1 MB. e.g. <binary file> |

## 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.activation_status ⭐ | string | Current state of the AePS Fingpay activation request. 'pending' means documents are submitted and under review. |
| data.activation_id ⭐ | string | Unique identifier for this activation request, for tracking and support. |
| data.message | string | Human-readable message about the activation status. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "modelname": "Morpho 1300E3",
  "devicenumber": "SN1234567890",
  "office_address": {
    "line": "Shop No. 5, Gandhi Market",
    "city": "Patna",
    "state": "Bihar",
    "pincode": "800001"
  },
  "address_as_per_proof": {
    "line": "Shop No. 5, Gandhi Market",
    "city": "Patna",
    "state": "Bihar",
    "pincode": "800001"
  },
  "pan_card": "<binary file>",
  "aadhar_front": "<binary file>",
  "aadhar_back": "<binary file>"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "AePS Fingpay activation request submitted successfully. Approval expected within 2-3 business days.",
  "response_type_id": 1388,
  "data": {
    "activation_status": "pending",
    "activation_id": "ACT20240101001",
    "message": "Activation request submitted. Approval expected within 2-3 business days."
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 400 | File format not accepted (PNG uploaded) |
| 400 | File size exceeds 1 MB |
| 200 | Agent user_code not found |