Card testing is the practice of pushing stolen card numbers through a live payment form in small increments to learn which ones still authorize. On Square and other processors it appears as bursts of low-value, high-volume charges with mismatched billing data and repeated declines. The only legitimate way to verify a payment integration is inside a provider's sandbox using published test card numbers, never against a live production account with real card data.

more on this topic

What does "longtail" mean in a card-testing attack?

The longtail pattern spreads attempts across hundreds of cards at tiny amounts instead of hammering one card with a large charge. Each attempt costs the attacker cents, and a single hit pays for the whole run. Because individual tickets look harmless, longtail runs often hide inside normal order volume until decline rates spike.

Related Square Test CVV vs Real Card Numbers: A Comprehensive Comparison

How are payment integrations supposed to be tested?

Every major processor publishes a sandbox with fixed test card numbers, expiration dates, and CVV values that never touch the card networks. Square, Stripe, and Adyen all document these fixtures in their developer portals, along with simulated decline and CVV-mismatch responses. Testing there proves your checkout handles approvals, soft declines, and hard declines without generating a single real authorization.

read more

Why does CVV verification not stop card testing on its own?

CVV checks confirm that the three-digit code matches what the issuer has on file at the moment of authorization. Attackers who hold full card data, including the CVV, pass that check cleanly. Fraud tooling therefore layers velocity limits, device fingerprinting, and address verification on top of CVV rather than treating it as a standalone gate.

question how to use square test cvv for testing?

What signals do processors use to flag card testing?

  • Many distinct card numbers hitting one merchant account in a short window
  • Clusters of identical ticket amounts, often under a few dollars
  • Repeated authorization attempts from a single IP range or device
  • Billing country, IP country, and card BIN country that do not line up
  • Decline-rate jumps well above the account's normal baseline

How does card testing hurt a merchant?

Excessive declines and chargebacks push an account toward monitoring programs, and card networks can levy fees for excessive fraud volume. Processors may freeze payouts or raise reserves while they review the activity. The damage lands on the merchant even though the stolen cards belong to someone else.

What should a merchant do when an attack starts?

  1. Enable velocity rules that cap attempts per card, per IP, and per device.
  2. Require CVV and address verification on every card-not-present order.
  3. Add a CAPTCHA or bot check to the checkout form.
  4. Block or challenge traffic from hosting providers and known proxy ranges.
  5. Contact the processor's risk team early so the account is flagged as a victim, not a source.

Is buying or selling card data ever legitimate?

No. Payment card credentials belong to the cardholder and the issuing bank, and trading them is a crime in the US and most other jurisdictions. Merchants who discover a card-testing run should preserve logs and report it to their acquirer and to law enforcement.