Skip to content

Square test cards

Every card number in Square's sandbox payments docs, with the CVV, postal code, expiry, and amount values that force errors and disputes, and the SCA cards for the Web and In-App Payments SDKs.
Verified against official documentationReviewed Send a correction (opens in a new tab)

Square test cards by scenario

Fixed success cards plus magic CVV, postal code, expiry, and amount values. One card declines generically; there is no card per decline reason. Where a cell names a trigger, use it with any of Square's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.

ScenarioSquareFlint
Successful payment4111 1111 1111 1111CVV 1114242 4242 4242 4242any future expiry, any CVC, any ZIP
Generic decline4000 0000 0000 00024000 0000 0000 0002
Insufficient fundsNot documented for cards4000 0000 0000 9995
Lost or stolen cardNot documented4000 0000 0000 99874000 0000 0000 9979lost, stolen
Expired cardExpiry 01/40 (expiration date incorrect)4000 0000 0000 0069
Incorrect CVCCVV 9114000 0000 0000 0127
3D Secure challenge4310 0000 0020 1019code 1234564000 0025 0000 3155
3D Secure authentication fails4811 1100 0000 00084000 0000 0000 3220fail the challenge
Card saves, then charges failNot documented4000 0000 0000 0341
Dispute or chargebackAmount 8801 to 88094000 0000 0000 02594000 0000 0000 1976fraudulent, inquiry

Declines, 3D Secure, and disputes

How Square triggers declines

Square has success cards and one generic decline card, 4000 0000 0000 0002. Other errors come from the card details: CVV 911 for an incorrect CVV, postal code 99999 for an incorrect postal code, and expiry 01/40 for an incorrect expiration date. The success cards need CVV 111.

How Square tests 3D Secure

In the sandbox, verifyBuyer creates a buyer challenge in every region, and the SMS verification code is 123456. The SCA cards for the Web Payments SDK and In-App Payments SDK each simulate one challenge result.

How Square simulates disputes

Disputes come from the amount: a payment of 8801 to 8809 creates a dispute with a reason for each amount, visible through the API only. Upload an evidence file named evidence_won or evidence_lost, then submit evidence, to win or lose it.

Look up a Square 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.

31 cards and 22 trigger values from Square

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 Square test card#

31 cards, 22 triggers

Fixed success cards plus magic CVV, postal code, expiry, and amount values. One card declines generically; there is no card per decline reason.

Expiry
Any future month and year
CVC
111; 1111 for American Express
Postal code
A valid postal code for USD, CAD, and GBP payments
  • The sandbox doesn't accept real cards. Enter test numbers in the Web Payments SDK or In-App Payments SDK, which tokenize them, or pass a test source_id such as cnon:card-nonce-ok to CreatePayment.
  • In the sandbox, verifyBuyer creates a buyer challenge in every region. The SMS verification code is 123456.
  • Creating a card on file with CreateCard from a test token requires postal code 94103 in the billing address.
  • Card-present payments can't be tested in the sandbox.

Success cards

8 cardsSquare docs
  • Visa

    Success
    #

    Success.

  • Mastercard

    Success
    #

    Success.

  • Discover

    Success
    #

    Success.

  • Diners Club

    Success
    #

    Success.

  • JCB

    Success
    #

    Success.

  • American Express

    Success
    #

    Success.

  • UnionPay

    Success
    #

    Success.

    CVC: 123

    Fails the Luhn check, though Square lists it as a working card, so a client-side Luhn check rejects it first.

  • Square gift card

    Success
    #

    Success.

    CVC: None

Error cards

2 cardsSquare docs
  • Brand not stated

    Generic decline
    #

    Card declined: the payment token errors at CreatePayment.

  • Brand not stated

    Save or verification fails
    #

    Card-on-file authorization declined.

SCA, Web Payments SDK

10 cardsSquare docs
  • Visa

    3DS frictionless
    #

    Web Payments SDK: No challenge.

  • Mastercard

    3DS frictionless
    #

    Web Payments SDK: No challenge.

  • Discover, EU

    3DS frictionless
    #

    Web Payments SDK: No challenge.

  • JCB

    3DS frictionless
    #

    Web Payments SDK: No challenge. JCB SCA testing works for sellers in AU, CA, and JP only.

  • Visa, EU

    3DS challenge
    #

    Web Payments SDK: Modal with verification code 123456.

  • Mastercard

    3DS challenge
    #

    Web Payments SDK: Modal with verification code 123456.

  • Mastercard, EU

    3DS challenge
    #

    Web Payments SDK: Modal with verification code 123456.

  • American Express, EU

    3DS challenge
    #

    Web Payments SDK: Modal with verification code 123456.

  • JCB

    3DS challenge
    #

    Web Payments SDK: Modal with verification code 123456. JCB SCA testing works for sellers in AU, CA, and JP only.

  • Visa

    3DS fails
    #

    Web Payments SDK: Failed verification without a challenge.

SCA, In-App Payments SDK

11 cardsSquare docs
  • Visa

    3DS frictionless
    #

    In-App Payments SDK: No challenge.

  • Mastercard

    3DS frictionless
    #

    In-App Payments SDK: No challenge.

  • Discover, EU

    3DS frictionless
    #

    In-App Payments SDK: No challenge.

  • JCB

    3DS frictionless
    #

    In-App Payments SDK: No challenge.

  • Visa, EU

    3DS challenge
    #

    In-App Payments SDK: Modal with verification code 123456.

  • Mastercard

    3DS challenge
    #

    In-App Payments SDK: Modal with verification code 123456.

  • Mastercard, EU

    3DS challenge
    #

    In-App Payments SDK: Modal with verification code 123456.

  • American Express, EU

    3DS challenge
    #

    In-App Payments SDK: Modal with verification code 123456.

  • JCB

    3DS challenge
    #

    In-App Payments SDK: Modal with verification code 123456.

    CVC: 1111 (as documented)

  • Mastercard

    3DS challenge
    #

    In-App Payments SDK: Modal with a multi-select challenge question: select both Paris and Lyon.

  • Visa

    3DS fails
    #

    In-App Payments SDK: Failed verification without a challenge.

Trigger values

Show all 22 values

CVV, postal code, and expiry values go in the card form. Amounts go on CreatePayment, evidence file names on a dispute, and source_id values replace the card entirely.

  • CVV

    Incorrect CVC#

    Card CVV incorrect.

  • Postal code

    CVC or address check#

    Card postal code incorrect.

  • Expiry

    Expired card#

    Card expiration date incorrect.

  • Amount

    Fraud block or review#

    Risk level MODERATE.

  • Amount

    Fraud block or review#

    Risk level HIGH.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason AMOUNT_DIFFERS, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason CANCELLED, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason DUPLICATE, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason NO_KNOWLEDGE, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason NOT_AS_DESCRIBED, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason NOT_RECEIVED, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason PAID_BY_OTHER_MEANS, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason CUSTOMER_REQUESTS_CREDIT, visible through the API only.

  • Amount

    Dispute or fraud warning#

    Creates a dispute with reason EMV_LIABILITY_SHIFT, visible through the API only.

  • Evidence file name

    Dispute or fraud warning#

    Uploading the file, then submitting evidence, sets the dispute to WON.

  • Evidence file name

    Dispute or fraud warning#

    Uploading the file, then submitting evidence, sets the dispute to LOST.

  • source_id

    Success#

    A credit or debit card payment succeeds.

  • source_id

    Generic decline#

    Card declined.

  • source_id

    Incorrect CVC#

    Bad CVV.

  • source_id

    CVC or address check#

    Bad postal code.

  • source_id

    Expired card#

    Bad expiration date.

  • source_id

    Insufficient funds#

    Gift card insufficient funds.

Not in Square's docs

  • Insufficient funds, lost or stolen, or expired-card declines for card numbers.
  • A dispute card: disputes come from the amount.
  • The exact error codes the error-state values return.

The same tests on Flint

On Flint, insufficient funds, expired cards, and lost or stolen cards each have their own card number, which Square doesn't document, and any 3-digit CVC works. Dispute cards open the dispute at any amount, and POST /v1/disputes/{dispute_id}/simulate rules on 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 Square number and outcome comes from Square's own docs, read on November 11, 2026. Each card group links to the page that lists it.

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