We have been automatically storing tokenized cards and would like to continue using this feature.
Our ticket kiosks use a dummy constituent ‘Kiosk User’ as a way to offer a quick, anonymous guest checkout experience. Since this dummy account is used by many different users each day, we realized it has been storing hundreds of tokenized cards on the record, which we do not want.
The only way I can find within the client to clear out just this specific account is to delete the cards one-by-one from the record. The parameters on the Credit Card Tokenization and Deletion Utility can be set to EXCLUDE a list of constituents, but not to target specific ones.
I am looking for:
I’ve been in touch with TASK, and am currently looking into developing a stored procedure based on AP_PURGE_T_ACCOUNT_DATA. Before we spend a lot of time on it, I wanted to check if anyone else already has a solution.
I’ve tested simply deleting the lines from T_ACCOUNT_DATA for that specific customer_no, and haven’t found any issues yet. Could it be as simple as that, or am I missing something?
We are on 12.5.1 and use Payment Express.
Hi Jennifer - there are other tables that potentially need to be updated when a row is removed from T_ACCOUNT_DATA. For example, tables like t_payment, t_contribution, etc contain an act_id column that references T_ACCOUNT_DATA.[id] that should be set to 0 or NULL (it seems to vary whether it should be 0 or NULL depending on the table). As Gawain pointed out, looking at AP_PURGE_T_ACCOUNT_DATA should allow you to quickly find the related tables.
Good luck!
David