CVV is a three- or four-digit security code printed on credit and debit cards to verify that the cardholder physically possesses the card during a transaction. CVV stands for Card Verification Value and is also known as CVC, CSC. Or CVV2, depending on the card brand. It helps prevent fraud in card-not-present transactions, such as online or phone purchases, by ensuring the code is not stored in magnetic stripe or chip data.
Category
Fraud prevention
Used for
Card-not-present transaction verification
Common confusion
CVV is not the same as the card’s PIN or magnetic stripe data
Also called
CVC, CSC
Often discussed with
Credit Card Payment Processing, Online Credit Card Processing

CVV. Or Card Verification Value, is a security feature designed to protect credit and debit card transactions from fraud. Unlike the card number or expiration date, which can be stored or transmitted during transactions, the CVV is a dynamic code that's not embedded in the magnetic stripe or EMV chip. This makes it harder for fraudsters to use stolen card details for online or phone purchases, where the physical card is not present. The code is typically printed on the back of Visa, Mastercard. And find cards (three digits) or the front of American Express cards (four digits).
Related glossary terms: Card Not Present Transaction, PCI Compliance, Payment Processor.
CVV serves as an additional layer of authentication, ensuring that the person initiating the transaction has access to the physical card. While it doesn't guarantee absolute security, it significantly reduces the risk of unauthorized transactions, particularly in e-commerce or mail-order/telephone-order (MOTO) scenarios. For merchants, requiring CVV during checkout can lower the likelihood of chargebacks due to fraud, as it provides evidence that the customer had the card in hand at the time of purchase.
When a customer enters their CVV during an online or phone transaction, the merchant’s payment processor sends the code to the card issuer for verification. The issuer checks the CVV against the code stored in its secure database and either approves or declines the transaction based on the match. This process happens in real time, adding only a few seconds to the checkout experience. Importantly, the CVV is not stored in the merchant’s systems after the transaction is completed, as PCI DSS (Payment Card Industry Data Security Standard) prohibits merchants from retaining this data.
The CVV’s effectiveness lies in its separation from other card data. Since the code is not encoded in the magnetic stripe or chip, it can't be skimmed or copied during in-person transactions. This makes it particularly valuable for card-not-present transactions, where fraud rates are higher. But CVV is not foolproof—if a fraudster gains access to the physical card or a photograph of it, they can still use the CVV. For this reason, CVV is often used alongside other fraud prevention tools, such as address verification (AVS) or two-factor authentication.
For merchants, requiring CVV during transactions can reduce fraud-related losses and chargebacks. Chargebacks occur when a customer disputes a transaction, often due to fraud. And the merchant is forced to refund the payment. By verifying the CVV, merchants can demonstrate that they took reasonable steps to confirm the cardholder’s identity, which can help in disputing fraudulent chargebacks. And some payment processors offer lower interchange fees for transactions that include CVV verification, as these transactions are considered lower risk.
For consumers, CVV provides an added layer of security, particularly for online shopping. While it does not prevent all forms of fraud, it makes it harder for criminals to use stolen card numbers without access to the physical card. Consumers should treat their CVV with the same care as their card number, avoiding sharing it unnecessarily or storing it in unsecured locations, such as emails or digital notes.
CVV is most critical in card-not-present transactions, where the merchant cannot physically inspect the card. This includes online purchases, phone orders. And mail-order transactions. In these scenarios, merchants are at higher risk of fraud, as criminals can use stolen card details without needing the physical card. Requiring CVV during checkout can deter fraudsters, as they're less likely to have access to the code. But CVV is not required for card-present transactions, such as in-store purchases, where the card is swiped, dipped. Or tapped at a terminal.
Merchants must also be aware of PCI DSS requirements regarding CVV. The standard prohibits merchants from storing CVV after a transaction is authorized, even if the data is encrypted. This rule is designed to cut down on the risk of CVV data being stolen in a breach. Merchants who fail to comply with this requirement may face fines or lose their ability to process credit card payments. And some industries, such as travel or subscription services, may have specific rules about when CVV can be collected or used for recurring payments.
A PIN is a numeric code used for in-person transactions at ATMs or point-of-sale terminals. While CVV is a security code used for card-not-present transactions like online purchases.
AVS verifies the cardholder’s billing address. While CVV verifies the physical card’s security code. Both are used to reduce fraud but serve different purposes.
An EMV chip generates a unique transaction code for in-person purchases. While CVV is a static code printed on the card for online or phone transactions.
While CVV is a valuable fraud prevention tool, it is not a silver bullet. Merchants should combine CVV verification with other security measures, such as AVS, tokenization. And fraud detection algorithms, to create a layered defense against unauthorized transactions.
A customer purchases a laptop online and enters their card number, expiration date. And CVV during checkout. The merchant’s payment processor sends the CVV to the card issuer, which verifies the code before approving the transaction. The merchant does not store the CVV, complying with PCI DSS requirements.
Card Not Present Transaction is a payment processed without the physical card being swiped, dipped. Or tapped at a terminal. These transactions occur online, over the phone, via mail order. Or through recurring billing, where the merchant can't verify the cardholder’s identity in person. They carry higher risk and often incur additional fees due to increased fraud potential.
PCI Compliance is adherence to the Payment Card Industry Data Security Standard (PCI DSS), a set of security requirements designed to protect cardholder data during credit and debit card transactions. PCI Compliance applies to any organization that accepts, processes, stores. Or transmits payment card information, ensuring consistent security measures to prevent data breaches and fraud.
Payment Processor is a financial technology company or service that acts as an intermediary between merchants, card networks. And banks to authorize, clear. And settle credit and debit card transactions. Payment Processors handle the technical and financial workflows required to transfer funds from a customer’s issuing bank to a merchant’s acquiring bank, ensuring transactions are secure, compliant. And completed in real time or near real time.
Tokenization is a data security process that replaces sensitive information, such as credit card numbers, with unique identification symbols called tokens. These tokens retain essential data without exposing actual details, reducing the risk of fraud or data breaches during transactions. Tokenization is widely used in payment processing to comply with security standards like PCI DSS while maintaining transaction functionality.
CreditCardProcessing-SanDiego.com
Contact CreditCardProcessing-SanDiego.com for practical guidance on CVV and related credit card processing work in San Diego.