---
title: "Pay BBPS Bill API Reference"
description: "Process a bill payment or recharge for any BBPS-connected biller."
canonical: "https://eps.eko.in/docs/bbps-pay-bill"
---


> **Canonical URL:** https://eps.eko.in/docs/bbps-pay-bill
> 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.

# Pay BBPS Bill API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/bbps`

Process a bill payment or recharge for any BBPS-connected biller.

The core money-debit API that executes a bill payment or prepaid recharge on the BBPS network. For operators where `billFetchResponse = 1`, the `billfetchresponse` token returned by the Fetch Bill API must be included.

> View product & pricing details: [Bharat Bill Payment System (BBPS)](https://eps.eko.in/products/bbps-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 |
| utility_acc_no | string | yes | Customer's account or consumer number with the biller. e.g. 1234567890 |
| confirmation_mobile_no | string | yes | Customer's mobile number for payment confirmation. e.g. 9999988888 |
| sender_name | string | yes | Customer's full name. e.g. Ramesh Kumar |
| operator_id | string | yes | Biller identifier from the Get Operators response. e.g. 83 |
| amount | string | yes | Payment amount in rupees (e.g. '1350' for ₹1,350). e.g. 1350 |
| source_ip | string | yes | IP address of the agent or retailer making this request. e.g. 192.168.1.1 |
| latlong | string | yes | Agent's GPS coordinates as `latitude,longitude`. Mandatory for agent activation compliance. e.g. 28.6139,77.2090 |
| billfetchresponse | string | no | The opaque token returned by the Fetch Bill API. Required when the operator's `billFetchResponse = 1`. e.g. eyJhbGciOiJSUzI1NiJ9... |
| dob | string | no | Date of birth of the policy holder in DD/MM/YYYY format. Required for LIC policy payments. e.g. 15/08/1985 |
| postalcode | number | no | 6-digit PIN code of the customer. Required for MSEB electricity payments. e.g. 400001 |

## 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. |
| tx_status | string | Transaction state: 0=Success, 1=Fail, 2=Awaited, 3=Refund Pending, 4=Refunded, 5=On Hold. |
| txstatus_desc | string | Human-readable transaction status. |
| data | object | API-specific response payload. |
| data.tid ⭐ | string | Eko's unique transaction identifier. Use this for status enquiry and dispute resolution. |
| data.operator_ref_id ⭐ | string | Reference number issued by the biller / BBPS network confirming receipt of payment. |
| data.amount ⭐ | string | Amount debited for this transaction. |
| data.balance | string | Remaining wallet balance of the agent after this transaction. |
| data.utility_acc_no | string | Consumer/account number against which the payment was made. |
| data.client_ref_id | string | Your reference ID echoed back. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "utility_acc_no": "1234567890",
  "confirmation_mobile_no": "9999988888",
  "sender_name": "Ramesh Kumar",
  "operator_id": "83",
  "amount": "1350",
  "source_ip": "192.168.1.1",
  "latlong": "28.6139,77.2090",
  "billfetchresponse": "eyJhbGciOiJSUzI1NiJ9...",
  "dob": "15/08/1985",
  "postalcode": 400001
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Bill payment successful",
  "response_type_id": 2,
  "tx_status": "0",
  "txstatus_desc": "Success",
  "data": {
    "tid": "1734567890",
    "operator_ref_id": "BBPS202406011234",
    "amount": "1350",
    "balance": "4820.50",
    "utility_acc_no": "1234567890",
    "client_ref_id": "BBPS-20240601-001"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Insufficient agent wallet balance |
| 200 | Transaction awaited — biller not confirmed yet |
| 200 | Amount mismatch — pay amount differs from fetched bill |