NPCI Onboarding Configurations

Apart from the legal and branding details, there are a few technical configurations that need to be set with NPCI - the same have been highlighted below. Biller has to take a decision on each of them and submit along with the APIs.

1. [Mandatory] What are the set of input parameters which will be sent as customer attributes and customer will have to key them in from the payment app ? For each parameter, describe the following details -
   • Name of the parameter (e.g. phone_number, loan_number, policy_no).
   • Data Type of the parameter (e.g Alphanumeric/Numeric/Date).
   • Any special characters allowed in the param value - if yes, which?
   • Minimum and Maximum length of the param value (e.g. 3 to 10 characters).
2. [Mandatory] What is the amount exactness of the payment you want to receive from BBPS. Select one of the following:
   • ADHOC - Customer will be able to edit the amount and input any number to make the payment.
   • EXACT - Amount would be non-editable.
   • EXACT DOWN - Customer would be able to edit the amount and input a figure which is equal or Less than the amount retrieved from Bill Fetch.
   • EXACT UP - Customer would be able to edit the amount and input a figure which is equal or Greater than the amount retrieved from Bill Fetch.
3. [Optional] Do you want to add any additional parameters in Bill Fetch Response? If yes, what are they? (This will become part of the additional_Info object in response.
4. [Optional] Do you want to always accept the payment - In this case even if your systems are down, the payment will be accepted by Cashfree and later retried to post to your system. It is recommended if you have no business logic for declining the payments. If you have business logic for decline then it is recommended to accept/reject each payment as per your logic.