Skip to main content
In addition to legal and branding details, billers must submit the following technical configurations to NPCI as part of the onboarding process. Review each configuration and provide your decisions along with your API contracts.

Customer input parameters

Required Define the input parameters that customers must enter in the payment app to identify their account or bill. For each parameter, provide the following details:

Payment amount exactness

Required Select the amount behaviour you want to apply to payments received through BBPS.

Additional bill fetch response fields

Optional If your bill fetch response needs to return fields beyond the standard response, specify the additional parameters here. These become part of the additional_info object in the bill fetch response.

Payment acceptance behaviour

Optional Select whether your system should always accept payments, or accept and reject based on business logic.
  • Always accept: Cashfree accepts all payments on your behalf, even if your systems are unavailable, and retries posting to your system later. Recommended if your system has no business logic for declining payments.
  • Accept or reject per transaction: Your system evaluates and responds to each payment individually. Recommended if you have business logic that requires declining specific payments.