2026-06-16 19:15 UTC
@henryk@chaos.social The concern is more the full combination returned together in a single API response: BIN (first 6) + last 4 + expiration + cardholder name + full billing address + billing IP. That's enough to reconstruct most of the PAN with brute force and satisfy AVS for card-not-present transactions.
Replies (1)
-
@henryk@chaos.social 2026-06-16 19:22
@bobdahacker@infosec.exchange I understand, but that's exactly what I pointed out: name, expiration, and 6+4 are within the boundary the PCI-DSS sets (well, *on* the boundary ;) and by definition not a security problem (beyond the PII angle). It's emphatically not enough for card-not-present transactions since, as you pointed out, the CVV is missing. *That* is the security boundary. I'm all for the "this is the shittiest leakiest API ever designed" classification, but it doesn't run afoul of PCI on this count.