Accept Online banking India payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.
Requirements
Requirement | Description |
---|---|
Integration type | Make sure that you have built an API-only integration. |
Setup steps | Before you begin, add Online banking India in your test Customer Area. |
Build your payment form for Online banking India
To show Online banking India in your payment form, you need to:
- Show Online banking India as an available payment method.
- Show a list of available banks to your shopper.
- After the shopper selects a bank, pass the corresponding issuer value to your server. You'll need this to make a payment. Make a /paymentMethods call to obtain the complete list of issuers for Online banking India. For example, if the shopper selects Central Bank of India, pass the value CBI.
We provide an Online banking India logo that you can use on your payment form. For more information, refer to Downloading logos.
We recommend you do not use a hardcoded form, because the list of issuers for Online banking India is long and changes relatively often, and not all issuers are online all the time.
Because of the large number of small issuers, we recommend you use a dynamically generated form showing the top 10 issuers, and an option to show more issuers if the shopper's bank is not listed.
If you are using the /paymentMethods to show available payment methods to the shopper, specify the following:
- countryCode: IN
- amount.currency: Any supported currency. For example, INR.
- channel: Specify Web, iOS, or Android.
The list of issuing banks and IDs is included in the object with paymentMethod.type
: onlinebanking_IN.
Make a payment
In your /payments request, specify:
paymentMethod.type
: onlinebanking_INpaymentMethod.issuer
: The issuer ID of the shopper's selected bank.
The /payments response includes the action
object with information that you must use to redirect the shopper.
Handle the redirect
-
To complete the payment, redirect the shopper to the
action.url
returned in the /payments response, taking into account the following recommendations:-
When using the HTTP GET method:
For security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView. -
Redirection for mobile integrations:
For mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.
-
-
After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:
details
: object that contains the URL-decodedredirectResult
returned when the shopper was redirected back to your site.
-
In the response note the following:
resultCode
: use this to present the result to your shopper.pspReference
: our unique identifier for the transaction.
Present the payment result
Use the resultCode that you received in the /payments/details response to present the paym