---
title: "BBPS Transaction Status API Reference"
description: "Check the current status of a BBPS bill payment by Eko TID or your client reference ID."
canonical: "https://eps.eko.in/docs/bbps-transaction-status"
---


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

# BBPS Transaction Status API Reference

`GET https://staging.eko.in/ekoapi/v3/tools/reference/transaction/{transaction-reference}`

Check the current status of a BBPS bill payment by Eko TID or your client reference ID.

Generic transaction enquiry endpoint that works for all Eko transaction types including BBPS. Pass either the Eko `tid` or your `client_ref_id` as the path parameter. Returns the current `tx_status` (0=Success, 1=Fail, 2=Awaited, 3=Refund Pending, 4=Refunded, 5=On Hold), the operator reference, and the debited amount. Use this to handle `tx_status=2` (Response Awaited) cases from Pay Bill. A timeout or slow bank response is not a failure — re-query with your `client_ref_id` to get the real status instead of retrying the payment.

> View product & pricing details: [Bharat Bill Payment System (BBPS)](https://eps.eko.in/products/bbps-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| transaction-reference | string | yes | Eko TID (`tid`) or your `client_ref_id` that uniquely identifies the transaction. e.g. 1734567890 |

## Query parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |

## 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's transaction ID. |
| data.amount ⭐ | string | Transaction amount in rupees. |
| data.operator_ref_id ⭐ | string | Biller or BBPS network reference number. |
| data.utility_acc_no | string | Consumer/account number for which the bill was paid. |

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Transaction found",
  "response_type_id": 1388,
  "data": {
    "tid": "1734567890",
    "tx_status": "0",
    "txstatus_desc": "Success",
    "amount": "1350",
    "operator_ref_id": "BBPS202406011234",
    "utility_acc_no": "1234567890"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Transaction not found for the given reference |