> For the complete documentation index, see [llms.txt](https://docs.digiledge.in/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digiledge.in/untitled/bbps/bbps-biller-integration/bbps-api-list/status-402-api.md).

# STATUS 402 API

<figure><img src="/files/tq2Wa0bIJcpQ2uxx5NAa" alt=""><figcaption></figcaption></figure>

* NPCI sends the Transaction Status Request to BOU.
* BOU forwards the Transaction Status Request to Biller.
* Biller sends the Transaction Status Request Acknowledgement to BOU, immediately upon receiving the request.
* After Biller processes the request, the resulting Transaction Status Request is sent to BOU.
* Once BOU receives the Transaction Status Response, a Transaction Status Response Acknowledgement is sent to Biller.
* BOU forwards the Transaction Status Response to NPCI.
* On receiving the Transaction Status Response, NPCI sends Transaction Status Response to BOU.
* Once BOU receives the Transaction Status Response from NPCI, they send the corresponding notification to Biller.

**STATUS 402 API is used to check the status of the bill transaction**

#### <mark style="color:blue;">**Request Parameters**</mark>

**The various parameters are explained below:**

| Parent Property/Element                | Property/Element Name        | Mandatory | Data Type | Description                                                                                                                                                                                                     |
| -------------------------------------- | ---------------------------- | --------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| \[ROOT] (No parent property / element) | refId                        | M         | String    | Unique identification assigned by the initiating BBPOU to unambiguously identify the transaction which is passed on, unchanged, throughout the entire end- to-end chain, binding the Fetch and Payment messages |
|                                        | txn                          | M         | String    | Transaction information passed throughout the system.                                                                                                                                                           |
|                                        | txn.ts                       | M         | String    | Transmission date and time of the transaction                                                                                                                                                                   |
|                                        | txn.xchange                  | M         | String    | Identification of the type of the request – transaction status (402)                                                                                                                                            |
|                                        | txnStatusReq                 | M         | String    | Information pertaining to transaction status request                                                                                                                                                            |
|                                        | txnStatusReq.msgId           | M         | String    | Unique identification assigned by the initiating BBPOU for chaining a request and response message                                                                                                              |
|                                        | txnStatusReq.txnRefere nceId | M         | String    | Transaction reference number used by the Customer for referring to a Payment transaction                                                                                                                        |
|                                        |                              |           |           |                                                                                                                                                                                                                 |

<mark style="color:blue;">**Expected Acknowledgement Parameters**</mark>

**The various parameters are explained below:**

| Parent Property/Element                | Property/Element Name | Mandatory | Data Type                               | Description                 |
| -------------------------------------- | --------------------- | --------- | --------------------------------------- | --------------------------- |
| \[ROOT] (No parent property / element) | reason                | M         | String Min Length – 1, Max Length – 100 | Reason of the Status        |
|                                        | code                  | M         | String Fixed Length 3                   | Response code for a request |
|                                        | status                | M         | String Min Length – 1, Max Length – 100 | Status of given request     |

<mark style="color:blue;">**Json Formatted Request Example**</mark>

```json
   
     {
    "refId": "String", "txn": {
    "ts": "String",
    "xchangeId": "String"
    },
    "txnStatusReq": { "msgId": "String",
    "txnReferenceId": "String"
    },
    "tenantId" : "String"
    }
```

<mark style="color:blue;">**Json Formatted Response Example**</mark>

```json
{
"reason":"String",
"code":"Integer", "status":"String"
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digiledge.in/untitled/bbps/bbps-biller-integration/bbps-api-list/status-402-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.