Payment Modes
With NTT DATA Payment Services India, you can enjoy a multitude of payment modes, giving your customers the flexibility to choose their preferred payment method. Diversifying payment options not only widens your customer base but also enables them to make more significant purchases. This contributes to an enhanced customer experience, reducing instances of shopping cart abandonment.
Net Banking
We let you seamlessly facilitate payments from your customers through Net banking. Customers input their Net banking credentials to complete transactions. This method is readily available by default, requiring no extra integration or permissions for activation at your application's Checkout.
For net banking payments, customers can choose their bank and enter the required credentials seamlessly with our payment gateway. We extend support to over 50+ banks across India.
Here is the compilation of banks for which our payment gateway provides net banking support.
- Airtel Payments Bank
- AU Small Finance Bank
- AU Small Finance Bank Limited
- Axis Bank NB
- Bandhan Bank
- Bank of Baroda Corporate
- Bank of Baroda Retail
- Bank of India
- Bank of Maharashtra
- Canara Bank
- Central Bank of India
- Capital Small Finance Bank
- City Union Bank
- Cosmos Bank
- CSB Bank
- DCB Bank
- Deutsche Bank
- Dhanlaxmi Bank
- EQUITAS BANK
- Federal Bank - Retail
- HDFC Bank
- HSBC Bank
- ICICI Bank - Retail
- ICICI Bank - Corporate
- IDBI Bank
- IDFC FIRST Bank Limited
- Indian Bank
- Indian Overseas Bank
- IndusInd Bank
- Jammu and Kashmir Bank
- Jana Small Finance Bank
- Janata Sahakari Bank LTD Pune
- Karnataka Bank
- Karur Vysya Bank
- Kotak Mahindra Bank
- Lakshmi Vilas Bank
- NKGSB Co-op Bank Ltd
- Punjab & Sind Bank
- Punjab National Bank - Corporate
- Punjab National Bank - Retail
- RBL Bank
- Royal Bank Of Scotland
- Saraswat Bank - Retail
- South Indian Bank - Retail
- Standard Chartered Bank
- Standard Chartered Bank - Retail
- State Bank of India
- Suryoday Small Finance Bank Ltd
- Tamilnad Mercantile Bank
- UCO BANK
- Ujjivan Small Finance Bank
- Union Bank of India - Retail
- Yes Bank
UPI
Accept payments seamlessly from customers through UPI apps such as Google Pay, BHIM UPI, PhonePe. Alternatively, customers can make direct payments by entering the UPI VPA.
Using NTT DATA Payment Services India for UPI checkout ensures a seamless payment experience for users, offering higher transaction success rates compared to other payment modes. NTT DATA Payment Services India supports integration with multiple third-party apps.
UPI Collect Request Flow
As per the UPI Collect Request flow, the payer enters their UPI VPA on the payment page. Subsequently, the VPA undergoes validation before the transaction is initiated. Once the VPA is validated, the payer receives notification on the VPA associated PSP application to authorize the transaction. Subsequently, the VPA undergoes validation before the transaction is initiated.
Here's how the flow unfolds:
- The customer opts for UPI as the preferred payment mode within the merchant app/website.
- The customer inputs the Virtual Payment Address (VPA).
- The customer receives a push notification and/or SMS indicating the collect request.
- Upon acceptance of the collect request by the customer, the customer enters the UPI PIN / MPIN.
- Confirmation of the successful payment is received by the customer through the app/website.
UPI Intent Flow
The UPI Intent Flow, supported on both iOS and Android devices, offers a seamless experience where customers are automatically redirected to their preferred PSP app, enhancing the payment process. With our payment gateway, UPI intent integration empowers merchants to facilitate direct payments through the UPI app installed on the customer's mobile phone, such as Google Pay, PhonePe, Amazon Pay, BHIM, and more, ensuring swifter and simpler UPI transactions.
Here's how the UPI Intent Flow unfolds:
- The customer chooses UPI as the preferred payment mode within the merchant app/website.
- The customer is presented with a list of UPI apps installed on their phone that support the intent flow.
- The customer selects their preferred UPI application to proceed.
- The chosen UPI app opens with pre-populated payment details.
- The customer enters the UPI PIN / MPIN to finalize the payment.
- Confirmation of the successful payment is received by the customer through the app/website.
Benefits of UPI Intent:
- Customers are relieved from remembering and entering VPA.
- Eliminates the need for customers to manage push/SMS notifications.
- Streamlines the transaction process, sparing customers from navigating through three apps (merchant, SMS, UPI app).
- Enhances the overall payment process, contributing to a higher conversion rate, reduced abandoned carts, and quicker payment completion times.
- The ease of making payments results in an optimal user experience for your customers.
Supported Platforms:
- UPI Intent Flow for Web Checkout is supported seamlessly on mobile devices by default.
- For Mobile SDK, UPI Intent Flow is efficiently supported on Android, iOS, and other hybrid platforms such as React Native and Flutter. This empowers customers to initiate payments using any of the UPI applications installed on their devices. For instance, if a customer has BHIM and Google Pay installed, these two applications will be exclusively available for making payments.
UPI Payment Link
Generate and distribute UPI payment links to seamlessly collect payments through UPI applications with our payment gateway. Crafting a UPI payment link involves initially adding your product and customer details. Share the payment link effortlessly through SMS, email, WhatsApp, or any preferred platform.
For payments, customers simply need to click the URL you've provided, and a list of UPI apps installed on their mobile will be presented. Customers can then choose their preferred UPI app to complete the payment.
Cards
The advantage of utilizing cards lies in the additional security layer during payment transactions. As a precautionary step, customers input their card number, expiry date, and CVV. The CVV plays a crucial role in fraud detection by cross-referencing customer details with the CVV number.
Our payment gateway accommodates a comprehensive range of major debit, credit (both retail and corporate), including but not limited to Visa, Mastercard, Amex, RuPay, Diners, Discover, Maestro, and others. This grants you the flexibility to selectively accept payments from specific card types.
Features:
- Save customer’s details for easy transaction retry: Secure your customer’s card information using tokenization. For subsequent transactions, customers only need to input the CVV of the previously stored card, eliminating the need to enter card details repeatedly. In accordance with RBI guidelines, we store cards in a tokenized format; we ensure the security of sensitive card details by exclusively retaining the tokens.
- 3DS2 Authentication Protocol: 3DS2 stands as an authentication protocol, empowering businesses, and payment providers to transmit supplementary information (such as customer device or browser data) to validate the transaction's authenticity. Our payment gateway integration is fully compliant with the 3DS2 protocol.
The customer's bank assesses the transaction for risk and determines the payment flow.
- Frictionless Flow: This mechanism activates when the bank identifies the transaction as originating from a trusted device, allowing the payment to proceed without extra authentication from the customer. Presently, this isn't applicable in India for domestic payments due to RBI's mandate for OTP-based authentication. However, it is applicable for international payments.
- Challenge Authentication Flow: This pathway is triggered when the bank perceives the transaction as originating from an untrusted device, requiring additional information. The customer must undertake supplementary authentication steps.
- CVV-less Flow for Card Payments: The innovative CVV-less payment feature has been introduced for saved cards, allowing cardholders to finalize transactions without the need for the card CVV. This streamlined method of card payments is both straightforward and secure, providing a swift and hassle-free experience for your customers. As a business, we recommend eliminating the CVV box entirely from the customer's checkout experience. This not only encourages customers to opt for their saved cards as a convenient payment method but also facilitates a quicker checkout process, enhancing overall user satisfaction.
Wallets
Mobile Wallet payments offer customers a convenient alternative to using physical cards. This method is often considered more secure, thanks to encrypted data that safeguards sensitive information. The streamlined and efficient checkout process associated with mobile wallets can incentivize customers to engage in more frequent and hassle-free transactions.
Refer to the table below for available wallets on the checkout page for your customers:
- Paytm
- PhonePe
EMI
We offer a seamless platform for collecting payments with EMI. When opting for EMI, the customer's credit card issuing bank assesses and decides whether to approve or reject the order. To proceed with EMI payments, customers need a credit card issued by one of the supported banks.
Once EMI transaction requests are submitted, they cannot be cancelled, modified, or reversed until approved or rejected by the issuing banks of the credit card holders.
Upon selecting the EMI plan, customers can view the entire amount charged on credit card payments. If eligible for EMI, customers can choose a bank from the list provided below, along with their corresponding rates and tenures. Once the customer selects an EMI plan, full amount is then settled to the merchant via bank.
Subsequently, customers are required to pay monthly instalments to the bank as specified in the EMI plan.
- Axis Bank
- HSBC Bank
- Kotak Bank
- Standard Chartered Bank
- Yes Bank
- RBL
- Bank of Baroda
Challan (NEFT/RTGS)
A challan is a document that serves as a means of transferring funds from one account to another. Typically, it includes the names and bank details of both parties, along with the date of the transaction.
Customers can utilize for NEFT, IMPS, and RTGS (bank transfers) payments directly on your checkout page, enabling the merchant to either make payment via online or offline mode. This method is often considered a reliable fallback option. Bank transfers are particularly popular for B2B transactions and larger payments, such as wholesale orders.
Advantages of Challan include:
- Facilitates cash flow management by effectively monitoring expenses and receivables.
- Acts as a catalyst for improved cash management and enhanced control over financial matters.
- Enables businesses to track inventory and monitor overall business performance.
Currencies
Currently, payments are accepted in 'INR' only. International debit and credit cards are accepted.
Status Codes
| Code | Message | Description | Remark |
|---|---|---|---|
| OTS0000 | Success | Transaction successful | - |
| OTS0601 | Failed | In stage two transaction, NDPS txn ID should not be null | - |
| OTS0602 | Failed | Incorrect surcharge amount | - |
| OTS0603 | Failed | Sub-channel cannot be empty | - |
| OTS0604 | Failed | If subchannel is NB then bank id shouldn’t be empty | - |
| OTS0605 | Failed | If subchannel is CC or DC then card data should not be empty | - |
| OTS0606 | Failed | If subchannel is UP then VPA should not be empty | - |
| OTS0607 | Failed | If subchannel is EM then EMI details should not be empty | - |
| OTS0608 | Failed | In stage two transaction, subchannel can not be empty | - |
| OTS0609 | Failed | Card details are missing | - |
| OTS0610 | Failed | Invalid EMI tenure | - |
| OTS0611 | Failed | Invalid EMI bank name | - |
| OTS0612 | Failed | Summation of amount & surcharge amount should be equal to total amount | - |
| OTS0613 | Failed | Response is already available in DB for NDPS txn ID | - |
| OTS0614 | Failed | NDPS’ amount mismatched with bank's amount | - |
| OTS0615 | Failed | - | Any of the mandatory parameter must be missing |
| OTS0616 | Failed | Insufficient merchant information | - |
| OTS0617 | Failed | In stage two transaction, DB stage should be 1 | - |
| OTS0618 | Failed | In stage two transaction, provided amount should be equal to DB amount | - |
| OTS0619 | Failed | Subchannel & card type mismatched | - |
| OTS0620 | Failed | Card scheme mismatched | - |
| OTS0621 | Failed | Amount should be within a range | - |
| OTS0622 | Failed | Account details mandatory for penny drop | - |
| OTS0623 | Failed | In seamless transaction, when merchant is on surcharge then surcharge amount should | - |
| OTS0624 | Failed | Transaction response is already available for NDPS txn ID | - |
| OTS0625 | Failed | Bank txn amount is mismatched with NDPS txn amount | - |
| OTS0626 | Failed | Amount & total amount of all passed products should be equal | - |
| OTS0627 | Failed | Inappropriate way to consume OTS payment service | - |
| OTS0628 | Failed | NDPS txn ID should not be empty/null in bank response | - |
| OTS0629 | Failed | In semi-seamless transaction, if it is card transaction then surcharge amount should not be null/empty/zero | - |
| OTS0630 | Failed | Card type mismatched | - |
| OTS0631 | Failed | Failed-invalid card number | - |
| OTS0632 | Failed | Failed-card exp month/year should be in proper format | - |
| OTS0633 | Failed | Failed-card is expired | - |
| OTS0634 | Failed | Failed-invalid CVV | - |
| OTS0635 | Failed | Failed-transaction mode not found in URL pattern | - |
| OTS0636 | Failed | Failed-unable to decrypt card details | - |
| OTS0637 | Failed | Failed-unable to decrypt enc data | - |
| OTS0638 | Failed | - | Any of the mandatory parameters must be missing from enc data |
| OTS0639 | Failed | Failed-future date not allowed | - |
| OTS0640 | Failed | Failed-Date format must be: "+OTSUtil.ATOM_DATE_PATTERN | - |
| OTS0641 | Failed | Merch ID or enc data missing | - |