Guide
Hundreds of small Stripe payments failed overnight. What a card testing attack is, what to do first, and what it does to your payouts and books
You wake up to 400 failed payments of $1 and $2, a few dozen that went through, and a customer list full of names like 'asdf qwer'. Nobody bought anything. Someone found a page on your site that takes a card and is using it to check which stolen cards still work. It is called card testing, and the clock that matters is not the declines. It is the handful of charges that succeeded.
How to tell it is card testing
Stripe's documentation lists three signs: a spike in failed or blocked payments on the Dashboard, a spike in API requests failing with 402 errors and a generic_decline outcome, and a spike of suspicious payments with low amounts, often with nonsensical customer names and emails. Attackers like small amounts because cardholders rarely notice them, and they like 'save card' pages because, in Stripe's words, card setup checks don't typically show up on cardholder statements. Many new customers created from the same place in a short time is the other giveaway.
Stripe's checklist, in order
Stripe's support checklist has four steps. One: identify the card testing activity. Two: refund the fraudulent payments to avoid disputes. Three: add one or more mitigations to your integration to stop it. Four: monitor that the mitigations work. If the attack keeps going after all four, Stripe says to contact support with the active charges and the list of mitigations you have already taken. Do step two early. The declines cost you little; the successful charges are the ones that turn into problems.
Why the charges that went through should be refunded now
Every test charge that succeeded is a real charge on a stolen card. When the real cardholder sees it, they report it as fraud, and Stripe says that leads to early fraud warnings or fraudulent disputes 'that cost you time and money'. A dispute takes the amount back plus a dispute fee, and a burst of disputes and warnings can, per Stripe, enlist you in the card networks' monitoring programs. Refunding first costs you only the processing fee on each charge, which Stripe keeps on a refund. On a pile of $1 charges, that fee is the whole loss, and it is far smaller than a dispute fee on each one.
What it costs, and what it doesn't
Stripe's documentation names the extra costs: authorization fees for accounts on custom pricing plans, and dispute fees. Check your own pricing page or contract for whether declined attempts are billed on your account; Stripe's card testing page doesn't say for standard pricing, so don't assume either way. Two costs don't show up on any invoice. Stripe warns that a wave of card testing can raise your decline rate for real customers even after the attack stops, and that test charges can look like good new customers in your data.
How to stop it
Stripe's first answer is to use a recommended integration, its current Payment Element or Checkout, which include rate limits, fraud models and CAPTCHA triggers; payments those stop are marked Blocked by Stripe. On top of that: require a login or a session check before anyone can reach a payment or save-card form, limit how many customers one IP address can create in a day, limit how many cards one account can add, and, if your Radar plan supports custom rules, write velocity rules for those limits. Stripe says a single filter such as blocking IP addresses is usually not enough on its own, so combine them. Keep your secret key secret: a leaked key lets testers create payments directly. Then, if the attack created customers or subscriptions, make sure nothing keeps charging them. Stripe's documentation warns not to keep retrying cards set up on fraudulent customers after an attack, because that repeats the original attack. Cancel any subscriptions the attacker started, and clear the fake customers out of your reporting so next month's new customer count and revenue aren't inflated by them.
What it does to your payouts
Declined attempts never settle, so they never appear inside a payout. The successful test charges do: each one lands in a payout as a small charge minus its fee. Your refunds come out of the next available payout, usually a later one. So the cleanup shows up as one payout with a cluster of tiny charges, and a later payout that is short by the refunds. Neither is an error. Any dispute that slips through comes out later still, with its fee on its own line.
How to book it in QuickBooks
Don't let the attack show up as sales. If you use a Stripe clearing account, record the successful test charges and their refunds against the same revenue line so they net to zero, with a memo like 'card testing, refunded' and the date range. Record the processing fees Stripe kept as a fee expense, or a separate fraud loss account if your bookkeeper prefers to see it on its own. Any dispute fees go to the same place. The payouts then match: the charges and refunds cancel out, and what is left is the fee total, which is the attack's cost.
See it in the morning, not at month-end
Conciliq reads your Stripe account every morning with a read-only key, rebuilds each payout line by line and tells you whether it is Matched, Timing or needs a look. A payout carrying a pile of tiny charges, or one short by a burst of refunds, is listed with what is inside it, so the cleanup is explained the day it lands. We can see your data, never touch it.
Check yours
Does the money Stripe paid you match your books?
Upload a Stripe export or paste a read-only key. Every payout in the last 90 days, matched to the cent, usually in under a minute. Nothing stored.
Run the free audit →Questions people ask
- Should I refund card testing charges or let them be disputed?
- Refund them. Stripe's checklist says to refund fraudulent payments to avoid disputes. A refund costs you the processing fee on the charge; a dispute takes the amount back, adds a dispute fee, and counts against you with the card networks.
- Does Stripe give back fees on refunded card testing charges?
- No. On Stripe's standard pricing, the processing fee on the original charge is not returned when you refund. On a card testing attack, those kept fees are most of the cost. Check your own contract if you are on custom pricing.
- Will blocking the attacker's IP address stop card testing?
- Usually not by itself. Stripe says single-signal filters like IP addresses are rarely enough. Combine a recommended integration such as Checkout or the Payment Element with a login before payment, per-IP limits on new customers, and CAPTCHA.
More guides
- Why your Stripe payout doesn't match your sales (and how to check it)
- QuickBooks' Stripe connector imports payouts, not fees. Here is what that does to your books
- Stripe payout breakdown: what every line inside a payout means
- Why a Stripe refund comes out of a later payout
- How a Stripe dispute hits your payout, and how to record it in your books
- A customer's card expires before their next Stripe renewal. What happens, and what to do
- Stripe debited your bank account. Why your balance went negative, and how to book it
- Stripe says the payout is Paid, but the money isn't in your bank. What each payout status means, and what to do
- How to reconcile Stripe payouts in Xero: what Xero matches on its own, and what it can't
- Stripe put a reserve on your account. What it does to your payouts, when the money comes back, and how to book it
- A Stripe renewal was declined. What do_not_honor, insufficient_funds and the other decline codes mean, and what to do about each
- You charged in euros or pounds and Stripe paid you in dollars. Where the conversion fee went, and how to reconcile it
- Your Stripe 1099-K is bigger than the money that hit your bank. Why, and how to tie it to your books
- When does Stripe pay you? The payout schedule, the first-payout wait, and what each setting does to your books
- How to record Stripe payouts and fees in QuickBooks Online by hand: the clearing account method, step by step
- How to read Stripe's payout reconciliation report: what each section means, which download to use, and how to tie every deposit to your books
- Your Stripe payout includes sales tax you owe. How to record it in QuickBooks, and why Stripe's tax report won't match your deposits
- A customer paid a year upfront through Stripe. How to record it in QuickBooks so one month doesn't look like a record
- Stripe sent an early fraud warning. Should you refund the charge or wait, and what each choice does to your payout
- Why your Stripe fees are more than 2.9% + 30¢, and how to find what each extra charge is
- A Stripe ACH payment looked paid, then failed days later. Why it happens, what it does to your payout, and how to book it
- A customer paid a Stripe invoice by check or bank transfer. How to mark it paid, why it never shows up in a payout, and how to book it
- You gave a customer a Stripe coupon. What it does to the charge, the fee and the payout, and how to record the discount in QuickBooks
- A Stripe refund failed. Where the money went, why your payout is suddenly bigger, and how to get the customer paid
- A customer downgraded or cancelled and Stripe gave them a credit, not a refund. Where the money is, why your next payout is smaller, and how to book it
- QuickBooks shows double your Stripe income. Why the sync app and the bank feed both recorded it, and how to fix it
- Stripe says a subscription is incomplete, past due, unpaid or paused. What each status means for the customer, your payouts and your books
- You took Stripe Capital financing and your payouts got smaller. How the repayment works, and how to record it in QuickBooks or Xero
- You took a Stripe Instant Payout and now nothing reconciles. How to match instant payouts, their fee and the smaller payouts after them
- Stripe fee calculator: what your payouts really cost