Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
Overview
About Stripe payments
Upgrade your integration
Payments analytics
Online payments
OverviewFind your use caseManaged Payments
Use Payment Links
Build a checkout page
Build an advanced integration
Build an in-app integration
Payment methods
Add payment methods
Manage payment methods
Faster checkout with Link
Payment interfaces
Payment Links
Checkout
Web Elements
In-app Elements
Payment scenarios
Handle multiple currencies
Custom payment flows
Flexible acquiring
Orchestration
In-person payments
Terminal
Beyond payments
Incorporate your company
Crypto
Financial Connections
Climate
Understand fraud
    Overview
    Types of fraud
    Card testing
    Identify fraud
    Verification checks
    Best practices
Radar fraud protection
Manage disputes
Verify identities
HomePaymentsUnderstand fraud

Card verification checks

Learn how to make use of card verification checks to protect against disputes and fraud.

When a card payment is submitted to a card network for authorization, Stripe provides the CVC, postal code, and billing street address for them to verify (if you collected these from the customer in your checkout flow). The card issuer checks this against the information they have on file for the cardholder. If the provided information doesn’t match, the verification check fails. A failed CVC or postal code check can indicate the payment is fraudulent, so review it carefully before fulfilling the order.

Each Charge object includes the verification response as part of its source attribute. You can also find the verification results in the Dashboard when viewing a payment.

If no information is collected, the card issuer can’t perform a verification check. Collect the CVC, postal code, and billing address for every payment to avoid this issue. The results of verification checks help improve the detection of fraudulent activity.

Card verification code check (CVC)

The CVC (or CVV) is the three- or four-digit number printed directly on a card that only cardholders in physical possession of the card should have access to. When you require the CVC value with a card payment method (during payment or when attaching the payment method to a customer’s profile), the card issuer verifies the value during transaction authorization.

Radar allows you to block payments that fail the card issuer verification in various situations by enabling a rule through the Dashboard. This doesn’t affect payments where the CVC check couldn’t be performed or is unavailable. For example, wallets like Apple Pay or off-session payments don’t require it.

Businesses can’t store the CVC number, so fraudsters are unlikely to obtain the CVC through a computer breach, making CVC verification an effective fraud prevention tool. However, CVC verification doesn’t protect against the physical theft of a card, nor computers or websites with poor security.

Address verification (AVS)

When you require the postal code and the billing street address with a card payment method (during payment or when attaching the payment method to a customer’s profile), the card issuer performs an AVS check to verify that they match the billing address on file.

Radar allows you to block payments that fail the postal code (AVS) verification in various situations by enabling a rule in the Dashboard. AVS checks can fail for legitimate payments. For example, a customer who enters their address incorrectly or moves without notifying their card issuer might see payments where the address check fails.

Support for AVS checks varies by country and card issuer. For example, certain countries don’t use a postal code, and some card issuers don’t support street address verification. Most cards issued in the United States, Canada, and the United Kingdom support street address verification.

See also

  • Best Practices for Preventing Fraud
  • Types of Fraud
  • Identifying Fraud
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Join our early access program.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc