CVV, or Card Verification Value, is a security code that users are required to enter when initiating card transactions online.
In accordance with the latest guidelines from the Reserve Bank of India (RBI), CVV is now required to be collected by merchants only during the first transaction when the card is being saved by the user, i.e., during the tokenization of the card.
When users attempt to initiate payments using a saved card (one that has been tokenized), CVV input is not necessary. Users can authenticate the payment simply by using OTP after selecting the saved card on the merchant payment page.
CVV Less Payments are supported by Juspay, empowering merchants to integrate this simplified flow seamlessly into their checkout page.
Merchants live with CVV Less flow: Swiggy, Redbus, Myntra, Cred etc
Invalid Youtube video link.
Explainer Video
Invalid Youtube video link.
Feature Benefits
Reduced time for payment
No scope of CVV related errors
One click checkout for card transactions
Upto 3% improvement in card success rates
User Journey
Frequently Asked Questions
1. Do all cards support this feature?
All cards issued by VISA and Mastercard, regardless of the issuing bank, support CVV-less transactions. However, for Rupay and AMEX cards, only a limited number of issuing banks currently offer this feature.
All banks and card networks are working towards adopting this new feature in the near future.
2. Is Native OTP (or DOTP) same as CVV-less payments?
No, both are distinct features designed to enhance the customer experience.
Native OTP (DOTP) provides an improved UI/UX for the card authentication step, and you can find more details here.
CVV-less payments are applicable only for saved card transactions, where the card used is already tokenized. In such cases, additional CVV details are not required in a repeat transaction flow. This feature works seamlessly with the Native OTP flow to deliver the best user experience for card transactions.
3. Does this feature work for guest checkout journeys?
No, the CVV input is optional only for tokenized card transactions, i.e. transactions attempted through a saved card. However, for guest users making payments using the card number, the CVV value is a mandatory input.
In case the CVV field is not included for these checkout journeys, transaction will fail.
4. What should I do if some of my PA/PG(s) do not support or enable this feature?
Juspay routes the CVV Less transactions to only supported gateways by default.
For example, if there are four gateways [PG1, PG2, PG3, PG4] configured for card payments for your account on Juspay Dashboard and only two of them [PG1, PG3] support CVV less payments :
PGs that will be used for processing CVV less Payments : [PG1, PG3]
PGs that will be used for card payments with CVV : [PG1, PG2, PG3, PG4]
The traffic routing for remaining payments to different PA/PGs will continue as per your PG configurations and the priority logic set by you.
5. Does Native OTP work together with CVV-less transactions?
Yes, enabling both CVV-less and Native OTP flow together allows users to complete transactions with just a single click, provided that the BIN (Bank Identification Number) supports both the flows.
