Card Testing
- Card testing (carding) means attempts to validate stolen or guessed card details, through small charges or card setup
- Possible targets: low-friction payment and card-setup pages
- Detect via: multiple small amounts same IP, sequential card numbers, high decline rates
- Prevent with velocity rules, CAPTCHA, minimum amounts, 3D Secure
- What it can cost: per-attempt fees if your contract bills them, processor reviews, Visa's enumeration program at high volumes, and disputes on test charges that succeed
A sudden burst of small charges, with lots of declines? That's probably card testing (or carding): fraudsters trying stolen or guessed card details to find out which still work. Small charges are one way. Saving a card is another. Turn on CAPTCHA and tighten your velocity rules now (response playbook), then add the longer-term controls.
How Card Testing Works
Common Testing Targets
| Possible Target | Why It Can Attract Testing |
|---|---|
| Donation pages | Low friction. Check your own AVS settings |
| Subscription services | Small amounts, and cards saved without a large first charge |
| Digital goods | Instant delivery, no shipping address to check |
| Low-friction checkouts | Few checks before the card is tried. Compare your fraud detection with your traffic |
| Card setup and account funding | A card can be tested by saving it, with no purchase |
Detection Signals
These are illustrative priorities. Test them against your legitimate traffic. Round amounts, shared IPs and shared addresses alone don't confirm testing (Stripe's guide).
Transaction-Level
| Signal | Priority to Check |
|---|---|
| Multiple small amounts, same IP | First |
| Sequential card numbers | First |
| High decline rate from same device | First |
| Round dollar amounts ($1, $2, $5) | Next |
| Multiple cards, same shipping address | First |
Velocity Patterns
Illustrative thresholds below, to run in shadow mode first: the rule records what it would block and lets the payments through. Choose counts and windows from your own retries, shared-IP traffic and observed attacks. Test legitimate traffic before enforcing.
| Pattern | Threshold Example |
|---|---|
| Transactions per IP per hour | >10 |
| Unique cards per IP per hour | >5 |
| Declines per IP per hour | >3 |
| Transactions per device per hour | >10 |
Impact Beyond Direct Loss
The test transactions aren't the expensive part. Here's what else it costs you:
- Authorization fees: If your contract charges per authorization attempt, every decline from the test adds a fee too (how auth and capture work)
- Processor attention: High decline rates can trigger a review
- Program trouble: Visa's VAMP has its own test for card testing, which it calls enumeration (thresholds). A fraud report the card's bank files on an approved test charge can also count toward VAMP's ratio, though not your chargeback ratio
- System load: Bot traffic strains infrastructure
- Chargebacks on your test charges: A test charge that succeeded on your checkout can itself be reported as fraud or disputed. Later fraud on that card gets disputed against whoever processed it (Stripe on the consequences, how chargebacks work)
Prevention Strategies
Technical Controls
- CAPTCHA: On payment pages, especially donations
- Rate limiting: By IP, device, session
- Velocity rules: Block on pattern detection (how to tune them)
- BIN-level blocking: Ranges your own attacks came from
- Device fingerprinting: Identify repeat offenders (what it reads)
Transaction Rules
- Minimum amount: Test an amount against legitimate small purchases or donations and attack behavior; no single dollar cutoff stops card testing
- AVS requirement: Address verification
- CVV requirement: Harder for card list fraud
- 3D Secure: Eligible sales can shift fraud liability. It adds a shopper step only when the bank asks for a challenge
Monitoring
- Real-time dashboards: Spot attacks quickly
- Decline spike alerts: Abnormal decline rates
- IP reputation feeds: Known bad actors
Response Playbook
When you're under attack:
- Immediate: Enable CAPTCHA, tighten velocity rules
- Short-term: Block offending IPs/devices
- Analysis: Find the hole they're using
- Long-term: Implement permanent controls
Next Steps
Under card testing attack now?
- Follow response playbook: Immediate actions
- Enable CAPTCHA: Add friction
- Tighten velocity rules: Block patterns
Preventing card testing?
- Implement velocity limits: Set thresholds
- Add device fingerprinting: Track offenders
- Require CVV/AVS: Verification signals
Measuring card testing impact?
- Track authorization fees: Know your costs
- Monitor decline rates: Spot attacks early
- Check fraud metrics: Network ratio impact
Related Topics
- Prevent Fraud: The fraud hub
- Third-Party Fraud: Fraud using stolen credentials
- Velocity Rules: Primary defense against card testing
- Data Enrichment: Datacenter IP and bot detection signals
- Device Fingerprinting: Track repeat offenders
- AVS & CVV: Verification signals
- 3D Secure: Authentication and liability shift on eligible fraud disputes
- Decline Codes: Understanding test failures
- Network Programs: Fraud ratio thresholds
- Fraud Metrics: Measuring card testing impact
- Survive Fraud Attack: Attack response playbook
- Processor Rules Configuration: Setting up blocking rules
- Account Takeover: Related attack pattern
- Risk Scoring: Combining signals