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 Agent Integration
  3. BBPS Agent API

Close Complaint

API for closing raised complaint.

Complaint can be closed only if the complaint status are the following COMPLAINT_OPEN_SUCCESS COMPLAINT_REOPEN_SUCCESS COMPLAINT_CLOSURE_REQUEST_FAILED COMPLAINT_CLOSURE_REQUEST_SUCCESS

Endpoint

Request: /couapp/complaints/closure

Request Parameters

The various parameters are explained below:

Parent Property/Element
Property/Element Name
Mandatory
Data Type
Description

[ROOT] (No parent property / element)

tenantId

M

Alphanumeric

Fixed Length – 4

complaintDescr

M

Alphanumeric

Description for closing complaint

complaintId

M

UUID

Complaint UUID

Response Parameters

The various parameters are explained below:

Parent Property/Element
Property/Element Name
Mandatory
Data Type
Description

complaints

complaintId

M

UUID

Id for the complaint disposion

complaintDescr

M

String

Complaint description

complaintDispos

M

String

Complaint disposition

complaintType

M

String

Type of the complaint

txnId

M

String

Transaction id for which the complaint is raised agains

complaintStatus

M

String

Complaint Status from NPCI

assignedTo

M

String

To Whom the complaint is assigned

complaintNpciId

M

String

Npci id of the complaint

complaintRaisedFrom

M

String

Who raised the complaint

userId

M

String

User id of the one who raised the complaint

status

M

String

Status of the complaint

refId

M

String

Reference id

estimated_TAT

M

String

creationDate

M

String

ISO 8601 Timestamp for the Complaint Creation date

modifiedDate

M

String

ISO 8601 Timestamp for the Complaint Modification date

billerName

M

String

Biller Name

txnAmount

M

String

Txn Amount

superLevelEsc

M

String

Super Escalation (True/False)

openComplaint

M

String

Flag indicating whether complaint is already open or not (Y/N)

reopenComplaint

M

String

Flag indicating whether complaint is already reopened or not (Y/N)

remarks

M

String

Remarks

agentId

M

String

Agent ID

category

M

String

Category of the biller

createdEpochDate

M

Numeric

UNIX Epoch Timestamp for the Complaint Creation date

modifiedEpochDate

M

Numeric

UNIX Epoch Timestamp for the Complaint Modification date

generalResp

statusCode

M

Numeric

200- SUCCESS Other than 200-Failure

status

M

String

It is either “Success” or failure

message

M

String

Contains the reason message for failure / success

Json Formatted Request Example

{
"complaintDescr" : "Closing complaint Issue resolved", "complaintId" : "809ec4c7-d81b-4d2b-9c66-3011a6fae714", "tenantId" : "FE41"
}

Json Formatted Response Example

{
"complaints": {
"complaintDescr": "Closing complaint Issue resolved",
"complaintDispos": "Transaction Successful, account not updated", 
"complaintId": "809ec4c7-d81b-4d2b-9c66-3011a6fae714", 
"complaintNpciId": "FE4123109776644",
"complaintRaisedFrom": "agent", 
"complaintType": "npciComplaint", 
"createdEpochDate": 1681893776, 
"creationDate": "2023-04-19T14:12:56.329935Z", 
"modifiedDate": "2023-04-19T14:13:32.25255Z",
"modifiedEpochDate": 1681893812,
"refId": "hHfEKYZExIpxNEV65HMQZ2Lh0DA31091413", 
"status": " COMPLAINT_CLOSURE_REQUEST_SUCCESS ",
"tenantId": "FE41",
"txnId": "155a4a71-141f-40fd-b772-9d0e020963e8", 
"txnNpciId": "FE413045Hl3L90ZWg59o",
"userId": "FE41FE42BNK519012345", 
"agentId": "FE41FE42BNK519012345"
},
"generalResp": {
"message": "Complaint closure requested", 
"remarks": "",
"status": "success", 
"statusCode": "200"
}
}
PreviousView Complaints History by idNextReopen Complaint

Last updated 1 year ago

Was this helpful?