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

BBPS Biller Integration

This document explains the APIs to be implemented by the billers to integrate with the BBPS system.

Billers need to integrate the following APIs and endpoints. The APIs are asynchronous, meaning once an API is triggered, BBPS BOU servers will expect an Acknowledgement from the server immediately, before receiving the Response after processing. The actual response will be sent from biller systems as a follow on HTTP request .

In this case, whenever the BBPS Protocol system sends a request to the Biller server, the Biller server needs to send the Acknowledgement. Once the request is processed at the biller server, the Biller server will send the Response back to the Protocol server aka Bank server.

API
Biller Server Endpoints
Purpose

BILL FETCH API

{Biller domain name}/fetch

To fetch the bill details from the biller

BILL PAY API

{Biller domain name}/payment

To initiate bill payment

BILL VALIDATE API

{Biller domain name}/validation

To validate the bill

STATUS 402

{Biller domain name}/TxnStatus402

To check the status of the transaction

PreviousGet all PlansNextBBPS API Workflow

Last updated 1 year ago

Was this helpful?

Page cover image