Request declined: CVV sales buying guide
I can’t write a buying guide for selling CVV data or card verification utilities used to support payment card fraud.
Square Card Test: How to Test Card Payments Safely
A Square card test is a payment run in Square's sandbox environment using Square's published test card numbers, which lets you verify that charges, declines, refunds, and error handling behave correctly without moving real money. Test card numbers only work in sandbox mode. A live Square account will reject them, and your own live card should never be used for repeated testing.
Request declined: CVV sales buying guide
What a Square card test actually checks
Testing is not only about whether a payment goes through. A complete sandbox pass confirms the full path your code takes from the moment a card is entered to the moment your system records the result.
- Tokenization: the card number converts into a payment token your server can use.
- Authorization: the payment is approved and a payment ID comes back.
- Capture and settlement logic: your order status updates at the right step.
- Declines: a rejected card triggers the correct error message and does not create an order.
- Refunds and voids: money-flow logic reverses cleanly in your database and dashboard.
- Webhooks: your endpoint receives and verifies event notifications.
- Idempotency: a retried request does not create a duplicate charge.
Sandbox test cards versus live cards
Square publishes a set of test card numbers for each major brand, along with example expiration dates and security codes. These numbers are designed to pass validation checks, so you can exercise your form and API code the same way a customer would.
Two limits matter. First, test numbers are tied to the sandbox. Second, test results do not predict real-world outcomes such as issuer rules, 3D Secure prompts, network outages, or disputes. Treat sandbox results as proof that your code works, not as proof that a real payment will succeed.
Because the published list changes over time, pull the current numbers from Square's official developer documentation rather than copying them from a blog post or forum thread.
How to run a test step by step
- Create a Square developer account and a sandbox application, then copy the sandbox access token and location ID.
- Point your integration at the sandbox base URL instead of the production one.
- Add a clearly labeled test mode flag in your config so production keys cannot be used in a test run.
- Submit a published test card number with a future expiration date and the example security code.
- Confirm the response object, then check that your order, email, and inventory logic reacted as expected.
- Repeat with each card brand you plan to accept, including American Express if you support it.
- Trigger failure paths deliberately, such as an invalid expiration date, a missing security code, and a card your sandbox is configured to decline.
- Run a refund on an approved test payment and verify the dashboard and webhook both update.
- Log the test IDs so a later code change can be compared against a known good run.
Common mistakes during testing
- Using live credentials with test card numbers, which produces confusing errors.
- Testing only the success case and never the decline path.
- Hard-coding a test card number into a checkout form that ships to production.
- Ignoring webhook signature verification until launch week.
- Assuming a sandbox approval means the integration is certified for live traffic.
Card testing as an attack, and how to stop it
Attackers sometimes use small charges to check whether stolen card numbers are active. That activity looks similar to ordinary testing on your end, but it comes from strangers and it costs you fees and chargebacks. Square merchants should watch for bursts of small declined payments from the same IP range or device fingerprint.
Practical defenses include rate limiting on the payment endpoint, CAPTCHA on high-risk forms, address verification and security code checks, blocking repeat attempts after several failures, and alerting on unusual approval-to-decline ratios. Card data handling should follow PCI DSS requirements, which means never storing full card numbers or security codes on your own servers. Using a hosted payment form or tokenization keeps that data inside the processor's environment.
Short answers to common questions
Do test card numbers work in a live Square account?
No. They are sandbox values. Live accounts need real cards from real cardholders, or a supported alternative payment method.
Can I reuse the same test card?
Yes. Sandbox test numbers can be used as often as you need, which is exactly why they are useful for automated test suites.
Does a passing test mean my checkout is secure?
No. It means your payment flow works. Security depends on how you handle tokens, keys, and cardholder data, and on the fraud controls you put in front of the form.