Introduction
PayU Vault APIs allow users to store multiple credit card or debit card details on PayU Vault (Cloud) easily and safely. PayU Vault stores the card details and provides access to you (merchant) when your customer provides his/her user credentials accompanied with or without a card token.
Your users save invaluable time when they use their cards that are stored on PayU Vault instead of entering the card details when they make payments safely on your website. Customers can use saved cards on all the merchant websites where they support PayU Vault.
Users can update or delete their card details on the PayU vault when required. You may need to enable this on their website.
The workflow for users with PayU Vault are:
- Customer visit the merchant’s website, adds items to the cart, or utilize the merchant’s services, and then enter the card details.
- Customer provides consent to the merchant and the merchant saves the card details on PayU Vault
- Customer visits the same merchant and uses the saved card details to proceed with the transaction.
- Customer provides his/her user credentials, the merchant retrieves the card details and the user enters the CVV or 3DBC number to complete payment.
Note: While CVV is not mandatory from the network perspective, some banks may impose the necessity of the same for doing transactions with a saved card. Also, if the bank does not mandate the CVV but the merchant captures the same, CVV will be verified. It is recommended that for the banks where CVV is not required, merchants should not ask for the same
- User can update or delete the card details when required.
Note:
You need to ensure that you have filled the “Self-Assessment Questionnaire A-EP and Attestation of Compliance” form from PCI, which is mandatory for all entities seeking to store, process, and transmit cardholder data.
Updated 7 days ago