A Square test card is a fake card number that the Square sandbox accepts so developers can run payments without moving real money. You type it into a test checkout the same way a shopper would, and Square returns a simulated approval or decline. Test cards work only in sandbox mode and are rejected by live Square accounts.

What is a Square test card?

Square runs two environments: production for real payments and sandbox for building and testing. A test card belongs to the sandbox. It looks like a normal 16-digit card number but maps to a scripted result inside Square's system.

Each card carries a preset outcome. One approves, another declines, another triggers a specific error so you can see how your checkout reacts. The card number, CVV, expiration date, and postal code all matter in sandbox.

Where can you find Square test card numbers?

Square publishes its current list in the developer documentation under test values or sandbox test cards. Use that page as your source. Card lists change when Square updates its sandbox, so a number copied from an old blog post may fail.

• Square Developer Docs: the official list of test card numbers with matching CVV, expiry, and postal codes.
• Your Square dashboard: sandbox credentials and API keys sit next to the test data you need.
• Square support: useful when a documented test card returns an unexpected result.

How do you use a Square test card?

1. Create a Square developer account and open a sandbox application.
2. Copy the sandbox application ID and access token into your test configuration.
3. Open the test values page and pick the card that matches the scenario you want.
4. Enter the number, CVV, expiration date, and postal code in your checkout form.
5. Submit the payment and read the response object for the status and error codes.

The expiration date on a test card must be in the future. Square's docs name the exact date for each card, so follow the table instead of guessing.

Which test cards does Square provide?

The list covers a handful of scenarios. Numbers live in the docs, but the categories stay consistent.

• Successful Visa payment: the standard approval card, often in the 4111 range.
• Successful Mastercard payment: the same approval flow on a second network.
• Declined card: returns a generic decline so you can test your error message.
• CVV failure: passes the card number and fails on the security code.
• Expired card: tests how your form handles a past expiration date.

Do not assume a number works because it appears on a forum. Check it against the current Square docs before you build automated tests around it.

Do Square test cards charge real money?

No. Sandbox transactions never touch a bank or a card network. You can run the same test card hundreds of times and no money moves.

That also means test cards cannot prove a live account can process payments. Switch to production credentials and a real card when you are ready to confirm live billing.

What else can you test with sandbox data?

Test cards cover the card entry step, and Square's sandbox goes further. You can build a full payment flow and watch each stage return a response.

• Refunds and partial refunds against a sandbox payment.
• Invoices and payment links that expire on a schedule you set.
• Webhook events for payment creation, refund, and dispute.
• Stored card behavior for repeat customers.

Testing these paths while you are still in sandbox saves a debugging session later, when the stakes include real customer money.

Why does a Square test card fail?

Five problems cause most failures.

• You are in production mode, where sandbox cards are declined on purpose.
• The expiration date is in the past.
• The CVV or postal code does not match the value listed for that card.
• Your application uses a live access token instead of a sandbox token.
• Square changed its sandbox values and your saved test data is out of date.

Test cards and real card data: what to keep separate

Test cards exist for software testing. Real card numbers belong to the people who own them, and using someone else's card data without permission is fraud under US law.

Store test values in your test environment only. Never place live card numbers in logs, spreadsheets, or code comments. PCI DSS rules apply to any system that stores, processes, or transmits real card data, and Square's own guidance covers how to stay compliant.

If you need card data for testing, use the sandbox list. There is no honest reason to buy card numbers for development work, and sites that sell them deal in stolen data.

FAQ

Is 4111 1111 1111 1111 a Square test card?

That number is a common Visa test value across payment processors, and Square's docs include a Visa card in that family. Confirm the exact string and its matching CVV, expiry, and postal code on Square's test values page before use.

Can I use a Square test card on a live site?

No. Live Square accounts reject sandbox card numbers. The card declines and the attempt may show up in your logs.

Do I need a Square account to get test cards?

You need a Square developer account to reach sandbox credentials and the test values page. The account itself is free.

What CVV do Square test cards use?

Square lists a specific CVV for each test card. The value is often three digits, but read the table because some cards use a different code to trigger a CVV failure.