Skip to content

Stripe test cards

Every card number in Stripe's testing docs, grouped the way Stripe lists them, with what each one does and the expiry, CVC, and postal code it needs. Flint processes cards on Stripe, so each of these also works in a Flint sandbox with no Stripe account.
Verified against official documentationReviewed Send a correction (opens in a new tab)

Stripe test cards by scenario

Card-number-driven: nearly every scenario has its own card number, and the expiry, CVC, and postal code can be any valid value. Where a cell names a trigger, use it with any of Stripe's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.

ScenarioStripeFlint
Successful payment4242 4242 4242 42424242 4242 4242 4242any future expiry, any CVC, any ZIP
Generic decline4000 0000 0000 00024000 0000 0000 0002
Insufficient funds4000 0000 0000 99954000 0000 0000 9995
Lost or stolen card4000 0000 0000 99874000 0000 0000 9979lost, stolen4000 0000 0000 99874000 0000 0000 9979lost, stolen
Expired card4000 0000 0000 00694000 0000 0000 0069
Incorrect CVC4000 0000 0000 01274000 0000 0000 0127
3D Secure challenge4000 0000 0000 32204000 0025 0000 3155
3D Secure authentication failsNo dedicated card4000 0000 0000 3220fail the challenge
Card saves, then charges fail4000 0000 0000 03414000 0000 0000 0341
Dispute or chargeback4061 2199 4639 38104000 0000 0000 02594000 0000 0000 02594000 0000 0000 1976fraudulent, inquiry

Declines, 3D Secure, and disputes

How Stripe triggers declines

Stripe gives each decline its own card number: 4000 0000 0000 0002 for a generic decline, 4000 0000 0000 9995 for insufficient funds, 4000 0000 0000 0069 for an expired card, and more in the declined payments group below. The expiry, CVC, and postal code can be any valid value, but Stripe skips the CVC and postal checks when you omit them, so a check-failure card only fails when you send the value.

How Stripe tests 3D Secure

Only the cards in Stripe's 3D Secure table test your authentication flow. 4000 0000 0000 3220 succeeds only after authentication, 4000 0025 0000 3155 requires it on every on-session payment, and the 3D Secure mobile cards test each challenge UI in Stripe's mobile SDKs. Other cards can still trigger 3D Secure, but return attempt_acknowledged.

How Stripe simulates disputes

Dispute cards succeed and then open a dispute: 4000 0000 0000 0259 as fraudulent during the payment, 4061 2199 4639 3810 shortly afterward, and 4000 0000 0000 1976 as an inquiry. Submit winning_evidence or losing_evidence as the dispute's evidence to close it either way.

Look up a Stripe test card

Paste with or without spaces or dashes. Matching runs in your browser, and the URL never holds a full card number unless it's a documented test card.

147 cards and 14 trigger values from Stripe

Comparing processors? The full test card lookup checks a number against Flint, Stripe, Adyen, Braintree, PayPal, Square, Checkout.com, and Authorize.net at once.

Every Stripe test card#

147 cards, 14 triggers

Card-number-driven: nearly every scenario has its own card number, and the expiry, CVC, and postal code can be any valid value.

Expiry
Any future date, such as 12/34
CVC
Any 3 digits; any 4 digits for American Express
Postal code
Any value
  • Omit the CVC or postal code and Stripe skips that check, so a check-failure card only fails when you send the value.
  • Cards that simulate issuer declines can't be attached to a Customer.
  • Only the cards in the 3D Secure table test your 3DS integration; other cards may still trigger 3DS but return attempt_acknowledged.
  • Card-level state from one test can affect the next, so use a different card for each independent end-to-end scenario.
  • The Stripe Services Agreement prohibits testing in live mode with real card details.

Cards by brand

Show all 22 cards

Stripe docs

  • Visa, United States

    SuccessOther 3DS result
    #

    Succeeds. In the 3D Secure table it is the supported but unenrolled card: the customer is never prompted, even when Radar requests 3DS.

  • Visa, Debit

    Success
    #

    Succeeds.

  • Mastercard

    Success
    #

    Succeeds.

  • Mastercard, 2-series

    Success
    #

    Succeeds.

  • Mastercard, Debit

    Success
    #

    Succeeds.

  • Mastercard, Prepaid

    Success
    #

    Succeeds.

  • American Express

    SuccessOther 3DS result
    #

    Succeeds. 3D Secure is not supported: the payment proceeds without authentication.

  • American Express

    Success
    #

    Succeeds.

  • Discover

    Success
    #

    Succeeds.

  • Discover

    Success
    #

    Succeeds.

  • Discover, Debit

    Success
    #

    Succeeds.

  • Diners Club

    Success
    #

    Succeeds.

  • Diners Club, 14-digit card

    Success
    #

    Succeeds.

  • BC Card and DinaCard

    Success
    #

    Succeeds.

  • JCB

    Success
    #

    Succeeds. The issuer is outside the US, so a cross-border fee can apply even in testing.

  • UnionPay

    Success
    #

    Succeeds. The issuer is outside the US, so a cross-border fee can apply even in testing.

  • UnionPay, Debit

    Success
    #

    Succeeds.

  • UnionPay, 19-digit card

    Success
    #

    Succeeds.

  • Cartes Bancaires, Co-branded with Visa

    Success
    #

    Succeeds.

  • Cartes Bancaires, Co-branded with Mastercard

    Success
    #

    Succeeds.

  • eftpos, Co-branded with Visa, Australia, debit

    Success
    #

    Succeeds.

  • eftpos, Co-branded with Mastercard, Australia, debit

    Success
    #

    Succeeds.

Cards by country

Show all 63 cards

Stripe docs

  • Visa, Argentina

    Success
    #

    Succeeds.

  • Visa, Brazil

    Success
    #

    Succeeds.

  • Visa, Canada

    Success
    #

    Succeeds.

  • Visa, Chile

    Success
    #

    Succeeds.

  • Visa, Colombia

    Success
    #

    Succeeds.

  • Visa, Costa Rica

    Success
    #

    Succeeds.

  • Visa, Ecuador

    Success
    #

    Succeeds.

  • Visa, Mexico

    Success
    #

    Succeeds.

  • Carnet, Mexico

    Success
    #

    Succeeds.

  • Visa, Panama

    Success
    #

    Succeeds.

  • Visa, Paraguay

    Success
    #

    Succeeds.

  • Visa, Peru

    Success
    #

    Succeeds.

  • Visa, Uruguay

    Success
    #

    Succeeds.

  • Visa, United Arab Emirates

    Success
    #

    Succeeds without authentication.

  • Mastercard, United Arab Emirates

    Success
    #

    Succeeds without authentication.

  • Visa, Austria

    Success
    #

    Succeeds without authentication.

  • Visa, Belgium

    Success
    #

    Succeeds without authentication.

  • Visa, Bulgaria

    Success
    #

    Succeeds without authentication.

  • Visa, Belarus

    Success
    #

    Succeeds without authentication.

  • Visa, Croatia

    Success
    #

    Succeeds without authentication.

  • Visa, Cyprus

    Success
    #

    Succeeds without authentication.

  • Visa, Czech Republic

    Success
    #

    Succeeds without authentication.

  • Visa, Denmark

    Success
    #

    Succeeds without authentication.

  • Visa, Estonia

    Success
    #

    Succeeds without authentication.

  • Visa, Finland

    Success
    #

    Succeeds without authentication.

  • Visa, France

    Success
    #

    Succeeds without authentication.

  • Visa, Germany

    Success
    #

    Succeeds without authentication.

  • Visa, Gibraltar

    Success
    #

    Succeeds without authentication.

  • Visa, Greece

    Success
    #

    Succeeds without authentication.

  • Visa, Hungary

    Success
    #

    Succeeds without authentication.

  • Visa, Ireland

    Success
    #

    Succeeds without authentication.

  • Visa, Italy

    Success
    #

    Succeeds without authentication.

  • Visa, Latvia

    Success
    #

    Succeeds without authentication.

  • Visa, Liechtenstein

    Success
    #

    Succeeds without authentication.

  • Visa, Lithuania

    Success
    #

    Succeeds without authentication.

  • Visa, Luxembourg

    Success
    #

    Succeeds without authentication.

  • Visa, Malta

    Success
    #

    Succeeds without authentication.

  • Visa, Netherlands

    Success
    #

    Succeeds without authentication.

  • Visa, Norway

    Success
    #

    Succeeds without authentication.

  • Visa, Poland

    Success
    #

    Succeeds without authentication.

  • Visa, Portugal

    Success
    #

    Succeeds without authentication.

  • Visa, Romania

    Success
    #

    Succeeds without authentication.

  • Visa, Saudi Arabia

    Success
    #

    Succeeds without authentication.

  • Visa, Slovenia

    Success
    #

    Succeeds without authentication.

  • Visa, Slovakia

    Success
    #

    Succeeds without authentication.

  • Visa, Spain

    Success
    #

    Succeeds without authentication.

  • Visa, Sweden

    Success
    #

    Succeeds without authentication.

  • Visa, Switzerland

    Success
    #

    Succeeds without authentication.

  • Visa, United Kingdom

    Success
    #

    Succeeds without authentication.

  • Visa, Debit, United Kingdom

    Success
    #

    Succeeds without authentication.

  • Mastercard, United Kingdom

    Success
    #

    Succeeds without authentication.

  • Visa, Australia

    Success
    #

    Succeeds.

  • Visa, China

    Success
    #

    Succeeds.

  • Visa, Hong Kong

    Success
    #

    Succeeds.

  • Visa, India

    Success
    #

    Succeeds.

  • Visa, Japan

    Success
    #

    Succeeds.

  • JCB, Japan

    Success
    #

    Succeeds.

  • Visa, Malaysia

    Success
    #

    Succeeds.

  • Visa, New Zealand

    Success
    #

    Succeeds.

  • Visa, Singapore

    Success
    #

    Succeeds.

  • Visa, Taiwan

    Success
    #

    Succeeds.

  • Visa, Credit, Thailand

    Success
    #

    Succeeds.

  • Visa, Debit, Thailand

    Success
    #

    Succeeds.

HSA and FSA cards

2 cardsStripe docs
  • Visa, FSA or HSA

    Success
    #

    Succeeds as an FSA or HSA card. Stripe lists the same number for both, with separate PaymentMethods: pm_card_debit_visaFsaProductCode and pm_card_debit_visaHsaProductCode.

  • Mastercard, FSA

    Success
    #

    Succeeds as an FSA card.

Declined payments

10 cardsStripe docs
  • Visa

    Generic decline
    #

    Declined: error card_declined, decline code generic_decline.

  • Visa

    Insufficient funds
    #

    Declined: card_declined with decline code insufficient_funds.

  • Visa

    Lost or stolen
    #

    Declined: card_declined with decline code lost_card.

  • Visa

    Lost or stolen
    #

    Declined: card_declined with decline code stolen_card.

  • Visa

    Expired card
    #

    Declined with expired_card.

  • Visa

    Incorrect CVC
    #

    Declined with incorrect_cvc.

    CVC: Any 3 digits, and you must send one

  • Visa

    Processing error
    #

    Declined with processing_error.

  • Visa

    Invalid card details
    #

    Rejected with incorrect_number: the number fails the Luhn check on purpose.

    Fails the Luhn check on purpose.

  • Visa

    Other decline
    #

    Declined: card_declined with decline code card_velocity_exceeded.

  • Visa

    Saves, then charges fail
    #

    Attaching the card to a Customer succeeds, but attempts to charge the customer fail.

Fraud prevention

Show all 15 cards

Stripe docs

  • Visa

    Fraud block or review
    #

    Risk level highest: Radar always blocks it.

  • Visa

    Fraud block or review
    #

    Risk level highest: Radar might block it, depending on your settings.

  • Visa

    Fraud block or review
    #

    Risk level elevated: Radar might queue it for review.

  • Visa

    Fraud block or review
    #

    High fraud dispute score; Radar might block it, depending on your settings.

  • Visa

    Fraud block or review
    #

    High early fraud warning score; Radar might block it, depending on your settings.

  • Visa

    Fraud block or review
    #

    Triggers the Radar Dynamic risk thresholds control, when enabled.

  • Visa

    Fraud block or review
    #

    Triggers the Radar free trial abuse risk control, when enabled.

  • Visa

    Other 3DS resultFraud block or review
    #

    Triggers the Radar Adaptive 3DS risk control, when enabled: Radar requests 3D Secure.

  • Visa

    CVC or address check
    #

    The CVC check fails if you provide a CVC; Radar might block the payment.

    CVC: Any 3 digits, and you must send one

  • Visa

    CVC or address check
    #

    The postal code check fails if you provide a postal code; Radar might block the payment.

    Postal code: Any valid postal code, and you must send one

  • Visa

    CVC or address check
    #

    The CVC check fails with risk level elevated; Radar might block the payment.

    CVC: Any 3 digits, and you must send one

  • Visa

    CVC or address check
    #

    The postal code check fails with risk level elevated; Radar might block the payment.

    Postal code: Any valid postal code, and you must send one

  • Visa

    CVC or address check
    #

    The address line 1 check fails. The payment succeeds unless a custom Radar rule blocks it.

  • Visa

    CVC or address check
    #

    The postal code and address line 1 checks both fail; Radar might block the payment.

  • Visa

    CVC or address check
    #

    The postal code and address line 1 checks are both unavailable. The payment succeeds unless a custom Radar rule blocks it.

Disputes

11 cardsStripe docs
  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then Stripe creates a fraudulent dispute shortly afterward. Stripe recommends it for most dispute tests.

  • Visa

    Dispute or fraud warning
    #

    Payment succeeds and is disputed as fraudulent during the payment request.

  • Discover

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as fraudulent.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as product not received.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as an inquiry.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then receives an early fraud warning.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed multiple times.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as a Visa Compelling Evidence 3.0 eligible dispute.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as a Visa compliance dispute.

  • Mastercard

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as a Mastercard compliance dispute.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds, then is disputed as a Smart Disputes eligible dispute.

Dispute prevention

3 cardsStripe docs
  • Visa

    Dispute or fraud warning
    #

    Charge succeeds; Visa Rapid Dispute Resolution prevents the dispute if the account is enrolled, otherwise a dispute is created.

  • Visa

    Dispute or fraud warning
    #

    Charge succeeds; Compelling Evidence 3.0 blocks the dispute if the account is enrolled in Dispute Deflection, otherwise a dispute is created.

  • Mastercard

    Dispute or fraud warning
    #

    Charge succeeds; Ethoca Alerts prevents the dispute if the account is enrolled, otherwise a dispute is created.

Refunds

2 cardsStripe docs
  • Visa

    Refund behavior
    #

    Charge succeeds. A refund starts pending, then moves to succeeded and sends refund.updated.

  • Visa

    Refund behavior
    #

    Charge succeeds. A refund starts succeeded, then moves to failed and sends refund.failed.

Available balance

2 cardsStripe docs
  • Visa

    Payouts and balance
    #

    The US charge succeeds and the funds go straight to your available balance, bypassing pending.

  • Visa

    Payouts and balance
    #

    The international charge succeeds and the funds go straight to your available balance, bypassing pending.

Authentication and setup

4 cardsStripe docs
  • Visa

    3DS challenge
    #

    Requires authentication for off-session payments unless you set it up for future payments; on-session payments always require authentication.

  • Visa

    3DS challenge
    #

    Requires authentication on every transaction, however the card is set up.

  • Visa

    3DS challenge
    #

    Already set up for off-session use: one-time and other on-session payments require authentication, and off-session payments succeed without it.

  • Visa

    3DS challengeInsufficient funds
    #

    Requires authentication, then every payment declines with insufficient_funds, even after successful authentication or setup.

3D Secure

7 cardsStripe docs
  • Visa, Ireland

    3DS challenge
    #

    3D Secure required: the payment succeeds only after authentication completes. Radar requests 3DS for it by default.

  • Visa, United States

    3DS challenge
    #

    3D Secure required: the payment succeeds only after authentication completes. Radar requests 3DS for it by default.

  • Visa

    3DS challengeGeneric decline
    #

    3D Secure required, then the payment declines with card_declined after authentication.

  • Visa

    Other 3DS result
    #

    3D Secure required, but the lookup fails with a processing error and the payment declines with card_declined.

  • Visa

    Other 3DS result
    #

    3D Secure supported but not required; Radar doesn't request it by default.

  • Visa

    Other 3DS result
    #

    3D Secure supported but not required, and attempting it results in a processing error.

  • Visa

    3DS frictionless
    #

    3D Secure required on every transaction; authentication completes through the frictionless flow and succeeds.

3D Secure mobile challenges

4 cardsStripe docs
  • Visa

    3DS challenge
    #

    Mobile SDK challenge with an out-of-band UI. Behaves like any other card in a browser or the API.

  • Visa

    3DS challenge
    #

    Mobile SDK challenge with a one-time passcode UI. Behaves like any other card in a browser or the API.

  • Visa

    3DS challenge
    #

    Mobile SDK challenge with a single-select UI. Behaves like any other card in a browser or the API.

  • Visa

    3DS challenge
    #

    Mobile SDK challenge with a multi-select UI. Behaves like any other card in a browser or the API.

Captcha

2 cardsStripe docs
  • Visa

    Other
    #

    The charge succeeds if the customer correctly answers the captcha challenge.

  • Visa

    Other
    #

    The charge succeeds if the customer correctly answers the captcha challenge.

Trigger values

Show all 14 values

The expiry and CVC values go in the card form with any test card. The evidence strings go in a dispute's evidence after a dispute card creates one. The Terminal amounts apply to the physical test card on a Terminal reader: use the cents in the payment's amount.

  • Expiry month

    Invalid card details#

    Any invalid month fails with invalid_expiry_month.

  • Expiry year

    Invalid card details#

    A year up to 50 years in the past fails with invalid_expiry_year.

  • CVC

    Invalid card details#

    A two-digit CVC fails with invalid_cvc.

  • Dispute evidence

    Dispute or fraud warning#

    Closes the dispute as won and credits the charge amount and related fees.

  • Dispute evidence

    Dispute or fraud warning#

    Closes the dispute as lost without a credit; for inquiries, closes the inquiry without escalation.

  • Dispute evidence

    Dispute or fraud warning#

    Escalates the inquiry to a chargeback and debits the dispute amount and fees.

  • Terminal amount

    Success#

    With the physical test card on a Terminal reader in a sandbox, an amount ending in .00 is approved.

  • Terminal amount

    Generic decline#

    With the physical test card on a Terminal reader in a sandbox, an amount ending in .01 is declined with call_issuer.

  • Terminal amount

    Other#

    On a reader with a cardholder-facing screen, insert or tap the card. If the card requires a PIN, the payment declines with offline_pin_required and requests PIN entry. Enter 1234 to complete it.

  • Terminal amount

    Other#

    On a reader with a cardholder-facing screen, insert or tap the card. If the card requires a PIN, the payment declines with online_or_offline_pin_required and requests PIN entry. Enter any four digits to complete it.

  • Terminal amount

    Generic decline#

    Declined with generic_decline.

  • Terminal amount

    Other decline#

    Declined with incorrect_pin.

  • Terminal amount

    Other decline#

    Declined with withdrawal_count_limit_exceeded.

  • Terminal amount

    Other decline#

    Declined with pin_try_exceeded.

Not in Stripe's docs

  • A card number for the fraudulent decline code; only the token tok_visa_chargeDeclinedFraudulent produces it.
  • Triggers based on cardholder name. Amount triggers exist only for Terminal's physical test card.

The same tests on Flint

Flint runs on Stripe test mode, so you test with the same numbers and no Stripe account of your own. A declined card leaves the order open with its balance due, so the buyer retries in the same checkout, and POST /v1/disputes/{dispute_id}/simulate rules on a test dispute as won or lost when you call it.

Flint test cards#

16 cards, 5 triggers

One rule for every card: any future expiry, any 3-digit CVC, any ZIP. Flint processes cards on Stripe, so every Stripe test card also works in a Flint sandbox, with no Stripe account to set up.

Expiry
Any future date
CVC
Any 3 digits
Postal code
Any ZIP code, such as 44444
  • The sandbox is free and needs no credit card. Every test key is bound to its own sandbox, and test and live traffic share one host: the key prefix decides the mode.
  • A decline never ends a checkout session. The buyer sees the failure inline and retries, and the order keeps its outstanding balance until a payment succeeds.
  • From a test suite, pay an order with a test token such as pm_card_visa instead of a card number; a declined token still returns 200 with the attempt failed.

Test cards

9 cardsFlint guide
  • Visa

    Success
    #

    Payment succeeds and the order becomes paid. Use it for card setup and renewals that succeed.

  • Visa

    3DS challenge3DS fails
    #

    Checkout opens a 3D Secure challenge. Complete it and the payment succeeds; fail it and the payment declines. The pay API returns requires_action until the browser finishes the challenge.

  • Visa

    3DS challenge3DS fails
    #

    3D Secure challenge. Complete it and resume, and the attempt succeeds; fail it and resume, and the attempt ends failed with authentication_required.

  • Visa

    Insufficient funds
    #

    Declined with insufficient_funds. Checkout shows the failure and the buyer can retry; the order stays open and unpaid.

  • Visa

    Generic decline
    #

    Declined with card_declined. The order stays open, and the buyer can retry in place.

  • Visa

    Expired card
    #

    Declined with expired_card. The order stays open.

  • Visa

    Incorrect CVC
    #

    Declined with incorrect_cvc. The order stays open.

  • Visa

    Processing error
    #

    Fails with processing_error. The order stays open.

  • Visa

    Saves, then charges fail
    #

    Saves to a customer, then every charge fails: point a subscription at it and the next renewal sends subscription.past_due. Subscribing with it from the start fails the first payment, which moves the subscription from incomplete to past_due.

Lost and stolen cards

2 cardsFlint guide
  • Visa

    Lost or stolen
    #

    The attempt ends failed with lost_card.

  • Visa

    Lost or stolen
    #

    The attempt ends failed with stolen_card.

Risk and fraud

3 cardsFlint guide
  • Visa

    Fraud block or review
    #

    Elevated risk: Flint's default rule opens a review, except on invoice and subscription renewal payments.

  • Visa

    Fraud block or review
    #

    Highest risk, blocked by the card processor's fraud screening. The attempt fails with payment_blocked.

  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then receives an early fraud warning.

Disputes

2 cardsFlint guide
  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then is disputed as fraudulent and waits in needs_response. Rule on it with POST /v1/disputes/{dispute_id}/simulate.

  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then is disputed as an inquiry and waits in inquiry_needs_response. Rule on it with POST /v1/disputes/{dispute_id}/simulate.

Test tokens

5 values

Pass one as payment_source.stripe.payment_method, with credential_type: stripe_payment_method, to pay an order from code with no card form. The reader outcomes go in the body of POST /v1/readers/{reader_id}/simulate, and the amounts apply to a payment presented on a physical reader. See the in-person payments guide.

  • Payment token

    Success#

    The payment succeeds and the order becomes paid.

  • Payment token

    Generic decline#

    The attempt fails with last_payment_error.code of card_declined.

  • Payment token

    Insufficient funds#

    The attempt fails with insufficient_funds.

  • Payment token

    3DS challenge#

    The attempt stops at requires_action with a 3D Secure step for the browser to complete.

  • Payment token

    3DS challenge#

    The attempt stops at requires_action, using 3D Secure 2.

Sources

Every Stripe number and outcome comes from Stripe's own docs, read on November 11, 2026. Each card group links to the page that lists it.

Test cards for other processors: Adyen, PayPal, Braintree, Authorize.net, Square, Checkout.com, Worldpay, Cybersource, NMI.