|
|
|
|
|
by hunter2_
1103 days ago
|
|
Ah. So in that case, NPM is not learning a new card number, and probably isn't even aware of anything at all, given that the card issuer is simply accepting transactions (instead of declining them as this person expected) on the old card number. NPM was in the wrong for continuing to place unwanted transactions, but they were not actively participating in this "follow" scheme so the blame stops short of that. |
|
The way the update services is work is that you send them the card type, card number, and expiration date of a card you have on file, and they respond typically with one of these four responses:
1. Still good.
2. The account is closed.
3. The card is still good but has a new expiration date, which is YYMM.
4. The account has a new card. The card number is XXXXXXXXXXXXXXXX and the expiration date is YYMM.