4 ms·
Payment processors don't allow just brute forcing all card numbers a.k.a. card enumeration or card testing [1][2] and card schemes penalise merchants and paymen
by janpeuker 6mo ago
Payment processors don't allow just brute forcing all card numbers a.k.a. card enumeration or card testing [1][2] and card schemes penalise merchants and payment processors heavily if they don't take measures against it [3].
1) https://stripe.com/newsroom/news/card-testing-surge https://stripe.com/newsroom/news/card-testing-surge
2) https://stripe.com/blog/the-ml-flywheel-how-we-continually-improve-our-models-to-reduce-card-testing https://stripe.com/blog/the-ml-flywheel-how-we-continually-i...
3) https://docs.stripe.com/disputes/monitoring-programs#enumeration-monitoring https://docs.stripe.com/disputes/monitoring-programs#enumera...
- kodbraker 6mo agoThe rate they try becomes very non frequent when they use multiple card validation apis. I'm not sure how it can be related when it's different pan numbers, different source ips etc. Enumerating CVC2 with a single PAN is a different story.
- opengrass 6mo agoUntil 6 years ago Stripe didn't obfuscate card numbers in API logs at all.
- e28eta 6mo agoThat’s untrue. While I would be willing to believe that for a brief period of time there was a bug that could expose it, having been at Stripe between 2017 and 2020, it was my experience that they had a robust system preventing PANs from being disclosed. That included efforts to mask PANs that were in the wrong place. We didn’t want them in our internal logging systems, and we certainly didn’t want to leak them back to the merchants.
- SkiFire13 6mo agoThis is pretty much a PCI DSS requirement for anyone that directly handles PANs.