We recently turned on the collection of credit cards to allow to offer recurring donations online. We want to remove the cards and tokens for patrons who are not on a payment plan which is the majority of cards in the system. I was hoping the deletion report would remove them. However I have found the number of cards deleted is not meeting my expectation. It is deleting about 5K records and leave me with about 40k records
I am looking to see what criteria other people are using to see how I can change my criteria to delete more. We are not on v..16 or using TMS, but we are moving in that implementing both of those soon.
Here is what I am currently using. Before the last run, I switched the Tokenize Cards? to Yes as I read that would delete the token. Before then I had it set to No. That change did significantly increase the number of deleted records.
Any feedback or example of other criteria would be helpful.
"Tokenize cards" is for turning locally stored cards numbers into tokens, the opposite of deletion. You should set that to no if you are doing a deletion run.
Gawain Lavers That is what I thought till I read this in Report Help. It seems contradictory when you say Yes to tokenize cards.
Tokenize Cards? – When set to Yes, all on-file credit cards will be tokenized. If the utility is run in deletion mode at the same time, only cards remaining after the deletion portion of the utility will be tokenized. If cards have already been tokenized, to purge existing tokens this parameter must also be set to Yes.
Interesting, I've always had this set to "No" in our scheduled jobs, and have a strong memory of it being specific to the (generally one-time) tokenization process. If set to "No" the Payment Method Group, which should also be irrelevant to card/token deletion, is disabled. I would confirm with support, but I believe the documentation is in error here.
HiI looked at this as part of v16 planning and have the following notes, I think from the v16 prep documentation. It contradicts the Yes/No instructions in Seth's snippet. I haven't done it yet, however, so can't report on results unfortunately! Note the comment about 2k max for tokenisation, which might explain your low numbers if you have that set to Yes.best wishesDawn
1. Delete existing cards which don’t need to be stored Run the Credit Card Tokenization and Deletion Utility with the following parameters. Once you have verified the results in review mode, it can be run in update mode. Credit cards associated with active payment plans cannot be deleted. Please note that this process is irreversible.
If only some credit cards should be deleted, the Exclusion List parameter can be used to define which constituents should be skipped. After deleting the existing credit cards, the remainder should be tokenized; see "Tokenize stored credit cards" below.
2. Tokenize existing cards to be stored Run the Credit Card Tokenization and Deletion Utility with the following parameters. Once you have verified the results in review mode, it can be run in update mode. You should select the appropriate Payment Method Group for your organization. Please note that credit cards cannot be "untokenized"; this process is irreversible. Note: When tokenizing cards, a maximum of 2000 cards can be tokenized in a single run of the utility (this is to avoid any issues with a long run timing out). If you have more than 2000 cards to tokenize the utility must be run multiple times. The maximum is automatically imposed, so you do not need to manually limit the number of accounts included in a run of the utility. Cards remaining untokenized due to reaching the 2000 card max in one run of the utility will automatically be selected the next time you run the utility with the same parameters.