List of Payment Modes [v3]
This API returns a list of payment modes that can be shown to the user to select on your checkout. The list only includes payment options that are enabled for you. The API also returns if the payment mode has any offers or additional charges to be levied.
Request Body required
This is the order_id returned by Nimbbl in response to the create order API
- 200
- 4XX
- 5XX
When the list of payment modes are fetched, the response will be as below
Schema
- pay_later
- upi
- credit_card
- debit_card
- prepaid_card
- Array [
- ]
- Array [
- ]
- intent
- collect
- Array [
- ]
- Array [
- ]
- Array [
- ]
- Array [
- ]
- Array [
- ]
- card_tray
- upi_tray
- wallet_tray
- netbanking_tray
- emi_tray
- standalone
- Array [
- ]
- Array [
- ]
- Array [
- ]
- Array [
- ]
- Array [
- ]
- pay_later
- payment_app
- Array [
- ]
- Array [
- ]
- Array [
- ]
- Array [
- ]
fast_payment_mode object
These are payment modes that are enabled for you and personalised for the customer.
Possible values: [fast
]
The display tray provides a hierarchy of how you can display these payment modes on your checkout. In the fast_payment_mode object currently only a single tray is supported and all underlying payment methods can be shown in the same hierarchy and there is a single parent called fast
The name of the display tray under which the payment modes can be shown on your checkout.
The logo of the display tray to be shown along side the display tray name on your checkout.
The description or sub text to be shown along with the display tray.
items array
This key will return an array of payment modes that belong to the customer, these are linked with the mobile number and email id of the customer that you have shared in the create-order API
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
Possible values: [Pay Later
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [lazypay
, simpl
, paytm_paylater
, icici_paylater
, mobikwik_zip
, kreditbee_paylater
, freecharge_paylater
, kissht_paylater
]
This is the code for the pay later created by Nimbbl, it could be used in subsequent API calls
The name of the pay later provider, it can be used in subsequent API calls
schemes object[]
The scheme contains details regarding the financing plans provided by the pay later provider
This is the due date on which the first EMI will need to be paid. For single EMI period pay laters, this will be the date on which repayment will be due
This is the total number of EMIs that will need to be repaid
This is the unique scheme id provided by Nimbbl, it will be required in subsequent API calls
This is the processing fee that will need to be paid by the customer to opt for this financing plan
This is the annual percentage rate of the financing plan. This needs to be displayed to your customer as per RBI guidelines
This is the instalment amount that the customer will need to repay when opting for this financing plan
This is the interest portion of the instalment
This is the down payment amount that the customer will need to pay first before the loan begins
This is for future use by Nimbbl
This is for future use by Nimbbl
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is a public URL from which the logo of the pay later provider can be fetched
This field provides the link to the terms and conditions of the paylater.
This field provides the link to the key fact statement of the paylater.
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [UPI
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
This is the UPI payment flow that is available for you
This is the name of the UPI app
Possible values: [gpay
, phonepe
, paytm
]
Specifies the UPI app that you want to open for the flow, the API will respond with an app specific intent URL. If it's not passed, the response will contain the generic intent URL.
This is the name of the UPI app
This is the code for the UPI app created by Nimbbl, it could be used in subsequent API calls
This is the name of the account holder who owns the UPI id
Possible values: Value must match regular expression [a-zA-Z0-9.\-_]{2,256}@[a-zA-Z]{2,64}
This is the UPI id of the customer
This is a public URL from which the logo of the UPI app provider can be fetched
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Credit Card
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
The URL of logo of the network
The URL of logo of the issuer
Specifies whether cvv is required to initiate a transaction or not.
token object
The label used for identifying the saved card
The issuer of the saved card
The network of the saved card
The last 4 digits of the saved card
The token id generate by nimbbl when the card was saved
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [get_bin_data
]
If you want to check details of the card entered by your customer on your checkout, then you can call this API
Possible values: [/api/v3/get-bin-data
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Debit Card
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
The URL of logo of the network
The URL of logo of the issuer
Specifies whether cvv is required to initiate a transaction or not.
token object
The label used for identifying the saved card
The issuer of the saved card
The network of the saved card
The last 4 digits of the saved card
The token id generate by nimbbl when the card was saved
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [get_bin_data
]
If you want to check details of the card entered by your customer on your checkout, then you can call this API
Possible values: [/api/v3/get-bin-data
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Prepaid Card
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
The URL of logo of the network
The URL of logo of the issuer
Specifies whether cvv is required to initiate a transaction or not.
token object
The label used for identifying the saved card
The issuer of the saved card
The network of the saved card
The last 4 digits of the saved card
The token id generate by nimbbl when the card was saved
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [get_bin_data
]
If you want to check details of the card entered by your customer on your checkout, then you can call this API
Possible values: [/api/v3/get-bin-data
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
offers object[] nullable
The offers array provides the list of offers configured by you along with the offer discount and grand total amount calculated as per the offer
This is the additional charge that will be charged for this payment mode
This is amount that will be discounted as per the offers that have been configured by you
This is the unique offer id provided by Nimbbl, it can be used in subsequent API calls
This is the offer name as configured
This is the offer start date in UTC
This is the offer end date in UTC
This is the description of the offer that can be used by you on your checkout
This is the grand total that will be sent for processing i.e. the total_amount - offer_discount + additional_charges
other_payment_modes object
These are payment modes that are enabled for you but are not personalised for the customer.
Possible values: [other
]
The display tray provides a hierarchy of how you can display these payment modes on your checkout. In the other_payment_modes object, the parent tray will come as other
. Payment modes below will be logically grouped in different display trays to help you build a checkout page
The name of the display tray under which the payment modes can be shown on your checkout.
The logo of the display tray to be shown along side the display tray name on your checkout.
The description or sub text to be shown along with the display tray.
items array
This key will return an array of payment modes that are enabled for you but aren't personalised for the customer
The display tray is a recommendation by Nimbbl to bunch certain payment modes together on your checkout
Possible values: [Credit Card
, Debit Card
, Prepaid Card
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [credit_card
, debit_card
, prepaid_card
]
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
This is a flag which tells us if there are any offers available
This is for future use by Nimbbl to fetch the logo of the payment mode from a public URL
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [get_bin_data
]
If you want to check details of the card entered by your customer on your checkout, then you can call this API
Possible values: [/api/v3/get-bin-data
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [UPI
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [upi
]
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
This is a flag which tells us if there are any offers available
This is for future use by Nimbbl to fetch the logo of the payment mode from a public URL
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [validate_vpa
]
If you want to validate the upi_id entered by the customer on your checkout, then you can call this API
Possible values: [/api/v3/validate-vpa
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Wallet
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [wallet
]
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
This is a flag which tells us if there are any offers available
This is for future use by Nimbbl to fetch the logo of the payment mode from a public URL
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [list_of_wallets
]
You can fetch the list of wallets and any corresponding offers available with them so you can show these to your customer on your checkout
Possible values: [/api/v3/list-of-wallets
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Netbanking
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [net_banking
]
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
This is a flag which tells us if there are any offers available
This is for future use by Nimbbl to fetch the logo of the payment mode from a public URL
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [list_of_banks
]
You can fetch the list of banks and any corresponding offers available with them so you can show these to your customer on your checkout
Possible values: [/api/v3/list-of-banks
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Credit Card EMI
, Debit Card EMI
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [credit_card_emi
, debit_card_emi
]
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is for future use by Nimbbl to fetch the logo of the payment mode from a public URL.
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
This is a flag which tells us if there are any offers available
This is the maximum additional charge that can be applied.
This is the maximum grand total amount that can be applied.
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [list_of_emis
]
You can fetch the list of EMIs and any corresponding offers available with them so you can show these to your customer on your checkout
Possible values: [/api/v3/emis
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
This is the code for the payment mode created by Nimbbl, it could be used in subsequent API calls
Possible values: [Pay Later
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [lazypay
, simpl
, paytm_paylater
, icici_paylater
, mobikwik_zip
, kreditbee_paylater
, freecharge_paylater
, kissht_paylater
]
This is the code for the pay later created by Nimbbl, it could be used in subsequent API calls
The name of the pay later provider, it can be used in subsequent API calls
schemes object[]
The scheme contains details regarding the financing plans provided by the pay later provider
This is the due date on which the first EMI will need to be paid. For single EMI period pay laters, this will be the date on which repayment will be due
This is the total number of EMIs that will need to be repaid
This is the unique scheme id provided by Nimbbl, it will be required in subsequent API calls
This is the processing fee that will need to be paid by the customer to opt for this financing plan
This is the annual percentage rate of the financing plan. This needs to be displayed to your customer as per RBI guidelines
This is the instalment amount that the customer will need to repay when opting for this financing plan
This is the interest portion of the instalment
This is the down payment amount that the customer will need to pay first before the loan begins
This is for future use by Nimbbl
This is for future use by Nimbbl
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is a public URL from which the logo of the pay later provider can be fetched
This field provides the link to the terms and conditions of the paylater.
This field provides the link to the key fact statement of the paylater.
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
Possible values: [Payment App
]
This is the payment mode that needs to be shown to the customer, it can also be used in subsequent API calls
Possible values: [freecharge
, paytm
]
This is the code for the payment app created by Nimbbl, it could be used in subsequent API calls
Possible values: [Freecharge
, Paytm
]
The name of the payment app provider, it can be used in subsequent API calls
This is the description of the display tray.
This is the URL of the logo for the display tray.
This is the subtext for the display tray.
This is for future use by Nimbbl to fetch the logo of the payment mode from a public URL
next object[]
The next array provides a recommendation for the next API call to be made, where multiple options are available, all of these are provided
Possible values: [initiate_payment
]
Once your customer has chosen their payment method and provided all information to initiate the payment, you can use this API
Possible values: [/api/v3/initiate-payment
]
This is the end point of the API that needs to be called for the above action, you will need to append the baseurl as provided in this doc
This is the amount before tax shared by you in the create-order API
This is the tax amount shared by you in the create-order API
This is the currency shared by you in the create-order API
This is the total amount shared by you in the create-order API
This is the additional charge that will be charged for this payment mode
This is the grand total that will be sent for processing i.e. the total_amount + additional_charges
offers object[] nullable
The offers array provides the list of offers configured by you along with the offer discount and grand total amount calculated as per the offer
This is the additional charge that will be charged for this payment mode
This is amount that will be discounted as per the offers that have been configured by you
This is the unique offer id provided by Nimbbl, it can be used in subsequent API calls
This is the offer name as configured
This is the offer start date in UTC
This is the offer end date in UTC
This is the description of the offer that can be used by you on your checkout
This is the grand total that will be sent for processing i.e. the total_amount - offer_discount + additional_charges
{
"fast_payment_mode": {
"parent_display_tray": "fast",
"display_tray_name": "string",
"display_tray_logo": "string",
"display_tray_subtext": "string",
"items": [
null
]
},
"other_payment_modes": {
"parent_display_tray": "other",
"display_description": "string",
"display_tray_logo": "string",
"display_tray_subtext": "string",
"items": [
{
"payment_mode": "Credit Card",
"payment_mode_code": "credit_card",
"display_tray": "card_tray",
"logo_url": "https://s3.ap-south-1.amazonaws.com/nimbbl/card/visa_v1.png"
},
{
"payment_mode": "Debit Card",
"payment_mode_code": "debit_card",
"display_tray": "card_tray",
"logo_url": "https://s3.ap-south-1.amazonaws.com/nimbbl/card/visa_v1.png"
},
{
"payment_mode": "Prepaid Card",
"payment_mode_code": "prepaid_card",
"display_tray": "card_tray",
"logo_url": "https://s3.ap-south-1.amazonaws.com/nimbbl/card/visa_v1.png"
},
{
"payment_mode": "UPI",
"payment_mode_code": "upi",
"display_tray": "card_tray",
"logo_url": "https://s3.ap-south-1.amazonaws.com/nimbbl/card/visa_v1.png"
}
]
}
}
When the list of payment modes cannot be fetched, the response will be as below
Schema
error object
This is the error_code generated by Nimbbl
This is a customer friendly message that can be displayed to your consumer
This explains to your team how to recover from the error
{
"error": {
"nimbbl_error_code": "INVALID_REQUEST_PARAMETER",
"nimbbl_consumer_message": "Sorry, your payment cannot be processed due to a technical error. Please try again after some time.",
"nimbbl_merchant_message": "There is an input validation error, please check the payload of your request."
}
}
When there is a problem on the server, the response will be as below
Schema
error object
This is the error_code generated by Nimbbl
This is a customer friendly message that can be displayed to your consumer
This explains to your team how to recover from the error
{
"error": {
"nimbbl_error_code": "INVALID_REQUEST_PARAMETER",
"nimbbl_consumer_message": "Sorry, your payment cannot be processed due to a technical error. Please try again after some time.",
"nimbbl_merchant_message": "There is an input validation error, please check the payload of your request."
}
}