Re:Credit cards are vulnerable to brute force kind attacks
by rconti on Friday May 01, 2026 @06:09PM
(#47981064)
Yep. I've been able to use the "wrong" (but still valid) expiration date on my AmEx for a long time. I've had other credit cards where the autopay info was never updated and it just kept working for at least 6 months.
[ Parent
| on HN ]
Re:Credit cards are vulnerable to brute force kind attacks
by Marsymars on Friday May 01, 2026 @08:08PM
(#47981956)
Funny, the Amex on my Pixel Watch stopped working only a couple weeks after the physical card expiry.
It was quite confusing, because a) I received a replacement physical card several months before the card expiry, so by the time my watch stopped working I'd entirely forgotten about it, b) there's no indication anywhere in the Android/Wear OS of what the expiry date is or that it might be expired and c) there's no indication at the point of sale that the virtual card is expired, simply a generic "Declined" message.
Re:Credit cards are vulnerable to brute force kind attacks
by kay_o on Friday May 01, 2026 @07:49PM
(#47981838)
You can run a charge with only the card number if you have sufficient trust. Each additional piece you add reduces liability and transaction fees (add exp, add cvc, add 3ds, ...)
Re:Credit cards are vulnerable to brute force kind attacks
by Denvercoder9 on Friday May 01, 2026 @06:19PM
(#47981160)
Account Updater functionality isn't necessarily even involved there. In the end whether to accept a transaction is up to the issuer, and quite often they'll keep accepting recurring transactions on otherwise outdated card information.