---
title: "Load Sender DigiKhata Wallet API Reference"
description: "Load funds into a DigiKhata sender's prepaid wallet."
canonical: "https://eps.eko.in/docs/ppi-digikhata-load-wallet"
---


> **Canonical URL:** https://eps.eko.in/docs/ppi-digikhata-load-wallet
> 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.

# Load Sender DigiKhata Wallet API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/ppi-digikhata/sender/{customer_id}/wallet/loadwallet`

Load funds into a DigiKhata sender's prepaid wallet.

Credits the sender's DigiKhata wallet with the given amount. Returns a transaction id (`tid`) and the fee charged for the load.

> View product & pricing details: [PPI Wallet](https://eps.eko.in/products/ppi-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| customer_id | string | yes | Sender's 10-digit mobile number. e.g. 8617567988 |

## 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 |
| amount | string | yes | Amount to load into the wallet (INR). e.g. 500 |
| org_id | string | yes | Organisation identifier. Defaults to 1. e.g. 1 |

## 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.tid ⭐ | string | Eko transaction ID for the wallet load. |
| data.fee | string | Fee charged for the wallet load (INR). |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "amount": "500",
  "org_id": "1"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "fee": "5.0",
    "description": "",
    "customer_id": "",
    "bank_ref_num": "",
    "tid": "355419717321"
  },
  "response_type_id": 2447,
  "message": "The Digi Khata wallet has been loaded successfully.",
  "status": 0
}
```