# What Is CVV? Card Security Codes Explained for Merchants

> What CVV is, where to find it on Visa, Mastercard and Amex cards, how CVV checks work in online payments, PCI rules on storing it, and what it can and cannot stop.
- **Author**: Deepak Jangir
- **Published**: 2026-11-07
- **Category**: Payments, Fraud Prevention
- **URL**: https://dodopayments.com/blogs/en/what-is-cvv

---

CVV (card verification value) is the three- or four-digit security code printed on a payment card that is not part of the card number or the magnetic stripe. Merchants ask for it in online and phone payments to check that the person paying has the physical card, or at least saw it, rather than just a stolen list of card numbers. On Visa, Mastercard and Discover it is three digits on the back; on American Express it is four digits on the front.

For customers, CVV is a box at checkout. For merchants, it is one of several fraud signals with specific rules attached: you can ask for it, you can decline payments when it does not match, but you can never store it after the payment is authorized. This guide covers where to find the code, what it is called on each network, how CVV verification works behind the scenes, and what it does and does not protect you from.

## What Does CVV Stand For?

CVV stands for **card verification value**. In practice, the code printed on the card is technically "CVV2", the second-generation value used for [card-not-present transactions](https://dodopayments.com/blogs/card-not-present-transactions). The original CVV (sometimes called CVV1) is encoded in the magnetic stripe and is checked when a card is swiped, which is why the printed code is a separate value.

Each card network uses its own name for the same concept:

| Network | Name | Digits | Location |
| --- | --- | --- | --- |
| Visa | CVV2 (Card Verification Value 2) | 3 | Back, signature panel |
| Mastercard | CVC2 (Card Validation Code 2) | 3 | Back, signature panel |
| American Express | CID (Card Identification Number), also called CSC | 4 | Front, above the card number |
| Discover | CID (Card Identification Number) | 3 | Back, signature panel |

You will also see generic terms such as **CSC** (card security code) and **CVC** in checkout forms. They all refer to the same field.

## Where Is the CVV on a Card?

For most cards, flip the card over and look at the signature strip or the area beside it. The CVV is the three-digit number, sometimes printed after the last four digits of the card number. For American Express, look on the front of the card for a small four-digit number printed above the main card number.

Some newer cards print the number on the back without a signature strip, and some numberless card designs move all details to the back. Virtual cards in banking apps show the CVV in the card details screen, and some banks offer **dynamic CVV**, where the code changes periodically in the app to make stolen details useless sooner.

## How CVV Verification Works in an Online Payment

When a customer enters their CVV at checkout, the code travels with the authorization request. The merchant never "checks" it locally. The issuing bank compares it with the value it expects and returns a result code.

```mermaid
flowchart LR
    A["Customer enters card,
expiry and CVV"] --> B["Payment provider
(tokenizes card)"]
    B --> C["Card network"]
    C --> D["Issuing bank
checks CVV"]
    D -->|"Match / No match"| C
    C --> B
    B --> E{"Approve or decline
based on result + rules"}
```

The response includes a CVV result alongside the approval decision. Common results are:

- **Match:** the code is correct.
- **No match:** the code is wrong. Most issuers decline outright; some approve and leave the decision to the merchant.
- **Not processed or unavailable:** the issuer did not check it.
- **Not provided:** the merchant did not send a CVV.

A well-configured payment stack declines "no match" results automatically. Allowing them through is one of the easiest ways to let fraud in, because a fraudster with a stolen card number but no CVV will guess. The same authorization response also carries the address verification result, explained in our guide to [AVS mismatches](https://dodopayments.com/blogs/avs-mismatch).

## Why Merchants Ask for CVV

CVV exists because card numbers leak far more often than physical cards are stolen. Data breaches, skimmers and phishing pages expose card numbers in bulk, but properly built systems never store the CVV, so breached databases usually lack it.

Requiring the CVV gives you:

- **A possession check.** Whoever is paying has seen the physical or virtual card.
- **Fewer fraudulent approvals.** Payments from dumps of card numbers without CVVs fail at authorization.
- **Better dispute evidence.** A "CVV matched" result is part of the evidence for card-not-present fraud disputes, alongside AVS and [3D Secure](https://dodopayments.com/blogs/3d-secure-3ds-payment-authentication) results.
- **Often better acceptance.** Issuers see a complete, verified request as lower risk.

## What CVV Cannot Protect You From

CVV is a useful filter, but it is weak on its own:

| Threat | Does CVV help? | Why |
| --- | --- | --- |
| Card numbers from a database breach | Yes | Breached data usually lacks the CVV |
| Phishing pages and fake checkouts | No | The victim types the CVV into the fake page |
| Malware skimming checkout forms | No | Scripts capture everything the customer enters |
| [Card testing](https://dodopayments.com/blogs/card-testing-fraud) with guessed CVVs | Partly | Velocity limits and bot detection matter more |
| [Friendly fraud](https://dodopayments.com/blogs/friendly-fraud-prevention) by the real cardholder | No | The real cardholder knows their own CVV |
| Account takeover with saved cards | No | Saved-card charges do not re-ask for the CVV |

That last row matters for subscription and SaaS businesses. Recurring charges on a stored card are processed without a CVV, because the merchant is not allowed to keep it. The protection comes from the first payment being verified properly, from [network tokenization](https://dodopayments.com/blogs/network-tokenization), and from fraud scoring on later activity.

## Can Merchants Store CVV? The PCI DSS Rule

No. Under PCI DSS, the card verification code is **sensitive authentication data**. It may not be stored after the transaction is authorized, even if it is encrypted. This applies to databases, logs, paper forms, call recordings, screenshots and support tickets.

Practical consequences for merchants:

- **Never log raw request bodies** from checkout forms. Debug logs are a common place where CVVs end up by accident.
- **Do not collect CVV on paper.** A [credit card authorization form](https://dodopayments.com/blogs/credit-card-authorization-form) should not include it.
- **Mask call recordings** if your team takes card payments over the phone.
- **Do not ask customers to email card details.** If they do, delete the message and ask them to pay through a secure link.

The simplest way to stay compliant is to never let the CVV touch your servers. Hosted checkouts and payment provider iframes collect the card number and CVV directly, tokenize the card, and give your system a token. Our [PCI DSS compliance guide](https://dodopayments.com/blogs/pci-dss-compliance-digital-business) explains how this keeps you in the lightest compliance tier, and the [raw card API guide](https://dodopayments.com/blogs/raw-card-api-pci-compliance) covers what changes if you handle card data yourself.

## Why Subscriptions Charge Without the CVV

Customers sometimes ask why a recurring charge went through when they never re-entered their CVV. The answer is the stored credential framework. At the first payment, the customer enters the full card details including the CVV, agrees to recurring terms, and the provider stores a token. Later charges are flagged as merchant-initiated transactions on a stored credential, which issuers process without a CVV.

With [Dodo Payments](https://dodopayments.com), this happens through the hosted checkout. The CVV is validated on the first payment, the card is tokenized, and renewals are charged automatically on each billing date. The [cards documentation](https://docs.dodopayments.com/features/payment-methods/cards) lists the protections applied to card payments, including PCI DSS Level 1 certification, tokenization on entry, real-time fraud scoring, CVV validation and 3D Secure. To require 3D Secure on a high-risk checkout, you can pass `force_3ds` when creating the session:

```javascript
// Require 3D Secure for this checkout, in addition to CVV validation
const session = await client.checkoutSessions.create({
  product_cart: [{ product_id: 'pdt_annual_plan', quantity: 1 }],
  customer: { email: 'buyer@example.com', name: 'Alex Rivera' },
  force_3ds: true,
  return_url: 'https://yourapp.com/welcome',
});
```

Requiring 3D Secure on every payment reduces fraud but can lower conversion, because some customers abandon during authentication. A balanced setup lets the issuer and risk engine trigger it when needed and reserves forced 3DS for high-value or high-risk products. The [subscriptions documentation](https://docs.dodopayments.com/features/subscription) explains how renewals and failed payments are handled on stored cards.

## CVV, AVS and 3D Secure Compared

CVV is one of three checks merchants commonly rely on for card-not-present payments. They answer different questions:

| Check | Question it answers | Strength | Liability shift |
| --- | --- | --- | --- |
| CVV | Does the payer have the card details printed on the card? | Blocks bulk stolen card numbers | No |
| AVS | Does the billing address match the issuer's records? | Catches mismatched stolen identities, mainly in the US, UK and Canada | No |
| 3D Secure | Can the cardholder authenticate with their bank? | Strongest, uses the bank's own login or biometrics | Yes, on authenticated transactions |

Using all three, with 3D Secure triggered on riskier payments, gives far better protection than any one alone. Our [payment security best practices](https://dodopayments.com/blogs/payment-security-best-practices) guide shows how they fit into a layered setup.

## CVV and Payment Declines

An incorrect CVV is one of the most common reasons legitimate customers get declined. It often shows up as a specific decline code such as "incorrect CVC" or "security code invalid". Our list of [credit card decline codes](https://dodopayments.com/blogs/credit-card-decline-codes) shows how processors label it.

To keep these declines from costing you sales:

- **Show a specific error.** "Your card's security code is incorrect" converts better than "Payment failed".
- **Let customers retry without retyping everything.**
- **Do not loosen CVV rules to "fix" declines.** A wave of CVV mismatches is often card testing, not customer error. See our guide to [reducing payment declines](https://dodopayments.com/blogs/reduce-payment-declines) for the safe way to improve approval rates.
- **Watch for spikes.** A sudden jump in CVV failures from many cards on one product is a classic card-testing pattern.

## FAQ

### Is CVV the same as CVC?

Yes. CVV (Visa) and CVC (Mastercard) are network-specific names for the same card security code. American Express and Discover call it CID. Checkout forms often use the generic labels CVV, CVC or security code.

### Is it safe to give my CVV when paying online?

It is safe on a legitimate, secure checkout, because merchants are not allowed to store it after the payment is authorized. Do not share it by email, chat or over an unverified phone call, and only enter it on checkout pages you reached from the merchant's own site.

### Why does American Express have a 4-digit CVV on the front?

American Express uses a four-digit Card Identification Number printed on the front of the card as its security code design. It serves the same purpose as the three-digit code on the back of Visa, Mastercard and Discover cards.

### Can a payment go through without a CVV?

Yes. Recurring and saved-card payments are processed without a CVV under stored credential rules, and some merchants choose not to require it on certain transactions. Most online checkouts require it for the first payment because it lowers fraud.

### How long can a merchant keep my CVV?

Only until the payment is authorized. PCI DSS prohibits storing the card verification code after authorization, even in encrypted form, so a compliant merchant never keeps it in databases, logs or paper records.

## Conclusion

CVV is a short code with a specific job: proving that the person paying has seen the card. It blocks payments made with bulk-stolen card numbers and strengthens dispute evidence, but it does nothing against phishing, malware or friendly fraud, and it cannot be stored once the payment is authorized. Pair it with AVS, 3D Secure and fraud scoring, and keep it off your servers entirely by using a hosted checkout. To accept cards with tokenization, CVV validation and fraud screening handled for you, start with the [Dodo Payments integration guide](https://docs.dodopayments.com/developer-resources/integration-guide) or see [Dodo Payments pricing](https://dodopayments.com/pricing).
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)