# Card Testing
Source: https://paymentsandrisk.com/docs/fraud/types/card-testing

Last updated 4 November 2026.

TL;DR

-   **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](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/), CAPTCHA, minimum amounts, [3D Secure](https://paymentsandrisk.com/docs/fraud/prevention/3ds/)
-   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](https://paymentsandrisk.com/docs/fraud/types/card-testing/#response-playbook)), then add the [longer-term controls](https://paymentsandrisk.com/docs/fraud/types/card-testing/#prevention-strategies).

## How Card Testing Works

```mermaid
flowchart TD
    A[1. Fraudster obtains or guesses card details\nbreach, purchase, skimming, enumeration] --> B[2. Tests them\nsmall charges or card setup]
    B --> C[3. Valid cards separated from invalid]
    C --> D[4. Valid cards used for larger fraud]
    C --> E[5. Valid cards resold at premium]
```

## Common Testing Targets

| Possible Target | Why It Can Attract Testing |
| --- | --- |
| Donation pages | Low friction. Check your own [AVS](https://paymentsandrisk.com/docs/fraud/prevention/avs-cvv/) settings |
| [Subscription](https://paymentsandrisk.com/docs/payments/subscriptions-recurring/) 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](https://paymentsandrisk.com/docs/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](https://docs.stripe.com/disputes/prevention/card-testing)).

### 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:

1.  **Authorization fees**: If your contract charges per authorization attempt, every [decline](https://paymentsandrisk.com/docs/reference/decline-codes/) from the test adds a fee too ([how auth and capture work](https://paymentsandrisk.com/docs/payments/auth-and-capture/))
2.  **[Processor](https://paymentsandrisk.com/docs/operations/processor-management/) attention**: High decline rates can trigger a review
3.  **Program trouble**: Visa's VAMP has its own test for card testing, which it calls enumeration ([thresholds](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/)). 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
4.  **System load**: Bot traffic strains infrastructure
5.  **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](https://docs.stripe.com/disputes/prevention/card-testing#card-testing-consequences), [how chargebacks work](https://paymentsandrisk.com/docs/chargebacks/))

## Prevention Strategies

### Technical Controls

1.  **CAPTCHA**: On payment pages, especially donations
2.  **Rate limiting**: By IP, [device](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/), session
3.  **Velocity rules**: Block on pattern detection ([how to tune them](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/))
4.  **BIN\-level blocking**: Ranges your own attacks came from
5.  **Device fingerprinting**: Identify repeat offenders ([what it reads](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/))

### Transaction Rules

1.  **Minimum amount**: Test an amount against legitimate small purchases or donations and attack behavior; no single dollar cutoff stops card testing
2.  **[AVS](https://paymentsandrisk.com/docs/fraud/prevention/avs-cvv/) requirement**: Address verification
3.  **[CVV](https://paymentsandrisk.com/docs/fraud/prevention/avs-cvv/) requirement**: Harder for card list fraud
4.  **[3D Secure](https://paymentsandrisk.com/docs/fraud/prevention/3ds/)**: Eligible sales can shift fraud liability. It adds a shopper step only when the bank asks for a challenge

### Monitoring

1.  **Real-time dashboards**: Spot attacks quickly
2.  **Decline spike alerts**: Abnormal decline rates
3.  **IP reputation feeds**: Known bad actors

## Response Playbook

When you're under attack:

1.  **Immediate:** Enable CAPTCHA, tighten velocity rules
2.  **Short-term:** Block offending IPs/devices
3.  **Analysis:** Find the hole they're using
4.  **Long-term:** Implement permanent controls

## Next Steps

**Under card testing attack now?**

1.  [Follow response playbook](https://paymentsandrisk.com/docs/fraud/types/card-testing/#response-playbook): Immediate actions
2.  [Enable CAPTCHA](https://paymentsandrisk.com/docs/fraud/types/card-testing/#technical-controls): Add friction
3.  [Tighten velocity rules](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/): Block patterns

**Preventing card testing?**

1.  [Implement velocity limits](https://paymentsandrisk.com/docs/fraud/types/card-testing/#velocity-patterns): Set thresholds
2.  [Add device fingerprinting](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/): Track offenders
3.  [Require CVV/AVS](https://paymentsandrisk.com/docs/fraud/prevention/avs-cvv/): Verification signals

**Measuring card testing impact?**

1.  [Track authorization fees](https://paymentsandrisk.com/docs/fraud/types/card-testing/#impact-beyond-direct-loss): Know your costs
2.  [Monitor decline rates](https://paymentsandrisk.com/docs/reference/decline-codes/): Spot attacks early
3.  [Check fraud metrics](https://paymentsandrisk.com/docs/fraud/metrics/): Network ratio impact

* * *

## Related Topics

-   [Prevent Fraud](https://paymentsandrisk.com/docs/fraud/): The fraud hub
-   [Third-Party Fraud](https://paymentsandrisk.com/docs/fraud/types/third-party/): Fraud using stolen credentials
-   [Velocity Rules](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/): Primary defense against card testing
-   [Data Enrichment](https://paymentsandrisk.com/docs/fraud/detection/data-enrichment/): Datacenter IP and bot detection signals
-   [Device Fingerprinting](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/): Track repeat offenders
-   [AVS & CVV](https://paymentsandrisk.com/docs/fraud/prevention/avs-cvv/): Verification signals
-   [3D Secure](https://paymentsandrisk.com/docs/fraud/prevention/3ds/): Authentication and liability shift on eligible fraud disputes
-   [Decline Codes](https://paymentsandrisk.com/docs/reference/decline-codes/): Understanding test failures
-   [Network Programs](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/): Fraud ratio thresholds
-   [Fraud Metrics](https://paymentsandrisk.com/docs/fraud/metrics/): Measuring card testing impact
-   [Survive Fraud Attack](https://paymentsandrisk.com/docs/playbooks/survive-fraud-attack/): Attack response playbook
-   [Processor Rules Configuration](https://paymentsandrisk.com/docs/fraud/processor-rules-configuration/): Setting up blocking rules
-   [Account Takeover](https://paymentsandrisk.com/docs/fraud/types/account-takeover/): Related attack pattern
-   [Risk Scoring](https://paymentsandrisk.com/docs/fraud/prevention/risk-scoring/): Combining signals
