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

STATUS 402 API

PreviousBillValidation Response EndpointNextTxnStatusResponse Endpoint

Last updated 1 year ago

Was this helpful?

  • 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

Request 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

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

Expected Acknowledgement Parameters

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

Json Formatted Request Example

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

Json Formatted Response Example

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