Products & Features

Covers queries regarding BillDesk's payment products such as BillDesk Neo – Full Redirect, CX+ – Deep API, platforms, plugins, and more.

Products

Q. Which BillDesk product is suitable for you?

A. BillDesk offers range of products that will be suitable to you as per your business need. Please check below our offerings and select the product more aligned to your need.

Q. What payment methods does BillDesk support?

A. BillDesk offers an extensive array of 150+ payment methods, encompassing UPI, cards, net banking, wallets, EMI, and more, providing your customers with diverse options for online payments. With our robust payment solutions, you can enhance customer convenience and satisfaction, ensuring seamless transactions every time.

Q. What is Neo – Full Redirect?

A. With minimal code development at your end, you can integrate the payments functionality for your website. Your customers will get redirected to the BillDesk Payment page, where in the customer will be able to choose between a variety of payment options viz., credit/ debit cards, netbanking, UPI, EMI etc. Once the customer completes the payment on the bank's site, the customer will finally get redirected to your Return URL wherein you can update the status of the transaction and display a payment acknowledgement message to the customer.

Q. What is Ace – SDK?

A. Similar to the Neo – Full Redirect, we offer another customer experience that enables you to display the payment options to the customer on your checkout page directly as modal (pop-up) window.

Q. What is CX+ – Deep API?

A. Are you PCI DSS certified? Do you manage the customer payment experience on your site/ app? If you answered Yes to both, then you could consider the CX+ – Deep API for your payments integration. You can interface with BillDesk using APIs while offering the best customer experience as per your needs.

Tokenisation

Q. What does Tokenisation of card mean?

A. Card tokenisation is a process of replacing actual card details by an encrypted code called the token, which is stored and used for future transactions. BillDesk offers tokenisation so that you can now offer a secure saved-card experience using tokens on your website, or app and improve your customer checkout experience.

Q. What are the benefits of Tokenisation?

A. Tokens do not contain any personally identifiable information and hence using them in transactions instead of card numbers makes the transactions more secure.

Since merchants and payment aggregators can store tokens, Tokenisation also enables a saved card experience for the customers during checkout.

Q. How can a card be tokenised?

A. Typically, a card tokenisation process consists of the following steps:

• Customer enters the full card details
• Customer gives explicit consent to save and tokenise the card
• Merchant initiates the tokenisation request directly or via another token requestor (TR)
• On successful Additional Factor of Authentication (AFA), the request is routed to a corresponding Token Service Provider (TSP), which is either a Network or the Issuing bank
• The TSP generates a token for the card in its vault

Q. Is Tokenisation applicable for international cards?

A. No. Tokenisation is mandated and applicable only for domestic (India) transactions.

Q. Does tokenisation affect the transactions done at a POS or a Merchant outlet?

A. No. Tokenisation is mandated and applicable only for online transactions. Even in online transactions, tokenisation is applicable only on the platforms where there is a saved card experience. If the customers are entering the full card details in the check out, tokenisation is not applicable in such transactions.

Q. Is it mandatory for a customer to tokenise her/ his card?

A. No. The customer can still enter the full card details and complete the transaction. However, if they want to reduce this effort and save their cards on the Merchant/ checkout platforms, then tokenisation is a necessity.

Q. Is there a limit on the number of times a card can be tokenised?

A. No. There is no limit on the number of times a card can be tokenised. It is expected that a card will be tokenised across multiple Merchant platforms.

Q. Will card tokenisation need to be completed at every Merchant platform separately?

A. Yes. Similar to a customer saving her/ his cards on each Merchant platform, tokenisation will also be required on each one of them individually.

Q. Can a bank (Issuer) decline a tokenisation request on a card?

A. Yes. If the card belongs to a BIN range that is not approved or onboarded for tokenisation, the Token Service Provider may decline the request to generate a token for that card.

Q. What are the different integration models of Card-on-File Tokenisation solutions that BillDesk offers to Merchants?

A. BillDesk allows Merchants to choose any one of the following integration models:

1. Merchant as Token Requestor (TR) - The cards will be tokenised by BillDesk with the Merchant as TR for all the token-related requests.
2. BillDesk as Token Requestor (TR) - The cards will be tokenised by BillDesk on behalf of Merchants and BillDesk will be the TR for these tokens.

Recurring Payments

Q. What is a recurring payment?

A. BillDesk offers services that allow merchants to enable subscription-based services for their customers and debit transaction amount at a regular interval. For example, an internet service provider can offer subscription services based on recurring payments or e-Mandates.

Q. What do I need to do to enable recurring payments?

A. We recommend you to get in touch with the BillDesk Relationship Manager (RM) to get the feature enabled for you to start offering it to your end customers.

Q. Can the Payment + eMandate Registration take place in the same transaction?

A. Yes, the feature is available with BillDesk. You can register for a mandate/e-Mandate as part of payment request itself. Please go through our guides section or Click Here.

Q. Is there a real-time confirmation of the recurring charge?

A. For a Card/ UPI AutoPay recurring charge the confirmation is in real-time. However, for an eNACH based recurring payment the confirmation will be sent through a webhook notification to the merchant.

Q. Can a customer sign up for autopay on a merchant website without an immediate "purchase"? For example - Setting up utility payments for future payments etc.

A. Yes, this is possible. Say for example, a customer is to be offered a free trial post which the recurring charge should be processed as per the frequency of the subscription plan; or say you want the customer to setup an e-Mandate so that the next insurance premium onwards the customer gets debited automatically.

Q. During the e-Mandate creation process, is the validity and current balance of the UPI id checked?

A. As a process, validity of UPI id is checked but the balance is not checked.

Q. During the e-Mandate creation process for UPI, is the Customer PSP availability checked?

A. No (Currently there is no restriction on any handle, PSP Acquirer returns an error)

Q. Is there a maximum time limit for the duration of e-Mandate? E.g. Can there be a perpetual e-Mandate of variable frequency valid till cancelled?

A. The maximum limit for an e-Mandate is set to 30 years for eNACH/ UPI AutoPay. No maximum duration limit is defined for e-Mandate on cards.

Q. Is there a limit on amount of e-Mandate?

A. BillDesk has not defined any limit on the amount for an e-Mandate.

Q. Does auto pay support plan upgrades? If the consumer has set up a variable frequency and variable amount, can e-Mandate amount be changed to a higher amount?

A. Yes. Merchant can use Modify e-Mandate to modify amount and end date. Alternatively, merchant can also setup an e-Mandate with higher amount and MAX condition while setting up mandate itself.

Q. Where can the customer remove/pause the e-Mandate (customer bank/ customer PSP app)?

A. Customer can 'pause', 'resume' an e-Mandate or 'revoke' such an e-Mandate through customer PSP app. Both actions require customer to enter UPI PIN to authenticate the action.

Q. When the consumer modifies an e-Mandate, does the merchant gets informed?

A. Yes. BillDesk will inform the merchant through web hooks.

Q. Is additional authentication required when merchant initiates a Modification or Revoke an Autopay e-mandate?

A. For modification of an e-Mandate, customer will need to do the authentication. To revoke an e-Mandate, no authentication is required.

Q. Is additional authentication required when customer initiates a revoke of an Autopay e-mandate from bank or issuer website?

A. Yes, an additional authentication is required on customer PSP app

Q. Does the customer get notification on each pre-debit (Invoice)?

A. The pre-debit notification (PDN) is sent to customer PSP app, and the issuer bank sends the SMS to the customer informing about each pre-debit (Invoice) request.

Q. If there is a blanket e-Mandate, do customers have to authenticate every time they make a purchase?

A. No, if the amount is up to Rs 15,000. For transaction amount above Rs 15,000, customer has to authenticate.

*The Reserve Bank of India (RBI) has released a circular RBI/2023-2024/88
CO.DPSS.POLC.No.S-882/02.14.003/2023-24 to revise the maximum amount that can be paid with e-mandates for recurring online transactions without the need for an Additional Factor of Authentication (AFA) to Rs. 1 lakh from the previous Rs. 15,000 for (a) subscription to mutual funds, (b) payment of insurance premiums, and (c) credit card bill payments.

Q. When an autopay charge fails, is there any retry mechanism that merchant can apply?

A. When an autopay charge fails, there may be multiple reasons associated with it. For a charge fail because of insufficient funds merchant can retry the following ways.

In case the reason is PDN not sent, merchant needs to retry sending the PDN and try the charge post 24 hrs of PDN.

For the e-Mandates that are paused by the customers, merchant has to wait until customer resume/continue the charge to go through for the said e-Mandate.

In case where the e-Mandate is cancelled from PSP app, the e-Mandate cannot be restored either from customer side or merchant side. Merchant will need to essentially create a new e-Mandate.

Q. If an e-Mandate is created by merchant on one acquiring bank, can he initiate charges for that e-Mandate from alternate acquiring?

A. No. Once an e-Mandate is created on a particular merchant VPA, all subsequent debits can be done through this VPA only.

Q. For UPI, when e-Mandate is created successfully and after e-Mandate creation, customer uninstalls the PSP application or changes phone or switches off the phone, will execution of mandate charge fail in these cases?

A. No. e-Mandate is registered at customer bank and customer PSP end. Customer device does not have any implications. Unless the recurring charge amount is greater than the permissible limit which would require customer to do the additional authentication.

Q. Can a customer suspend an e-Mandate for limited time?

A. Yes, customer can pause/ resume an e-Mandate through customer UPI PSP App.

Q. Can a Revoked e-Mandate get re-instated or does it have to be created again?

A. In such a scenario, e-Mandate/ Mandate needs to be created again.

Q. If customer changes the registered number in his bank account, does this impact existing e-Mandates?

A. No, he will still receive notifications on SMS from bank on the new number.

Q. For UPI Autopay, if customer creates an e-Mandate through a PSP Issuer App and uses one of his bank accounts with Bank 1 as an issuing bank, and if customer changes this to Bank 2, will recurring transactions on the PSP Issuer still get honored?

A. Yes

Q. When a merchant creates an e-Mandate of Rs. 20,000, as per RBI guidelines customer authorization is required above Rs. 15000. Is this validated in PDN or charge step?

A. PDN is a one-way communication in UPI Autopay. During charge call, customer needs to authorize this.

Q. How many different durations/ frequencies of e-Mandates can be supported?

A. The following frequencies are currently supported:

• weekly - Once in a week
• monthly - Once in a month
• bi-monthly - Twice in a month
• quarterly - Once in a quarter or 3 months
• bi-annually - Twice in a year
• yearly - Once in a year
• adhoc - Others

Account Validation Service

Q. What is an Account Validation Service?

A. Account Validation Service (AVS) offered by BillDesk lets you pre-define the account from where you would want your customers to complete the transaction. This service ensures that the customer completes the transaction from the account specified by you.

Q. Does Account Validation Service validates IFSC code?

A. Yes, BillDesk supports validation of IFSC code when you integrate with AVS API.

Q. Does AVS validates bank account number?

A. Yes, BillDesk supports validation of bank account number when you integrate with AVS API.

Q. Where can I use the Account Validation Service?

A. There are lots of services where you can make use of Account Validation Services, such as, loan, insurance, Systematic Investment Planning (SIPs) etc.

Guest Checkout

Q. What is Alternate ID (Alt-ID) for guest checkout transactions?

A. The Reserve Bank of India (RBI) has issued guidelines that require Payment Gateways (PGs) and Payment Aggregators (PAs) to ensure safer and more customer-friendly digital payment solutions and has specified that no entity in the card transaction/ payment chain, other than the card issuers and/ or card networks, shall store CoF (card-on file) data. An Alt ID is an alternate identifier for a real card number provided by cardholder during a guest checkout transaction. BillDesk supports Alt-ID based guest checkout transactions that is compliant with these guidelines.