#BBPS BillPay

#What is BBPS?

BBPS, or Bharat Bill Payment System, offers online and offline payments to over 20k businesses, including utilities, loan EMIs, and school fees.

#Who is an agent?

An agent is a registered BBPS entity allowed to collect payments for BBPS billers across all categories.x

You may register as an agent on BBPS, to collect BBPS bill payments with (Website Name) APIs on your supported collection channels (offline or online).

#What can I do with this product?

Our (Website Name) BillPay service lets your customers pay their bills on your app or website - from choosing companies to pay, to retrieving and paying bills. You can even collect payments directly from your business if you are a BBPS biller.

(Website Name) BBPS BillPay connects to NPCI through simple RESTful APIs, some of which are asynchronous. The API can be consumed only or you can subscribe to the webhook notifications (Website Name) provides.

You may integrate with (Website Name) in any of the following ways—

• (Website Name) API integration -—Register as an agent institution and use the (Website Name) APIs. Use your own payment gateway and build your own screens.
• Integration with a website—one-line integration with pre-built screens. Inbuilt UPI payment option.
• App integration—Integrate with pre-built screens, as web views in your app. Support for Android and iOS. Inbuilt UPI payment option.

#API integration

With (Website Name) BillPay, you can easily become an agent on the BBPS network and incorporate BBPS bill payments into your app or website. All necessary approvals are handled by (Website Name) in collaboration with our bank partner and BBPS.

This guide will walk you through the API integration process, help you create user-friendly screen flows, and get you ready to accept BBPS payments seamlessly on your platform.

#How to integrate

Grab your API keys first. Share the nitty-gritty with us to set up your agent. Dive into the API integration process. If you need a hand, hit us up at (Website Name) Support. Here's the breakdown:

A summary of the integration process—

1. Get your API keys
2. Provide details to set up agent
3. Start API integration
4. Share screens for NPCI approval
5. Run and submit test cases
6. Get production credentials and go live

Congratulations, you're live! Any issues? We've got your back at (Website Name) Support.

#Step 1 — Get your API keys

X-PARTNER-ID must be used in the auth header, and clientID and secret must be used for the bearer token. Contact the (Website Name) team at [Insert Contact Details] to learn more about these values .

Once you have the credentials, get the token by making a POST request to https://sandbox-kabini-coudc.(Website Name).co/api/v1/auth/token.

{
"clientID":"james-bond",
"secret":"5ja0077m-55e0-47s9-9bo7-ndaa18a7c0f7"
}

You then get a token which can be used to make Authenticated requests to BillPay APIs.

{
"expiresIn":600,
"token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImxEUXBadm5xRmtTdlRaMDV6NFdjTjl0My0zY0JSVWo5di1rYnVNX2dpQkEifQ.eyJleHAiOjE2NTgzMTUwMDcsImlhdCI6MTY1ODMxMjAwNywianRpIjoiMjQzMTAwN2MtODAwNy00MDA3LWI5ZWUtZTQ4MmY2YTU3ZGViIiwiaXNzIjoiaHR0cHM6Ly9hdXRoLWRldi5zZXR1LmNvL2F1dGgvcmVhbG1zL2NvdS1kYy1qYW1lcy1ib25kLXVhdCIsImF1ZCI6WyJqYW1lcy1ib25kIiwiYWNjb3VudCJdLCJzdWIiOiI0ZDhkMDY1Mi1kMmY2LTQyMWYtODNkMi0xYWUxYjc5ZTI1ZGIiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJqYW1lcy1ib25kIiwic2Vzc2lvbl9zdGF0ZSI6ImExOThkMDA3LWViOWQtNDAwNy05NGRjLTNlMjJmYTEzYTAwNyIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9qYW1lcy1ib25kLWNvdWRjLnNldHUuY28iXSwicmVhbG1fYWNjZXNzIjp7InJvbGVzIjpbIlNlY3JldF9JbnRlbGxpZ2VuY2VfU2VydmljZSJdfSwicmVzb3VyY2VfYWNjZXNzIjp7ImphbWVzLWJvbmQiOnsicm9sZXMiOlsiU2VjcmV0X0ludGVsbGlnZW5jZV9TZXJ2aWNlIl19LCJhY2NvdW50Ijp7InJvbGVzIjpbImNvdW50ZXItdGVycm9yaXNtIiwiY291bnRlci1wcm9saWZlcmF0aW9uIl19fSwic2NvcGUiOiJiYnBzOmJvbmQiLCJjbGllbnRJZCI6ImphbWVzLWJvbmQiLCJjbGllbnRIb3N0IjoiMDA3LjAwNy4wMDcuMDA3IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJzZXJ2aWNlLWFjY291bnQtamFtZXMtYm9uZCIsImNsaWVudEFkZHJlc3MiOiIwMDcuMDA3LjAwNy4wMDcifQ.svjuDXhx71uur_XYDCYLlObPBWctPHCDn1DtAAS-xMvnAvPdgqqVIUbGXdBxePE-blJPUDWH9J4ZXj5-kvi3onGdnmQxZcckW7dmIRrfTtUMCBj_4iefqiDV1D58Fblf9hCGjVGVWL9fuatNFvV46IaVREfaUTKuSbqwzhMpSGICJWhOM1Jt1Z2pB0x3e55dgmqhjeThZrstOwsJ2GTQ5N9gFennpmqmK_HVXU-rFwJzD44EMsN5GeH6Hh8zSC35NYkagrrlOkiuPGukoOMC9xFeGKGMSML3ve8_NmPVdhM6BaOwsau4wEJ-VV4oRY7TEl7d-IXmZqCVE0vyV2GZjQ",
"success":true,
"traceId":"C3SFG0O6N88R6UI7EQ"
}

#Step 2 — Set up your BBPS agent

An agent on BBPS is an entity that allows its customers to pay any BBPS-listed business. In order to fetch bills for customers from BBPS-listed businesses, you need to register on BBPS and receive an agent ID.

Share business details

Contact [Insert Contact Detail] for a list of the business details you need to provide to create your BBPS agent ID(s).

Share callback URL

Setting up a callback URL is recommended for receiving notifications for various types of events

• APIs to fetch bill for a customer
• APIs to validate customer identifier with a biller
• APIs to for completing a bill payment
• APIs to raise disputes against a payment
• APIs to receive an automatic bill due notification

When this is enabled by you, any successful fetch, validate, payment, dispute or autofetch event gets posted to your callback URL.

You may specify only one callback URL. This should be a valid URI string that starts with either https:// or http:// scheme.. For e.g., https://my-billpay-callback.com.

Website Name will append the following default paths to this callback URL, to alert your on specific events—

Other events are not related to the core BillPay APIs, but are updates about BBPS businesses.

A business may be delisted from BBPS or update the type of identifier they accept to retrieve a customer's bill. Such events can be useful if you maintain a database of BBPS businesses. The full list of events can be found here.

#Step 3 — Start API integration

You can begin testing different scenarios for fetching/paying bills or raising disputes and managing their resolution once you receive your APIs keys and agent ID for testing.

#Step 4 — Share screens for NPCI approval

As part of your application development process, it is imperative to ensure that the screens align with the BBPS guidelines. To seek approval from NPCI, you are required to submit a comprehensive document featuring screenshots of the following key screens:

• Category list screen, Displaying all BBPS categories.
• Biller list screen, Enlisting all billers under a selected category.
• Customer Input Screen, Where a customer inputs biller-specific identifiers before retrieving their bill.
• Payment confirmation screen, Where the customer verifies the bill amount and proceeds with the payment.
• Payment status screen, Reflecting the processing status of the payment, indicating whether it was successful or failed.
• Confirmation SMS, The text message sent to customers after a payment, specifying its success or failure.
• Bill receipt screen, Allowing customers to view and download receipts for successful transactions.
• Raise complaint screen, Enabling customers to raise complaints, with specific transaction IDs associated.
• Complaint status screen, Where customers can track the latest status of their registered complaints.

Throughout this submission, it is crucial to adhere to the BBPS guidelines and incorporate the provided logo and branding elements. The following points summarize the essential aspects to consider:

• The application or website UI must feature a "Pay Bills" button prominently displaying the BBPS logo.
• The BBPS logo should consistently appear in the top right corner of all screens utilized by customers during biller or bill searches, as well as on screens related to payment processes.
• The BBPS Assured logo is mandatory on pages confirming payment success and providing payment receipts. However, the regular BBPS logo can be omitted from these specific pages.

#Step 5 — Execute and Document Test Cases

Follow the outlined test cases in this document and provide detailed documentation of the results using a copy of the specified file.

#Step 6 — Obtain Production Credentials and Launch

Upon successful completion of all required approvals and agreements, you will be issued production credentials. Once you receive these credentials, it is essential to verify the integration thoroughly. Subsequently, you are authorized to proceed with the deployment and officially launch your application or website.

#Quickstart—API integration

Here is a concise overview of the APIs essential for initiating integration with the BBPS COU product for testing purposes.

As a representative of the BBPS system, your primary responsibilities involve facilitating customers in retrieving bills from any business listed on BBPS and enabling them to make payments to these businesses.

To achieve this, the fundamental fetch, pay and dispute APIs are asynchronous. Each API has a request endpoint and a response endpoint. The request endpoint registers the call and the response endpoint is used to retrieve the status of the registered call.

#Fetch bill

The utilization of the Fetch bill API with endpoint /bbps/bills/fetch/request is imperative for obtaining detailed bill information on behalf of a customer. It necessitates the submission of both the customer's particulars and the specific business from which they intend to retrieve their bill.

For instance, when facilitating the payment of a Vodafone Postpaid phone bill for a customer, it is essential to provide:

• The customer's identifier, which, in this case, is the mobile number.

• The business's identifier, denoted by the BBPS ID assigned to Vodafone in this context

{
"customer":{
"mobile":"9505987798",
"billParameters":[
{
"name":"Parameter 1",
"value":"Value 1"
},
{
"name":"Parameter 2",
"value":"Value 2"
},
{
"name":"Parameter 3",
"value":"Value 3"
}
]
},
"agent":{
"app":"SmartPay",
"channel":"INT",
"geocode":"19.0139,72.8254",
"id":"AX01AI06512391457204",
"ifsc":"ICIC0000152",
"imei":"123456789012345",
"ip":"124.170.23.24",
"mac":"48-4D-7E-CB-DB-6F",
"mobile":"9481773011",
"os":"iOS",
"postalCode":"600001",
"terminalId":"6000011234"
},
"biller":{
"id":"VODA00000MUM03"
}
}

You get a refId in the response, a unique identifier that can be further used to check the status of the bill fetch.

{
"data":{
"refId":"LNMSQQR4RKT7X1UGPY7JGUV454PL9T2C689",
},
"success":true,
"error":null
}

You may also use the /bbps/bills/fetch/response endpoint with above refId to check status of the bill fetch—

{
"refId":"LNMSQQR4RKT7X1UGPY7JGUV454PL9T2C689"
}

In the response you either get the bill details, or “Processing” status if the bill fetch is still in progress.

{
"data":{
"additionalInfo":[
{
"name":"Distributor Contact",
"value":"Cockatoojelly"
},
{
"name":"Distributor Name",
"value":"Frightstripe"
},
{
"name":"Consumer Number",
"value":"105"
},
{
"name":"Consumer Address",
"value":"Samuraipsychadelic"
}
],
"bill":{// optional - not present if biller does not support it
"amount":301500,
"billDate":"2021-09-13",
"billNumber":"8394852342371080869",
"billPeriod":"Monthly",
"customerName":"William Miller",
"dueDate":"2021-09-26"
},
"billerRefId":"4047076513",
"exactness":"ANY",
"paymentLimits":[
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"Internet Banking",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"Debit Card",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"Credit Card",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"Prepaid Card",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"IMPS",
"supportsPendingStatus":false
},
{
"maxLimit":4999900,
"minLimit":100,
"paymentMode":"Cash",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"UPI",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"Wallet",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"NEFT",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"AEPS",
"supportsPendingStatus":false
},
{
"maxLimit":20000000,
"minLimit":100,
"paymentMode":"Account Transfer",
"supportsPendingStatus":false
}
],
"refId":"C51JQ9ED608P36RN28GGM9L63RN12591837",
"status":"Success"
},
"success":true,
"traceId":"C51JQCUD608P36RN28H0"
}

Auto-fetch bills

Alternatively, you have the option to activate automatic bill fetches for customer bills. By supplying the customer identifier and the BBPS identifier for the relevant business, (Website Name) obtains the necessary information to automatically retrieve bill details for each subsequent payment cycle. Upon successful automatic bill retrieval, the response is directed to the specified callback URL.

To initiate auto-fetch for a bill, you can activate the autoFetch field to true, when making a Fetch Bill API request to /bbps/bills/fetch/request. The system will recognize and adhere to this flag value once the bill fetch operation is successfully executed.

{
+   "autoFetch": true,
   "customer": { ... },
   "agent": { ... },
   "biller": { ... }
}

The response structure remains unchanged, accompanied by an additional field known as autoFetchHash. This hash serves as a unique identifier for the bill fetch and can be utilized to ascertain the last auto-fetched date, verify the ongoing status of auto-fetch, or disable auto-fetch for the bill in theManage auto-fetch for bills section.

{
+   "autofetchHash": "d28ca210e0267a13fa0db18ee96a349dc4578f032e5902192af762763224204a",
   "data": { ... },
   "success": true,
   "traceId": "C51JQCUD608P36RN28H0"
}

When you set autoFetch flag to true, the response for Fetch bill will contain a autofetchHash. You can use this to—

• Hit the /list endpoint to check if the bill autofetch is active, along with last date for bill fetch
• Disable auto fetch by hitting the /delete endpoint
  

Specify auto-fetch for multiple bills——A POST request to /bbps/autofetches lets you register multiple bills to be fetched automatically, at their respective payment cycles.

List auto-fetch details for multiple bills—A GET request to /bbps/autofetches returns list of bills registered for autofetch. Each entry has

• lastFetchDate which is the date of the last bill fetch
• isActive which specifies if bill has auto fetch enabled

Disable auto-fetch—A DELETE request to /bbps/autofetches/{autofetchHash} disable auto fetch for a bill on your app/website

#Pay bill

The Pay bill API serves the purpose of transmitting payment details executed by a user on your application or website to (Website Name). This information is utilized by (Website Name) to validate the payment with the respective biller.

#Raise dispute

The Raise Dispute API is employed to formally raise a complaint for a payment conducted by a user on your application or website. (Website Name) processes this information and initiates a complaint on the BBPS Platform.

#List data in bulk

To keep your systems updated with the latest data, (Website Name) also provides actions to list data in bulk. The following APIs are available—

• List categories—lists all categories on BBPS.
• List billers—lists all billers on BBPS.
• List disputes—lists all the raised disputes using the Dispute API. Dispute API.
• List fetched Bills—lists all the fetched bills that were fetched using Fetch API. Fetch API.
• List paid bills—lists all the bill pay transactions paid using Pay API.Pay API.

#Check server health

The health check API tells you the health of the (Website Name) BillPay server.

Aside from the above, there are other APIs which are also vital for a complete customer payment experience. See the full API reference for more details.

#Payment Channel

This is the initiating payment channel.

#Payment Mode

Payment modes supported by a biller.

#Customer

Customer object holds the customer mobile number and the customer bill parameters.

#Biller

Biller object holds the biller ID.

#Agent

Details pertaining to the Agent which initiates the transaction. Values of the field if provided to NPCI has to be matched against it.

#Initiating Channel & Required Agent parameters

#Initiating Channel & Eligible Payment modes

#Failure Reason

#Payment Details

#Bill Status

#Transaction Status

#Dispute Status

#Bill Period

#Bill Data

#Exactness

Amount acceptance by the biller.

#Refund Status

#Payment Limit

#Dispute Type

#Biller Customer Params

#Fetch API Type

#Biller Payment Channel

Maxium amount accepted by the biller for the Payment Channel.

#Biller Plan Information

#Transaction

/transactions

#Query Parameters

#Response

#Dispute

/disputes

#Query Parameters

#Response

#Biller MDM

/billers

#Query Parameters

#Response

#Dispute Request

/bills/dispute/request

#Request Body

#Dispute Response

/bills/dispute/response

#Response Body

#Fetch Request

/bills/fetch/request

#Request Body

#Fetch Response

/bills/fetch/response

#Response Body

#Payment Request

/bills/payment/request

#Request Body

#Payment Response

/bills/payment/response

#Response Body

#Webhooks

Here is the general structure of any webhook—

"traceId":"C3SFG0O6N88R6UI7EQ",
"timeStamp":"2021-11-12T00:12:29+05:30",
"event":"BILLER_UPDATES",
"data":{...}

1. traceId is a unique ID assigned to the error and used by (Website Name) to debug
2. timeStamp denotes the time when the webhook was triggered
3. event is a pre-defined list of event types used to define what the webhook was triggered for
4. data contains the webhook payload data

#Bill fetch webhook

You can use this webhook to get information about outstanding bills on BBPS. When the Fetch bill API is used, it will be triggered. An error message will be displayed if the bill does not exist.

Method : POST
URL    : To be provided by partner

Bill fetch sample request

{
"event":"BILL_FETCH",
"timeStamp":"2023-08-27T17:09:24.566+05:30",
"data":{
"bill":{
"amount":60500,
"billDate":"2023-06-02",
"billNumber":"3749280326878517751",
"billPeriod":"Monthly",
"customerName":"Elijah White",
"dueDate":"2023-06-02"
},
"billerRefId":"9540207519",
"exactness":"Exact",
"paymentLimits":[
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"Internet Banking",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"Debit Card",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"Prepaid Card",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"IMPS",
"supportsPendingStatus":false
},
{
"maxLimit":4999900,
"minLimit":100,
"paymentMode":"Cash",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"UPI",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"Wallet",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"NEFT",
"supportsPendingStatus":false
},
{
"maxLimit":99999900,
"minLimit":100,
"paymentMode":"AEPS",
"supportsPendingStatus":false
}
],
"refId":"CJLJBQK91PA0FD9MPMK0W75BD9M32391709",
"status":"Success"
}
}

#Bill payment webhook

A payment request for a particular bill has been received by NPCI. It will also pass on relevant errors and messages.

Method : POST
URL    : To be provided by partner

Bill payment sample request

{
"event":"BILL_PAY",
"data":{
"refId":"HENSVVR4QOS7X1UGPY7JGUV444P10102202",
"status":"PROCESSING/SUCCESS/FAILURE",
"billerRefId":"ABC1235",
"transactionId":"AX01122999900001",
"failureReason":{
"code":"BRR005",
"message":"Biller not accepting payments at the moment"
},
"paymentDetails":{
"mode":"Internet Banking/Debit Card/Credit Card/IMPS/Cash/UPI/Wallet/NEFT/Prepaid Card/AEPS/Account Transfer/Bharat QR/USSD",
"paymentRefId":"N2001121212344",
"amount":10000,
"timestamp":"2020-12-12T13:12:00+05:30"
},
"billerId":"VODA00000MUM03"
},
"success":true,
"traceId":"C3SFG0O6N88R6UI7EQ",
"error":null
}

#Dispute webhook

View the status update for a customer dispute using this webhook.

Method : POST
URL    : To be provided by partner

Dispute sample request

{
"event":"BILL_DISPUTE",
"data":{
"refId":"JPMRPBOGGDTP1EFRZVXVESQVQIS10461642",
"complaintId":"OP0121046567755",
"status":"PROCESSING / OPEN / CLOSED",
"assignedTo":"AX39",
"remarks":"Resolved in favour of customer"
},
"success":true,
"error":null
}

#Autofetch bill webhook

This informs you that a new bill is due for a particular bill.

Method : POST
URL    : To be provided by partner

Autofetch bill sample response

{
"event":"AUTOFETCH",
"data":{
"bill":{
"amount":324600,
"billDate":"2023-06-02",
"billNumber":"5085594745324366399",
"billPeriod":"Monthly",
"customerName":"Matthew Garcia",
"dueDate":"2023-06-02"
},
"billerRefId":"4096245202",
"customer":{
"billParameters":[
{
"name":"Application ID",
"value":"41116419"
}
],
"mobile":"9002198485"
},
"hash":"3ad9934ba90a1d0fd0fed3a3738dd74886240a1bb55575d18e07f063a10cc593",
"isActive":true,
"lastFetchDate":"2023-08-27",
"billerId":"AADH00000NATPT"
},
"timeStamp":"2023-08-27T17:09:26.405+05:30"
}

#Biller updates webhook

This is used to notify you about updates on any BBPS biller—including biller being added to or modified on the BBPS platform. In case of a biller gets modified, the request contains the biller with the new modification.

Method : POST
URL    : To be provided by partner

Biller updates sample request

{
"event":"BILLER_UPDATES",
"traceId":"C6I7O22PC5TNLVD7QSKG",
"timeStamp":"2021-11-29T12:36:48.910+05:30",
"data":[
{
"ID":699158487875191900,
"Status":"ACTIVE",
"BillerAcceptsAdhoc":"F",
"BillerAdditionalInfo":[
{
"DataType":"ALPHANUMERIC",
"Optional":true,
"ParamName":"URL"
},
{
"DataType":"ALPHANUMERIC",
"Optional":true,
"ParamName":"Early Payment Date"
}
],
"BillerAdditionalInfoPayment":null,
"BillerAliasName":"TATA PWR - MUM",
"BillerCategoryName":"DTH",
"BillerCoverage":"IND",
"BillerCustomerParams":[
{
"dataType":"NUMERIC",
"maxLength":12,
"minLength":12,
"paramName":"Consumer Number"
}
],
"BillerDescription":"",
"BillerEffctvFrom":"2017-10-31",
"BillerEffctvTo":"2025-12-31",
"BillerID":"ZEE500000NAT01",
"BillerMode":"ONLINE",
"BillerName":"ZEE TV",
"BillerOwnerShp":"Private",
"BillerPaymentChannels":[
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"INT"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"INTB"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"MOB"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"MOBB"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"POS"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"MPOS"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"ATM"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"BNKBRNCH"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"KIOSK"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"AGT"
},
{
"minLimit":100,
"maxLimit":500000000,
"paymentChannel":"BSC"
}
],
"BillerPaymentModes":[
{
"minLimit":1,
"paymentMode":"Internet Banking"
},
{
"minLimit":1,
"paymentMode":"Debit Card"
},
{
"minLimit":1,
"paymentMode":"Credit Card"
},
{
"minLimit":1,
"paymentMode":"Prepaid Card"
},
{
"minLimit":1,
"paymentMode":"IMPS"
},
{
"minLimit":1,
"paymentMode":"Cash"
},
{
"minLimit":1,
"paymentMode":"UPI"
},
{
"minLimit":1,
"paymentMode":"Wallet"
},
{
"minLimit":1,
"paymentMode":"NEFT"
},
{
"minLimit":1,
"paymentMode":"AEPS"
},
{
"minLimit":1,
"paymentMode":"Account Transfer"
}
],
"BillerResponseParams":{
"amountOptions":[
{
"amountBreakupSet":[
"BASE_BILL_AMOUNT"
]
},
{
"amountBreakupSet":[
"Early Payment Amount"
]
}
]
},
"BillerTempDeactivationEnd":"",
"BillerTempDeactivationStart":"",
"BillerTimeOut":"",
"CustomerParamGroups":{
"groups":null
},
"FetchRequirement":"MANDATORY",
"InterchangeFee":null,
"ParentBiller":"",
"PaymentAmountExactness":"EXACT",
"PlanAdditionalInfo":null,
"PlanMdmRequirement":"",
"SupportBillValidation":"",
"SupportDeemed":"",
"SupportPendingStatus":"",
"NameVector":"'mum':3 'pwr':2 'tata':1 'tv':5 'zee':4",
"Plans":[
{
"ID":773944272117303200,
"PlanID":"1",
"AmountInRupees":"99.0",
"BillerID":"ZEE500000NAT01",
"CategorySubType":{
"subType":"1 Month"
},
"CategoryType":"Premium",
"EffctvFrom":"2021-01-01",
"EffctvTo":"2021-12-31",
"PlanAdditionalInfo":[],
"PlanDescription": "All ZEE5 Originals and Exclusives, Blockbuster Movies, All ALT Balaji Shows, Zindagi TV Shows,
Kids, Live TV, TV shows before telecast. Watch on 5 devices at a time",
"Status":"ACTIVE"
},
{
"ID":773944272134080400,
"PlanID":"2",
"AmountInRupees":"299.0",
"BillerID":"ZEE500000NAT01",
"CategorySubType":{
"subType":"2 Months"
},
"CategoryType":"Premium",
"EffctvFrom":"2021-01-01",
"EffctvTo":"2021-12-31",
"PlanAdditionalInfo":[],
"PlanDescription": "All ZEE5 Originals and Exclusives, Blockbuster Movies, All ALT Balaji Shows, Zindagi TV Shows,
Kids, Live TV, TV shows before telecast. Watch on 5 devices at a time",
"Status":"ACTIVE"
},
{
"ID":773944272142469000,
"PlanID":"3",
"AmountInRupees":"599.0",
"BillerID":"ZEE500000NAT01",
"CategorySubType":{
"subType":"6 Months"
},
"CategoryType":"Premium",
"EffctvFrom":"2021-01-01",
"EffctvTo":"2021-12-31",
"PlanAdditionalInfo":[],
"PlanDescription": "All ZEE5 Originals and Exclusives, Blockbuster Movies, All ALT Balaji Shows, Zindagi TV Shows,
Kids, Live TV, TV shows before telecast. Watch on 5 devices at a time",
"Status":"ACTIVE"
},
{
"ID":773944272159246300,
"PlanID":"4",
"AmountInRupees":"999.0",
"BillerID":"ZEE500000NAT01",
"CategorySubType":{
"subType":"12 Months"
},
"CategoryType":"Premium",
"EffctvFrom":"2021-01-01",
"EffctvTo":"2021-12-31",
"PlanAdditionalInfo":[],
"PlanDescription": "All ZEE5 Originals and Exclusives, Blockbuster Movies, All ALT Balaji Shows, Zindagi TV Shows,
Kids, Live TV, TV shows before telecast. Watch on 5 devices at a time",
"Status":"ACTIVE"
},
{
"ID":773944272167635000,
"PlanID":"5",
"AmountInRupees":"365.0",
"BillerID":"ZEE500000NAT01",
"CategorySubType":{
"subType":"12 Months"
},
"CategoryType":"Club",
"EffctvFrom":"2021-01-01",
"EffctvTo":"2021-12-31",
"PlanAdditionalInfo":[],
"PlanDescription": "TV shows before telecast, Select ZEE5 Originals, Select ALT Balaji Shows, Select Movies, Zindagi
TV Shows, Kids, Live TV. Watch on 2 devices at a time",
"Status":"ACTIVE"
}
]
}
]
}