GivingTuesday is December 1. Your foundation or development team is planning the emails, the social posts and the match. Somebody else is planning too: people holding lists of stolen card numbers, looking for a payment form that will tell them which ones still work.
It is called card testing. Donation pages are a favorite target, and the damage does not stop when the fake gifts do. A form that gets used for card testing in November can decline real donors on GivingTuesday.
Where this comes from. Stripe's documentation on card testing and GivingTuesday's own site, both read directly. The steps below apply whatever processor you use. The dashboard names will differ.
How Card Testing Works
Someone buys stolen card numbers, then runs a script that tries each one on a real payment form. A card that goes through is confirmed as valid and gets used or resold. Stripe notes that testers favor small payments, because cardholders are less likely to notice and report them.
Now look at a typical donation form. Anyone can reach it without logging in. The donor picks the amount, often as low as a dollar. There is no cart and no shipping address. Stripe says the easier a payment form is to reach, the easier it is to attack. A donation form is about as easy as it gets. Gift membership and event registration pages have the same profile.
Why It Matters More Than the Fake Gifts
- Disputes. Some of the test payments succeed. When the real cardholders see them, they report fraud, and you return the money and pay dispute fees on top of it.
- Declines for real donors. Stripe warns that a high decline rate can damage your standing with card issuers, which can raise declines on legitimate payments even after the testing stops. That is the GivingTuesday risk: real donors turned away because of an attack weeks earlier.
- Bad data. Fake gifts look like new donors. They land in your CRM, trigger receipts to made-up addresses, and distort the numbers you report to your board.
What It Looks Like
Stripe lists three signs: a spike in failed or blocked payments, a spike in declined requests, and a run of low-dollar payments, often with nonsense names and email addresses. If your development team has ever said that a batch of strange one-dollar gifts came in overnight, that was probably card testing.
What to Check Before December 1
- Read your processor dashboard. Look at failed payments for the last 90 days. A spike you did not explain is worth explaining now.
- Confirm the CAPTCHA is enforced. A CAPTCHA only helps if it is checked on the server for every payment request. When a CAPTCHA is not stopping card testing, those are the first two things Stripe says to check.
- Add limits. Stripe recommends rate limits, such as capping how many payment attempts or new donor records a single source can create in a day.
- Reconsider the minimum gift. A one-dollar option serves card testers better than donors. Raising the minimum gift is our recommendation, not Stripe's, and it is a fundraising decision, so ask your development team first.
- Know what your form is built on. Stripe says its own recommended payment forms include card testing protection, and that sites using a plugin usually need code-level changes to get the same. If your donation form is a plugin, send that documentation to the developer or vendor.
If It Is Already Happening
Stripe's advice is to refund the fraudulent payments to head off disputes, add protections, and keep watching to confirm they work. Do not retry failed payments from those records. Stripe says retrying repeats the original attack.
Plan for the Day Itself
Decide now who watches the payment dashboard on December 1, and who is allowed to turn on a stricter CAPTCHA or pause the form if an attack starts at 2 p.m. with your match still running. That person should not be finding out where the settings are for the first time.
Then send a test gift through every donation form you have, and confirm the receipt arrives. A donation page that takes the payment but never sends the receipt is a different problem, and it is one you want to find before your donors do.