Menu

Card testing hides inside your own decline rate
📰

Card testing hides inside your own decline rate

DEV Community: backend·Payneteasy·about 10 hours ago
#R9rVHAyp
#devtobackend#devto#dev#decline#card
Reading 0:00
15s threshold

We found card testing on a checkout by accident. A merchant's approval rate fell from 81% to 64% in two days. The first guess was an issuer problem or a routing bug. It was neither.

The logs showed about 3,000 attempts an hour from a few hundred IPs. Each attempt was a $1 authorization with a different PAN, and almost all were declined. A few percent were approved, and that was the point: the attacker was checking which stolen cards were still live.

The checkout endpoint had no limit on failed attempts per session, per IP, or per BIN range. It accepted anonymous POSTs and returned a clean decline code each time. We had effectively built a card validity oracle and handed it out for free.

The fix was boring:

Cap failed attempts per session and per device fingerprint, not just per IP. Botnets rotate IPs.

Add a CAPTCHA or 3DS step after the second decline.

Return the same generic message for every decline reason on the client side.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.