Card Testing Fraud: How Attacks Work and How to Limit Damage

Card Testing Fraud How Attacks Work and How to Limit Damage

Here is an example of how it often starts. A finance lead reviewing the company card sees a $1.00 donation to a charity site nobody has heard of. Two days later there is a $2.49 charge at an online game store. Nobody flags either one, because they are too small to matter. The following week, the same card pays for $640 of electronics.

The small charges were not mistakes. They were tests. Card testing fraud is how criminals find out which stolen card numbers still work before they spend them. This guide explains how the attack works, what the warning signs look like for cardholders and merchants, which controls stop which stage, and how separate virtual cards limit the damage when a test succeeds.

What card testing fraud is

Card testing is the step between stealing card data and using it. Fraudsters often hold large batches of card details and do not know which are still active. They run small payments or card verifications to sort live cards from dead ones, then either spend the live cards or sell them as verified. Stripe’s documentation on card testing lists other names for the same activity, including carding, account testing, enumeration and card checking.

How a card testing attack works

Stage 1: getting card data

Card details come from merchant breaches, phishing pages, malware on checkout pages and skimming. In an enumeration attack, also called a BIN attack, fraudsters skip theft entirely and generate plausible card numbers within a known card number range, then guess the expiry date and security code.

Stage 2: running the tests

Automated scripts send many attempts through a merchant’s checkout, often one with weak protections. Two methods are common. Small payments are used because cardholders tend to ignore them. Card setup flows, where a merchant saves or verifies a card without charging it, are popular because, as Stripe notes, these verifications do not usually show up on cardholder statements.

Stage 3: sorting the results

Each approval or decline tells the fraudster something. Approved cards go on a “valid” list. Declines are discarded.

Stage 4: cashing out

Valid cards are used for larger purchases, often of goods that are easy to resell, or sold on to other criminals at a higher price because they are confirmed to work.

Warning signs

For cardholders

  • Small charges, often under a few dollars, from merchants you do not recognize.
  • Donations to charities you did not choose. Donation pages are a common testing ground.
  • Authorization alerts or declines you did not trigger.
  • Several small charges on the same day from unrelated merchants.

For merchants

  • A sudden spike in failed or declined payments.
  • Many low-value payments with nonsensical names or email addresses.
  • Large numbers of cards added to new accounts, often from the same network address.
  • Rising disputes weeks later, when cardholders notice the charges that went through.

Merchants pay for card testing too: disputes, extra fees and a higher decline rate that can make legitimate customers’ payments look riskier to issuers.

Which controls stop which stage

No single control stops card testing. Each one works at a different point in the attack, and some are run by merchants, some by issuers and some by you.

ControlRun byBlocks the testLimits the cash-out
CAPTCHA, rate limits and login before checkoutMerchantOftenIndirectly
Issuer fraud monitoringCard issuerSometimesSometimes
3-D Secure checksMerchant and issuerWhere the merchant requests itWhere the merchant requests it
Spending limits on a cardCard providerNo, small tests passYes, up to the limit
Merchant locksCard providerYes, at every other merchantYes
Single-use numbersCard providerYes, once usedYes
Separate prepaid card per vendorYouNoYes, to the funds on that card

The pattern is clear. Merchant controls fight the test itself. Card-level controls accept that some tests will pass and focus on making the cash-out small or impossible.

What to do if you spot a test charge

  1. Act on the small charge. Do not wait to see whether a larger one follows. The small one is the warning.
  2. Contact your card issuer. Report the charge as unauthorized and ask for a replacement card.
  3. Dispute any charges that went through. Follow your issuer’s process and keep dates and reference numbers.
  4. Work out where the card was stored. List the merchants that had it on file. One of them may have been the source.
  5. Update the services that used the card. The fewer services share a card, the shorter this list is.
  6. Split your cards going forward. Give important vendors their own cards so the next test only reaches one of them.

How virtual cards limit the damage

Virtual cards cannot stop a fraudster from testing a number they already hold. What they change is how much a successful test is worth.

  • Spending limits cap the cash-out at a set amount.
  • Merchant locks make a stolen number useless anywhere except its original merchant.
  • Single-use numbers are dead after one purchase, so there is nothing to test.
  • Separate prepaid cards per vendor cap the cash-out at whatever is on that card, and keep the stolen number away from your main account.

Example: containing exposure with ZenVCC

ZenVCC is a prepaid virtual card platform, and it covers only the last item on that list. To be direct: it does not offer spending limits you set per card, merchant locks or single-use numbers. If those controls are a must, look for a provider that offers them.

What it does offer is a separate prepaid card for each vendor, bought from one balance funded with crypto (Bitcoin, USDT on TRC-20 or Solana, TRX or SOL), with each deposit checked on its blockchain before it is credited. Because a card can only spend what is on it, a fraudster who passes a test can take at most that card’s funds. Your bank card is never on file with the vendor, and other vendors keep working because they use different cards. For background, ZenVCC publishes a plain-English explainer on how virtual cards work.

Practical details and limits:

  • Costs. A one-time $10 issue fee per card, $0.10 per payment and no monthly fee, so splitting vendors across many cards does not add recurring costs.
  • Validity. Three years from the day the card is ready.
  • Visibility. The ZenVCC dashboard does not list card payments, so you will not see small test charges there. Check vendor billing pages and receipts instead.
  • If details leak. Its guidance is to remove the card from every site that saved it, buy a new card for those payments and contact support with the card’s reference number.
  • 3-D Secure. The dashboard does not show 3-D Secure codes, so a payment that asks for one cannot be completed with these cards. Merchants that require 3-D Secure will decline them.
  • Funds stay on the card. There are no transfers from a card back to the balance, so load each card with what that vendor needs, not more.

Key takeaways

  • Card testing fraud uses small payments or card verifications to find working stolen cards before a larger cash-out.
  • A small charge from an unknown merchant is the warning sign. Report it immediately.
  • Merchant controls such as CAPTCHA and rate limits fight the test. Card-level controls limit the cash-out.
  • Spending limits, merchant locks and single-use numbers are strong card controls where your provider offers them.
  • Separate prepaid cards per vendor cap what any one stolen number can lose, even without those features.

Look at your last three months of statements for small charges you cannot explain, and give your most important vendors their own cards. If a prepaid card per vendor with no monthly fee fits your setup, compare ZenVCC with the cards you use now.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *