> 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/bill-pay-api/billpayment-response-endpoint.md).

# BillPayment Response Endpoint

### **Biller server to Biller Protocol**

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

**The various parameters are explained below:**

| Parent Property/Element                | Property/Element Name | Mandatory | Data Type                               |                                                                                                                                     |
| -------------------------------------- | --------------------- | --------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| \[ROOT] (No parent property / element) | errorCode             | M         | String Fixed Length – 6                 | <p>Carries the compliance code indicating the reason for a failed</p><p>transaction – not required for a successful transaction</p> |
|                                        | errorDescription      | M         | String Min Length – 1, Max Length – 100 | <p>Description of the compliance code – not required for a</p><p>successful transaction</p>                                         |
|                                        | status                | M         | String Format: Successful/Failure       | Status of the bill fetch responseSuccessful/Failure                                                                                 |
|                                        | tenantId              | M         | String Fixed length - 4                 | OU ID of the BOU                                                                                                                    |

**Json Formatted Response Example**

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