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:| Field | Description |
|---|---|
| Name | Parameter identifier, for example, phone_number, loan_number, policy_no |
| Data type | Alphanumeric, Numeric, or Date |
| Special characters | Whether special characters are allowed in the value, and if so, which ones |
| Length | Minimum and maximum character length of the value, for example, 3 to 10 characters |
Payment amount exactness
Required Select the amount behaviour you want to apply to payments received through BBPS.| Option | Description |
|---|---|
ADHOC | Customer can enter any amount |
EXACT | Amount is non-editable |
EXACT DOWN | Customer can enter an amount equal to or less than the bill fetch amount |
EXACT UP | Customer can enter an amount equal to or greater than the bill fetch amount |
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 theadditional_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.