If you delete card records from the Registered Cardholder database, it would not prevent the cardholder from re-registering. For example, a card has been deleted from the registered users' database; the next time the cardholder attempts performing a transaction using that card, the AOF window appears prompting the cardholder to re-register the card.
If you do not want the card to be able to register again, you should also delete it from Potential Cardholder database. This way the card will not be able to register or perform any transactions in any case (will fail in authorization stage).
The issuer can send Delete commands only for registered cards. So should scan through the Registered Cardholder report generated by RSA and locate the cards to be deleted before sending Delete command.
|Issue||When a card is reported lost or stolen, how can it be deleted from RSA Production System?|
1) There are two main databases when discussing Delete ? Potential Cardholder (contains all the cardholder information required for registration) and Registered Cardholder (Registered cards).
2) There are two main batch files when discussing Delete ? Delete batch file and Addupdel batch file (with Delete action ?D?). DELETE batch updates the Registered Cardholder DB and ADDUPDEL with D action updates the Potential Cardholder database.
Note - Using the Delete file is also important from billing purposes- if you cancel a card and delete its record through the ADDUPDEL, RSA will continue to bill this card. In order to remove it from the billable cards table, you should delete it from the registered cards DB.
Note - If user has multiple cards per user and one of these cards was deleted from the registered card DB, the user will still be registered for the service; just this specific card will be removed.
|Legacy Article ID||a47924|