Credit cards that require CVV re-entry are marked as “Invalid” and the process to re-enter CVV has unneeded friction. ChowNow invalidates CVVs for several reasons to help control fraud, including when a user adds a new delivery address, every 180 days and soon whenever a user logs in (web users are automatically logged out if they don’t start a session over a rolling 30-day period).
Saved credit cards that require CVV re-entry are marked as “Invalid” within the payment method selector, a label that doesn’t explicitly let the user know why or what is wrong with the card.

When re-entering a CVV, users must enter in all of their credit card information again, including the number, expiration date, CVV and zip code, when all that’s really needed is the CVV.

After researching best practices and looking at competitor checkout flows, I proposed:

• Highlight or single out the CVV prompt

• Let users know that this is a security measure for their benefit, but with the least amount of text possible.

• If the user doesn’t have their card on hand, they may want to use another option, like Paypal. Make it easy for them to switch payment option if they don’t want to re-enter their CVV.

• Detect card type and use appropriate security code acronym or ask for a “Security Code” instead. This can help a user know what’s being asked for and how to find it.

• Credit card numbers are created in a consistent way. American Express cards start with either 34 or 37. Mastercard numbers begin with 51–55. Visa cards start with 4. And so on. This information can be used to detect what type of credit card someone is using simply by looking at their credit card number.

The design helped decrease declined card/payment failure rates by ~60%.