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
  4. BILL PAY API

BillPayment Response Endpoint

Biller server to Biller Protocol

Request Parameters

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

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 responseSuccessful/Failure

tenantId

M

String Fixed length - 4

OU ID of the BOU

Json Formatted Response Example

    {
    "reason":"String",
    "code":"Integer", "status":"String"
    }
PreviousBILL PAY APINextPayment Notification API

Last updated 1 year ago

Was this helpful?