What will happen to existing mandates?
All existing mandates will have to be tokenized, and a migration activity using the Update SI API has to be performed. For more information, refer to Modify the Recurring Payments for a Card
To tokenize the card, the consent of a customer has to be present. A successful customer consent means that the AFA on that card should have been successful.
- If merchant wants to do migration, then the merchant can update the mandate with the token using the Update SI API.
- If merchant wants PayU to do the migration, same has to be informed to their respective PayU Key Accounts Manager. PayU will do the migration and inform about the successful migrations through an excel report.
What will happen to new mandates?
- Mandates through plain card
- Merchant will pass plain card number. PayU post-authentication will tokenize the card and then authorize the transaction.
- There can be cases where merchants might not want PayU as a token requestor. This case is possible but will lead to an additional leg where PayU will authorize and return an intermediate response of authorization. The merchant will have to tokenize with the token requestor and then update the token through the Update SI API. For more information, refer to Modify the Recurring Payments for a Card.
- Mandates through already generated tokens
- The merchant will initiate the transaction with a token. PayU will set up the subscription, initiate the AFA and activate the subscription basis of the token passed.
- Mandates through plain card
If the merchant has not taken consent for a token, can they update the token without customer intervention?
Yes, the merchant can tokenize the card and call our S2S API to update the token without any customer intervention.
Is this tokenization approach final?
- Representation to the regulator has been already made for SI hub to store the card, which means that if the approval comes, there is no change for the merchant in the recurring leg for the merchant to process existing mandates and new mandates through plain cards. For mandates setups where instead of the plain card, there is only a token available, in that case, the merchant will need to pass the token in the _payment API and PayU will set up and do AFA basis token.
- If the above approach is not feasible, the merchant will have to tokenize the card and update the subscription with the token. Now, if the regulator approves of treating SI consent as tokenization consent, the merchant can start doing bulk migration without customer intervention; otherwise, the merchant needs explicit tokenization consent.
- Payu suggests to follow the new approach and go live with it asap.
Can cards saved through SI be used for saved cards transactions?
SI Consent can be used to tokenise cards for SI. If merchant wants to use the token for other purposes, then an explicit consent is required and whether same token can be used or an additional token has to be created, that still requires clarity from regulator.
- What are the payment instruments for Subscriptions?
The following are the payment instruments available for Subscriptions:
- Net Banking
- UPI Autopay
- Does PayU support physical eNACH and Aadhaar eNACH?
No, PayU does not support physical eNACH and Aadhaar eNCAH.
- Which UPI banks or mobile apps are supported for UPI Autopay?
PayU supports UPI Autopay. for banks or mobile apps. For the list of UPI banks or mobile apps. For more information, refer to UPI Handles
- Which banks are supported for Net Banking recurring payments?
PayU supports NetBanking recurring payments for banks and cards. For a list of banks and cards, refer to Bank Codes - Recurring Payments
- What happens when users get the ‘Card not Supported’ error while registering a mandate?
This error indicates that the specific customer’s card does not support recurring payments. Hence, the customer needs to use another card. To check if a card supports recurring payments using seamless integration (Merchant Hosted or S2S), use the Get BIN Info API. For more information, refer to Get Bin Info API.
- What can be the maximum end date for a mandate with cards?
The maximum end date for a card mandate is the card’s expiry.
- Do I need to use separate APIs to create cards, Net Banking, and UPI Autopay mandates?
No, only the _payment API is required to create Cards, Net Banking, and UPI Autopay mandates.
- Is pre-debit necessary for Net Banking to enable recurring transactions?
No, pre-debit is required only for Cards and UPI.
- Is pre-debit mandatory for recurring transactions using cards and UPI?
Yes, pre-debit is mandatory for cards. You must use pre-debit at least 24 hours before the recurring charge transaction.
- What are the possible ways to integrate recurring payments with PayU?
You can integrate recurring payments with PayU using the following methods:
- Using API Integration
- Using PayUBiz Dashboard(Zero-Code Change)
- Using Zion Subscription Automation
- Does PayU support the interoperability of eNACH mandates?
No, PayU is currently developing this feature and will communicate it to you after it is released.
- What is a Consent or Registration Transaction in the context of recurring payments?
A Consent or Registration Transaction is the first transaction in a recurring payment series, in which the customer provides consent to the merchant to charge their card or bank account for future transactions. This transaction typically involves storing the payment information securely in the payment gateway for future use.
- What is the workflow for a Consent or Registration Transaction?
For the workflow for a Consent or Registration Transaction, refer to Customer Experience and Workflow - Recurring Payments based on the payment mode.
- What are the benefits of using a Consent or Registration Transaction for recurring payments?
The benefits of using a Consent or Registration Transaction for recurring payments include improved customer experience, reduced payment friction, and increased convenience for both customers and merchants. By storing payment information securely in the payment gateway, merchants can process future transactions more easily and reduce the need for customers to enter payment information repeatedly.
- How does PayU ensure the security of payment information in a Consent or Registration Transaction?
PayU uses various security measures such as PCI-DSS compliance, encryption, tokenization, and fraud detection to ensure the security of payment information in a Consent or Registration Transaction. PayU also stores payment information in a secure, encrypted format, and allows merchants to access the information only when needed.
- Can customers cancel Consent or Registration Transactions at any time?
Yes, your customers can cancel Consent or Registration Transactions at any time, by contacting the merchant or the payment gateway directly. You should have a clear cancellation policy in place and make it easy for customers to cancel Consent or Registration Transactions if they choose to do so.
- Can I use different payment methods for Consent or Registration Transactions and subsequent transactions in a recurring payment series?
Yes, you can use different payment methods for Consent or Registration Transactions and subsequent transactions in a recurring payment series. However, it is recommended that you use the same payment method for all transactions in a recurring payment series to avoid confusion and potential errors.
- What is a Payment Consent Transaction?
A Payment Consent Transaction is the initial transaction in a recurring payment series, in which the customer provides consent to the merchant to charge their payment method for future transactions. This transaction typically involves storing the payment information securely in the payment gateway for future use.
- How can a Payment Consent Transaction be registered using the PayU API?
A Payment Consent Transaction can be registered using the PayU API by sending a request to the PayU server with the payment information and transaction details. The API supports various payment methods, including credit cards, debit cards, net banking, and UPI.
- What are the steps involved in registering a Payment Consent Transaction using the PayU API?
For the steps involved in registering a payment consent, refer to the following based on the integration:
- Payment Consent Transaction using PayU Hosted Checkout
- Payment Consent Transaction using Merchant Hosted Checkout
- What are the benefits of using the PayU API to register a Payment Consent Transaction?
The benefits of using the PayU API to register a Payment Consent Transaction include faster implementation, improved checkout experience for customers, and reduced risk of fraud and chargebacks. By using the API, merchants can automate the payment process and avoid manually handling payment information, which reduces the effort required to implement the feature.
Updated 7 days ago