Every authorization attempt carries fixed network and processing fees, whether it approves or declines. A testing wave is thousands of declines, and each one lands on your statement. Here is the fee stack, then a calculator you can put your own numbers into.
These are always-on, per-attempt pass-through fees. They are charged when the authorization request reaches the network, so a declined card test is billed just like a real order. Figures shown are representative; exact amounts vary by processor.
Enter the declined attempts from one card-testing event. The network fees above are fixed; add your gateway's per-authorization fee for a fuller picture. Nothing leaves your browser.
At minimum, in network and processing fees — before any chargeback losses or VAMP exposure.
A single enumeration run is rarely a one-off. Attackers probe in waves, so the real figure compounds across events. This estimate is a floor, not a forecast.
Enter a decline count to see the floor.
Gateway-native scoring runs after the attempt is already there, so the per-attempt fees are charged whether it blocks the card or not. Cardvera sits in front of the gateway and turns card testing away before the meter starts.
See what this looks like on your own traffic. Tell us what you're seeing and we'll walk you through where Cardvera turns card testing away, before the meter starts.
No spam. No drip campaigns. Just a reply from a human.