This is very common among almost all major eCommerce companies. Clickbait title, but the gist of this is to say, "Hey, we know you lose your card from time to time... and cards eventually expire (sometimes because of a security breach or other issue that you, the end-user, had nothing to do with). Rather than make you waste time going back through and updating every instance where you opted for the vendor / service provider to save your info, and risk you getting late fees or your electricity being turned off, let's just be smart and push updates to trusted stores that you have already opted to give your card to."
Sometimes I cancel a card, to revoke access to accounts I lost the password to.
When I cancel a card, that doesn't mean that certain people should predict their own capacity to use a new card.
Glad to know that the destruction and replacement of a card might not work. I will now reconsider my tactics for revocation.
Clearly, I need to destroy, uproot the account, migrate elsewhere across provider boundaries, and deny further awareness of cards that might possess the property of re-use.
Certain companies must only be aware of disposable numbers, since they seem to be frisky about what I'd elect for them to know.
Better workflow would be to cancel the account by contacting customer support.
Some cards offer one-time-use numbers, those work great for one-time transactions but a vendor won't be keen on accepting them for recurring payments as you would have to re-enter a card number every billing cycle.
Typically disposable numbers are easy to identify (for the vendor at any rate), much the same way a Visa or MasterCard are different from each other.
Bank of America years ago had disposable credit card numbers. I found them awkward to generate (I think it was a Java applet?) and I couldn't use the criteria I preferred. They might have changed that.
Final https://getfinal.com/ is a startup that looks to be built around this concept.
Nothing sinister going on here at all.