From 7eac8de9563d4c2e7b45488104519885f7d9ae90 Mon Sep 17 00:00:00 2001 From: tanmay Date: Fri, 17 May 2024 11:11:04 +0530 Subject: [PATCH 1/5] Updates to List Billers API - add/update coverage related query params - add updatedSince query param - add bbpsUpdateTimestamp to billerDetails - add enforcesSameDayFetchPay to billerDetails --- .../billpay/api-integration/getBillers.json | 9 +++ .../payments/billpay/api-integration.json | 57 +++++++++++++++++-- 2 files changed, 61 insertions(+), 5 deletions(-) diff --git a/api-playground/json/payments/billpay/api-integration/getBillers.json b/api-playground/json/payments/billpay/api-integration/getBillers.json index 1b075945..2a18534c 100644 --- a/api-playground/json/payments/billpay/api-integration/getBillers.json +++ b/api-playground/json/payments/billpay/api-integration/getBillers.json @@ -19,6 +19,12 @@ { "pincode": "pincode" }, + { + "country": "country" + }, + { + "coverage": "coverage" + }, { "state": "state" }, @@ -33,6 +39,9 @@ }, { "paymentMode": "paymentMode" + }, + { + "updatedSince": "updatedSince" } ], "header": [ diff --git a/api-references/payments/billpay/api-integration.json b/api-references/payments/billpay/api-integration.json index 0bd5a011..b65d1b13 100644 --- a/api-references/payments/billpay/api-integration.json +++ b/api-references/payments/billpay/api-integration.json @@ -93,19 +93,41 @@ "type": "string" } }, + { + "name": "coverage", + "in": "query", + "schema": { + "type": "string" + }, + "example": "IND-TEL-Hyderabad", + "description": "Fetches billers in the provided coverage area" + }, + { + "name": "country", + "in": "query", + "schema": { + "type": "string" + }, + "example": "IND", + "description": "Fetches billers in the provided country" + }, { "name": "state", "in": "query", "schema": { "type": "string" - } + }, + "example": "TEL", + "description": "Fetches billers in the provided state" }, { "name": "city", "in": "query", "schema": { "type": "string" - } + }, + "example": "Hyderabad", + "description": "Fetches billers in the provided city" }, { "name": "tags", @@ -165,6 +187,16 @@ ] } } + }, + { + "name": "updatedSince", + "in": "query", + "schema": { + "type": "string", + "format": "date-time" + }, + "example": "2020-12-12T13:12:00+05:30", + "description": "Fetches billers updated on or after the provided timestamp" } ], "responses": { @@ -1756,18 +1788,28 @@ ], "type": "object", "properties": { + "bbpsUpdateTimestamp": { + "type": "string", + "format": "date-time", + "example": "2020-12-12T13:12:00+05:30", + "description": "The timestamp when the biller was last updated accurate to the nearest day" + }, "categoryName": { "type": "string", "example": "loan-repayment" }, "city": { "type": "string", - "example": "city" + "example": "Hyderabad" }, - "coverage": { + "country": { "type": "string", "example": "IND" }, + "coverage": { + "type": "string", + "example": "IND-TEL-Hyderabad" + }, "createdAt": { "type": "string", "format": "date-time", @@ -1787,6 +1829,11 @@ "$ref": "#/components/schemas/customerParamsGroupItem" } }, + "enforcesSameDayFetchPay": { + "type": "boolean", + "example": true, + "description": "Denotes whether the biller requires biller payment to be made on the same calendar day as the bill fetch." + }, "exactness": { "type": "string", "enum": [ @@ -1851,7 +1898,7 @@ }, "state": { "type": "string", - "example": "state" + "example": "TEL" }, "supportsPendingStatus": { "type": "boolean", From a9ab103355d89b0f87912f1fe7b12e899c88ad75 Mon Sep 17 00:00:00 2001 From: Sreejit7 Date: Fri, 17 May 2024 13:46:03 +0530 Subject: [PATCH 2/5] Update COU user events - add missing details, fix examples and formatting --- .../billpay/pre-built-screens/webhooks.mdx | 156 +++++++++++++----- 1 file changed, 111 insertions(+), 45 deletions(-) diff --git a/content/payments/billpay/pre-built-screens/webhooks.mdx b/content/payments/billpay/pre-built-screens/webhooks.mdx index d1e5754d..643c7901 100644 --- a/content/payments/billpay/pre-built-screens/webhooks.mdx +++ b/content/payments/billpay/pre-built-screens/webhooks.mdx @@ -86,6 +86,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t "billDate":"2024-03-01" // if available "dueDate": "2024-03-20", // if available "customerName": "Ram Charan", // if available + "customerId": "cust@1234" // if available "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", "event": "bill_fetch_success", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831", @@ -95,7 +96,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t "value": "ABC" } ] - }`} +}`} @@ -125,7 +126,18 @@ Below are the parameter tables and sample payloads for the listed events. Note t + + + + + + + + + + + + - + + + + + + + @@ -229,21 +259,22 @@ Below are the parameter tables and sample payloads for the listed events. Note t {`{ - "mobileNumber": "9481773053", - "status": "FETCH_FAILURE", - "billId": "", - "billerId": "MAHI00000NATIC", - "billerName": "Mahindra Rural Housing Finance Ltd", - "billerCategory": "Loan-Repayment", - "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", - "event": "bill_fetch_failure", - "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831", - "fetchErrorCode": "ERR001", - "error": { - "code": "ERR001", - "message": "Unable to get details" - } - }`} + "mobileNumber": "9481773053", + "status": "FETCH_FAILURE", + "billId": "", + "billerId": "MAHI00000NATIC", + "billerName": "Mahindra Rural Housing Finance Ltd", + "billerCategory": "Loan-Repayment", + "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", + "customerId": "cust@1234" // if available + "event": "bill_fetch_failure", + "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831", + "fetchErrorCode": "ERR001", + "error": { + "code": "ERR001", + "message": "Unable to get details" + } +}`}
String Unique identifier for the bill. It is generated by the - biller. Also called as billNumber. Not applicable where + biller. Not applicable where + there is no bill. + + 490a8940-886e-45ed-bfd1-21dbed064373 +
billNumberString + Unique identifier for the bill as sent by NPCI. Not applicable where there is no bill. @@ -172,11 +184,29 @@ Below are the parameter tables and sample payloads for the listed events. Note t 101.55
billDateString (Date)Date of bill generation. Format is YYYY-MM-DD. + 2023-05-02 +
dueDate String (Date) Due date of the bill. Format is YYYY-MM-DD. + 2023-05-20 +
customerIdStringUnique identifier for the customerId used for this session + cust@1234 +
sessionId
@@ -318,6 +349,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t 7f6de02a-0061-403f-bd65-47d4b5f72c87 + + + + + + @@ -388,14 +427,15 @@ Below are the parameter tables and sample payloads for the listed events. Note t "billerName": "Mahindra Rural Housing Finance Ltd", "billerCategory": "Loan-Repayment", "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", + "customerId": "cust@1234" // if available "billAmount": "105.0", - "dueDate": "2021-05-23", + "dueDate": "2021-05-23", // if available "amountPaid": "601.00", "orderId": "H001234566666", "event": "bill_payment_success", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831", "paidOn": "02-01-2006 15:04:05" - }`} +}`}
customerIdStringUnique identifier for the customerId used for this session + cust@1234 +
event String
@@ -481,6 +521,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t 7f6de02a-0061-403f-bd65-47d4b5f72c87 + + + + + + @@ -494,7 +542,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t @@ -506,7 +554,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t Fastag @@ -532,7 +580,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t @@ -567,13 +615,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t "billerName": "Mahindra Rural Housing Finance Ltd", "billerCategory": "Loan-Repayment", "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", + "customerId": "cust@1234" // if available "orderId": "Q00ABCDEFGHZOQ", "billAmount": "105.0", - "dueDate": "2021-05-23", + "dueDate": "2021-05-23", // if available "amountPaid": "601.00", "event": "bill_payment_failure", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831" - }`} +}`}
customerIdStringUnique identifier for the customerId used for this session + cust@1234 +
billAmount String (Number)String (Date) Due date of the bill. Format is YYYY-MM-DD. - 44339 + 2023-05-02
- 2022-01-03 + 601.75
String (DateTime) Time of transaction - 02-01-2006 15:04:05" + 02-01-2006 15:04:05
@@ -659,6 +708,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t 7f6de02a-0061-403f-bd65-47d4b5f72c87 + + + + + + @@ -682,7 +739,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t @@ -735,15 +792,15 @@ Below are the parameter tables and sample payloads for the listed events. Note t "billerId": "MAHI00000NATIC", "billerName": "Mahindra Rural Housing Finance Ltd", "billerCategory": "Loan-Repayment", - "customerId": "9CBV4C9MSURWXRM54Q3DY8WEE", "billAmount": "105.0", - "dueDate": "2021-05-23", + "dueDate": "2021-05-23", // if available "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", + "customerId": "cust@1234" // if available "amountPaid": 601.0, "amount": null, "event": "bill_collection_failure", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831" - }`} +}`}
customerIdStringUnique identifier for the customerId used for this session + cust@1234 +
orderId StringString (Date) Due date of the bill. Format is YYYY-MM-DD. - 44339 + 2023-05-02
@@ -822,14 +879,6 @@ Below are the parameter tables and sample payloads for the listed events. Note t Loan-Repayment - - - - - - @@ -843,7 +892,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t @@ -854,6 +903,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t 7f6de02a-0061-403f-bd65-47d4b5f72c87 + + + + + + @@ -916,13 +973,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t "billerName": "Mahindra Rural Housing Finance Ltd", "billerCategory": "Loan-Repayment", "sessionId": "7f6de02a-0061-403f-bd65-47d4b5f72c87", + "customerId": "cust@1234" // if available "billAmount": "105.0", - "dueDate": "2021-05-23", + "dueDate": "2021-05-23", // if available "orderId": "H001234566666", "amountPaid": "601.00", "event": "bill_payment_refunded", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831" - }`} +}`}
customerIdStringSetu's customer reference ID - 9CBV4C9MSURWXRM54Q3DY8WEE -
billAmount String (Number)String (Date) Due date of the bill. Format is YYYY-MM-DD. - 44339 + 2023-05-02
customerIdStringUnique identifier for the customerId used for this session + cust@1234 +
amountPaid String (Number)
@@ -1004,6 +1062,14 @@ Below are the parameter tables and sample payloads for the listed events. Note t 7f6de02a-0061-403f-bd65-47d4b5f72c87 + + + + + + @@ -1017,7 +1083,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t @@ -1082,7 +1148,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t "status": "submitted", "event": "dispute_raised", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831" - }`} +}`}
customerIdStringUnique identifier for the customerId used for this session + cust@1234 +
billAmount String (Number)String (Date) Due date of the bill. Format is YYYY-MM-DD. - 44339 + 2023-05-02
@@ -1107,7 +1173,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t @@ -1193,7 +1259,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t "status": "closed/unknown", "event": "dispute_status_change", "refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831" - }`} +}`}
String (Date) Date of the transaction. Format is YYYY-MM-DD. - 44371 + 2021-06-24
@@ -1218,7 +1284,7 @@ Below are the parameter tables and sample payloads for the listed events. Note t From 3d5fdd7b3f2c294f1ab9c8a074b69dc43edd1a7b Mon Sep 17 00:00:00 2001 From: Sreejit7 Date: Fri, 17 May 2024 14:14:58 +0530 Subject: [PATCH 3/5] Add allowedPaymentModes to response and handlers --- .../custom-payment/android.mdx | 14 +++++++++++--- .../custom-payment/cross-platform.mdx | 5 ++++- .../pre-built-screens/custom-payment/iOS.mdx | 18 +++++++++++++++--- .../custom-payment/website.mdx | 4 ++-- 4 files changed, 32 insertions(+), 9 deletions(-) diff --git a/content/payments/billpay/pre-built-screens/custom-payment/android.mdx b/content/payments/billpay/pre-built-screens/custom-payment/android.mdx index ab8eb982..0992d18c 100644 --- a/content/payments/billpay/pre-built-screens/custom-payment/android.mdx +++ b/content/payments/billpay/pre-built-screens/custom-payment/android.mdx @@ -148,13 +148,17 @@ Here is a sample of the Java Interface class needed by the webview— } /** Show a toast from the web page */ @JavascriptInterface - public void initiatePayment(String orderId, String beneVpa, String amount, String callback, String remarks) { + public void initiatePayment(String orderId, String beneVpa, String amount, String callback, String remarks, String mobileNumber, String refId, String customerId, String allowedPaymentModes) { Intent intent = new Intent(mContext, PaymentScreen.class); intent.putExtra("BENE_VPA", beneVpa); intent.putExtra("ORDER_ID", orderId); intent.putExtra("AMOUNT", amount); intent.putExtra("CALLBACK_URL", success_url); intent.putExtra("REMARKS", remarks); + intent.putExtra("MOBILE_NUMBER", remarks); + intent.putExtra("REF_ID", refId); + intent.putExtra("CUSTOMER_ID", customerId); + intent.putExtra("ALLOWED_PAYMENT_MODES", allowedPaymentModes) mContext.startActivity(intent); } /** Show a toast from the web page */ @@ -181,11 +185,15 @@ The interface will contain 2 methods— `initiatePayment` on the Android interface takes the following parameters -- `orderId` on the Setu COU System. Example— `Z7pFtTgr9LtO` +- `orderId` on the Setu COU System. Example— `COUWLZ7pFtTgr9LtO` - `amount` to be paid by the customer: Example— `3522.20` -- `callback` which needs to be loaded if the payment is completed. Example—`//billpay.setu.co/cou/payment-callback/68c7217b-8fa7-4c1f-8e5f-317ff3027668` +- `callback` which needs to be loaded if the payment is completed. Example—`https://billpay.setu.co/cou/payment-callback/68c7217b-8fa7-4c1f-8e5f-317ff3027668` - `beneVpa` to which amount is to be transferred—this is relevant only if you can transfer in real time using UPI rails. - `remarks` used to communicate information between mobile app and webview +- `mobileNumber` mobile number used for the session. Example - `9876543210` +- `refId` BBPS reference ID linked to a particular bill (only available for fetch billers). Example - `CMA0I65RCU2I32C3L0H0KNYQYAG40021831` +- `customerId` linked to a particular session. Example - `cust@1234` +- `allowedPaymentModes` comma separated list of modes allowed for this payment. One of these should be sent in the `paymentMode` in the payment confirmation webhook. When `initiatePayment` is called by the webview, your app needs to do the following— diff --git a/content/payments/billpay/pre-built-screens/custom-payment/cross-platform.mdx b/content/payments/billpay/pre-built-screens/custom-payment/cross-platform.mdx index b6fd89ae..dd98078b 100644 --- a/content/payments/billpay/pre-built-screens/custom-payment/cross-platform.mdx +++ b/content/payments/billpay/pre-built-screens/custom-payment/cross-platform.mdx @@ -175,7 +175,10 @@ The `initiatePayment` method in the `controller` takes an object param with the - `callback` URL which needs to be loaded in the webview once the payment is completed. Example —`https://billpay.setu.co/payment-callback/68c7217b-8fa7-4c1f-8e5f-317ff3027668` - `beneVpa` to which amount is to be transferred—this is relevant only if you can transfer in real time using UPI rails. - `remarks` used to communicate information between mobile app and webview -- `mobileNumber` the customer mobile number used for the payment +- `mobileNumber` mobile number used for the session. Example - `9876543210` +- `refId` BBPS reference ID linked to a particular bill (only available for fetch billers). Example - `CMA0I65RCU2I32C3L0H0KNYQYAG40021831` +- `customerId` linked to a particular session. Example - `cust@1234` +- `allowedPaymentModes` comma separated list of modes allowed for this payment. One of these should be sent in the `paymentMode` in the payment confirmation webhook. When initiate_payment case is called by the webview, your app needs to do the following— diff --git a/content/payments/billpay/pre-built-screens/custom-payment/iOS.mdx b/content/payments/billpay/pre-built-screens/custom-payment/iOS.mdx index 07fee847..c1eb8a0d 100644 --- a/content/payments/billpay/pre-built-screens/custom-payment/iOS.mdx +++ b/content/payments/billpay/pre-built-screens/custom-payment/iOS.mdx @@ -105,13 +105,21 @@ func userContentController(_ userContentController: WKUserContentController, did let billAmount = dict["data"]?["amount"] as! String let orderID = dict["data"]?["orderId"] as! String let beneficiaryVPA = dict["data"]?["beneficiaryVPA"] as! String + let mobileNumber = dict["data"]?["mobileNumber"] as! String + let refId = dict["data"]?["refId"] as! String + let customerId = dict["data"]?["customerId"] as! String + let allowedPaymentModes = dict["data"]?["allowedPaymentModes"] as! String let vc = PaymentViewController( successLink: successLink + successParams, remarks: remarks, billAmount: billAmount, orderID: orderID, - beneficiaryVPA: beneficiaryVPA + beneficiaryVPA: beneficiaryVPA, + mobileNumber: mobileNumber, + refId: refId, + customerId: customerId, + allowedPaymentModes: allowedPaymentModes ) let navVC = UINavigationController(rootViewController: vc) @@ -160,9 +168,13 @@ The `initiate_payment` case in the the `userContentController` takes the followi - `amount` to be paid by the customer. Example — `3522.20` - `callback` URL which needs to be loaded in the webview once the payment is completed. Example — `https://billpay.setu.co/payment-callback/68c7217b-8fa7-4c1f-8e5f-317ff3027668` - `beneficiaryVPA` to which amount is to be transferred—this is relevant only if you can transfer in real time using UPI rails. -- `remarks` used to communicate information between mobile app and webview +- `remarks` used to communicate information between mobile app and webview. +- `mobileNumber` mobile number used for the session. Example - `9876543210` +- `refId` BBPS reference ID linked to a particular bill (only available for fetch billers). Example - `CMA0I65RCU2I32C3L0H0KNYQYAG40021831` +- `customerId` linked to a particular session. Example - `cust@1234` +- `allowedPaymentModes` comma separated list of modes allowed for this payment. One of these should be sent in the `paymentMode` in the payment confirmation webhook. -When `initiate_payment` case is called by the `webview`, your app needs to do the following— +When `initiate_payment` case is called by the `webview`, your app needs to do the following- 1. Remove the webview 2. Initiate the payment flow diff --git a/content/payments/billpay/pre-built-screens/custom-payment/website.mdx b/content/payments/billpay/pre-built-screens/custom-payment/website.mdx index cb278e09..c2b76d5f 100644 --- a/content/payments/billpay/pre-built-screens/custom-payment/website.mdx +++ b/content/payments/billpay/pre-built-screens/custom-payment/website.mdx @@ -61,8 +61,8 @@ Note that the API key is issued by you "amount": 1201.00, "customerMobileNumber": "9481773053", "postPaymentUrl": "https://billpay.setu.co/payment/post-payment/c4e154e6-7b2b-4e0a-9749-60499b61ce93", - "allowedPaymentMethods": [ - "CASH", "UPI" + "allowedPaymentModes": [ + "CASH", "UPI", "CREDIT CARD" // list of allowed values for "paymentMode" in webhooks ] }`} From de4e0d2708d299af64156b55abc8095d11aa09b9 Mon Sep 17 00:00:00 2001 From: Sreejit7 Date: Fri, 17 May 2024 14:21:20 +0530 Subject: [PATCH 4/5] remove broken custom payment webhook API reference --- content/payments/billpay/pre-built-screens/custom-payment.mdx | 2 +- .../payments/billpay/pre-built-screens/custom-payment/apis.mdx | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/content/payments/billpay/pre-built-screens/custom-payment.mdx b/content/payments/billpay/pre-built-screens/custom-payment.mdx index dad280de..50a50a12 100644 --- a/content/payments/billpay/pre-built-screens/custom-payment.mdx +++ b/content/payments/billpay/pre-built-screens/custom-payment.mdx @@ -44,7 +44,7 @@ You need to call the following APIs— Create one time link 2. Confirm payment diff --git a/content/payments/billpay/pre-built-screens/custom-payment/apis.mdx b/content/payments/billpay/pre-built-screens/custom-payment/apis.mdx index c2f57de2..981c177d 100644 --- a/content/payments/billpay/pre-built-screens/custom-payment/apis.mdx +++ b/content/payments/billpay/pre-built-screens/custom-payment/apis.mdx @@ -48,8 +48,6 @@ The `orderId` is always prefixed with `COUWL` to identify Setu payment requests. }`} -See API reference for more information. -
### APIs you need to support From c41f2d9da5645822bbe9669c42557e4062c78c92 Mon Sep 17 00:00:00 2001 From: tanmay Date: Fri, 17 May 2024 14:46:48 +0530 Subject: [PATCH 5/5] Update list biller objects --- .../billpay/api-integration/objects.mdx | 53 ++++++++++--------- 1 file changed, 29 insertions(+), 24 deletions(-) diff --git a/content/payments/billpay/api-integration/objects.mdx b/content/payments/billpay/api-integration/objects.mdx index 39477d1e..98e600b8 100644 --- a/content/payments/billpay/api-integration/objects.mdx +++ b/content/payments/billpay/api-integration/objects.mdx @@ -347,36 +347,41 @@ Maxium amount accepted by the biller for the [Payment Channel](#payment-channel) | after | `string` | Billers are sorted via the Biller ID. Providing a biller Id fetches billers right after this biller in a paginated way. | | search | `string` | searches the provided text over biller name and biller alias | | pincode | `string` | | -| state | `string` | | -| city | `string` | | +| coverage | `string` | BBPS coverage. Used to search billers having a specific coverage area | +| country | `string` | BBPS Country Code. Used to search billers operating in a certain country | +| state | `string` | BBPS state code. Used to search billers operating in a certain state | +| city | `string` | city name, used to search billers operating in a certain city | +| updatedSince | `date-time` | Fetch billers updated on or after the provided timestamp | | tags | `string` | | | paymentChannel | [Payment Channel](#payment-channel)`[]` | | | paymentMode | [Payment Mode](#payment-mode)`[]` | | ### Response -| parameter | type | description | -| ---------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| categoryName | `string` | Biller Category | -| city | `string` | Biller City | -| coverage | `string` | Biller coverage | -| createdAt | `date-time` | Biller Created At | -| customerParams | [Biller Customer Params](#biller-customer-params)`[]` | Customer Parameter format descrption | -| exactness | [Exactness](#exactness) | Biller Exactness | -| fetchApiType | [Fetch API Type](#fetch-api-type) | Biller Fetch API Type | -| id | `string` | Biller ID | -| logo | `string` | Biller logo | -| modifiedAt | `date-time` | Biller Created At | -| name | `string` | Biller Name | -| payWithoutFetchAllowed | `bool` | Whether biller allows bill payment without a fetch or not. Even in case of `BILL_FETCH` API type, certain bills make the fetch optional | -| paymentChannels | [Biller Payment Channel](#bill-payment-channel)`[]` | Payment Channel limits set by the biller. | -| paymentModes | [Payment Limit](#payment-limit)`[]` | Payment mode limits set by the biller. | -| pincode | `string` | Biller Pincode | -| supportsPendingStatus | `bool` | Whether the biller supports pending status. In this case, a payment can be in progress for up to 2 days. | -| tags | `string` | Additional Tags of the biller. | -| state | `string` | Biller State | -| plans | [Biller-Plan-Information](#biller-plan-information)`[]` | Plans provided by the biller. | - +| parameter | type | description | +| ----------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| categoryName | `string` | Biller Category | +| city | `string` | Biller City | +| country | `string` | Biller Country | +| coverage | `string` | Biller coverage | +| createdAt | `date-time` | Biller Created At | +| customerParams | [Biller Customer Params](#biller-customer-params)`[]` | Customer Parameter format descrption | +| exactness | [Exactness](#exactness) | Biller Exactness | +| fetchApiType | [Fetch API Type](#fetch-api-type) | Biller Fetch API Type | +| id | `string` | Biller ID | +| logo | `string` | Biller logo | +| modifiedAt | `date-time` | Biller Modified At | +| name | `string` | Biller Name | +| payWithoutFetchAllowed | `bool` | Whether biller allows bill payment without a fetch or not. Even in case of `BILL_FETCH` API type, certain bills make the fetch optional | +| paymentChannels | [Biller Payment Channel](#bill-payment-channel)`[]` | Payment Channel limits set by the biller. | +| paymentModes | [Payment Limit](#payment-limit)`[]` | Payment mode limits set by the biller. | +| pincode | `string` | Biller Pincode | +| supportsPendingStatus | `bool` | Whether the biller supports pending status. In this case, a payment can be in progress for up to 2 days. | +| tags | `string` | Additional Tags of the biller. | +| state | `string` | Biller State | +| plans | [Biller-Plan-Information](#biller-plan-information)`[]` | Plans provided by the biller. | +| enforcesSameDayFetchPay | `bool` | Whether the biller requires bill payment to be on the same calendar day as bill fetch. | +| bbpsUpdateTimestamp | `date-time` | Last updated date-time of the Biller accurate to the nearest day. |
## Dispute Request
String (Date) Date of the transaction. Format is YYYY-MM-DD. - 44371 + 2023-05-02