---
title: "Add Settlement Bank Account API Reference"
description: "Register a bank account as an AePS fund-settlement recipient for an agent."
canonical: "https://eps.eko.in/docs/aeps-add-settlement-account"
---


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

# Add Settlement Bank Account API Reference

`POST https://staging.eko.in/ekoapi/v3/user/payment/aeps/settlement/account`

Register a bank account as an AePS fund-settlement recipient for an agent.

Adds and name-verifies a bank account to which an agent can settle AePS funds. On success a `recipient_id` is returned — pass it to Initiate Settlement. If the account holder name does not match, the response reports the mismatch.

> 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 |
| user_code | string | yes | User code of the retailer/agent the service is run for. e.g. 20810200 |
| client_ref_id | string | no | Unique reference id per API call, generated by your system. e.g. REQ-20260101-001 |
| bank_id | integer | yes | Unique identifier for the bank. e.g. 12 |
| ifsc | string | yes | IFSC code of the bank account. e.g. BKID0006701 |
| service_code | integer | yes | Service code for AePS fund settlement. Value: 39. e.g. 39 |
| account | string | yes | Account number of the user's bank account. e.g. 987867867967969 |

## 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.recipient_id ⭐ | number | Settlement recipient identifier — pass to Initiate Settlement. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "bank_id": 12,
  "ifsc": "BKID0006701",
  "service_code": 39,
  "account": "987867867967969"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "recipient_id": 1893
  },
  "response_type_id": 1336,
  "message": "Account added",
  "status": 0
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Account verification failed — name mismatch |
| 200 | Account verification failed — name not returned by bank |