BBPS
  • BBPS
    • BBPS Agent Integration
      • Broad examples of bill payments
      • How a bill is presented
      • FETCH AND PAY
        • Bill fetch api
        • Bill Fetch by bill id api
        • Bill Fetch by client request id api
      • VALIDATE AND PAY
        • Bill validate api
        • Bill Validation response by client request id api
        • Bill validation response by bill id api
      • QUICK PAY
      • COMPLAINT RAISING
      • AGENT APPLICATION
      • BBPS Master Data API
        • List Billers API
        • Billers By ID API
        • Categories Master Data API
        • Contact Master Data API
        • Customer Parameters API
        • Customer Parameters API
        • Customer Parameters Groups API
        • Disposition API
        • Initiating Channel API
      • BBPS Agent API
        • Bill Fetch by bill id
        • Bill Fetch by Client Request ID API
        • Get all Plan categories
        • Get all Plans
        • Bill Validate API
        • Bill Validation response by Client Request ID API
        • Bill validation response by bill id
        • Bill Payment API
        • Transaction Status txnId API
        • Transaction Status ClientReqId API
        • Adding complaint by txnId
        • View Complaints by id
        • View All Complaints
        • Txn Status Check API (401)
        • View Complaints History by id
        • Close Complaint
        • Reopen Complaint
        • Complaint Status
      • Get all Plan categories
      • Get all Plans
    • BBPS Biller Integration
      • BBPS API Workflow
      • BBPS API List
        • BILL FETCH API
        • Bill Fetch Response Endpoint
        • BILL PAY API
          • BillPayment Response Endpoint
          • Payment Notification API
          • Payment Status API
        • BILL VALIDATE API
          • BillValidation Response Endpoint
        • STATUS 402 API
          • TxnStatusResponse Endpoint
      • Bill Fetch by bill id
Powered by GitBook
On this page

Was this helpful?

  1. BBPS
  2. BBPS Biller Integration
  3. BBPS API List

Bill Fetch Response Endpoint

Biller server to Biller Protocol

Endpoint

Request: POST /BillFetchResponse

Response Parameters

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

errorCode

M

String Fixed Length – 6

Carries the compliance code indicating the reason for a failed

transaction – not required for a successful transaction

errorDescription

M

String Min Length – 1, Max Length – 100

Description of the compliance code – not required for a

successful transaction

status

M

String Format: Successful / Failure

Status of the bill fetch response Successful/Failure

billNumber

M

String Min Length – 1, Max Length – 100

Unique Id of the Bill

customerName

M

String Min Length – 1, Max Length – 100

Name of the Customer

amount

M

String Min Length – 1, Max Length – 18

Total amount of the bill

billPeriod

M

String Min Length – 1, Max Length – 50

Bill Period set by the biller

billDate

M

String Fixed Length – 10

Bill Date set by the biller

dueDate

M

String Fixed Length – 10

DueDate Set by the biller

billerResponseTags

M

Array of name value pairs

Biller response related tag indicating the various amount options

provided by the Biller

name

M

String Min Length – 1, Max Length – 100

Name of the amount field assigned by the Biller

value

M

String Min Length – 1, Max Length – 100

Value of the amount field

additionalInfo

M

Array of name value pairs Min Length – 1, Max Length – 100

Additional information parameters sent by the Biller supporting

fetch is copied in the payment request "as-is" – not applicable for

payment only Billers

Value

M

String Min Length – 1, Max Length – 100

Value of the field

tenantId

M

String Fixed length - 4

OU ID of the BOU

Json Formatted Response Example



    {
    "refId": "String", "errorCode": "String", "errorDescription": "String", "status": "String", "billNumber": "String", "customerName": "String", "amount": "String", "billPeriod": "String", "billDate": "String", "dueDate": "String", "billerResponseTags": [
    {
    "name": "String",
    "value": "String"
    }
    ],
    "additionalInfo": [
    {
    "name": "String",
    "value": "String"
    }
    ],
    "tenantId" : "String"
    }

Json Formatted Acknowledgement Example


{
"reason":"String",
"code":"Integer", "status
}
PreviousBILL FETCH APINextBILL PAY API

Last updated 1 year ago

Was this helpful?