Overview:  Based on your business needs you can either store a credit card token for future use or simply delete the token after a transaction.  A token is a secure digital representation of your customer’s credit card and allows you to avoid storing actual credit card numbers.

Note: By default a credit card token is kept one (1) day.

Determining if you should store the token for future use:

1. If you wish to provide the highest level of customer convenience and eliminate the need for customers to repeatedly enter their credit card number then you should store the token!
   Note: Your customers prior billing address, shipping address and all other previous data will remain in their account. Only their credit card details will be deleted.
2. If you process payments as an administrator on behalf of the customer you should store the token!
   Note: You can impersonate and manage accounts regardless of tokenization settings but your ability to charge a customer’s card without the credit card number would be lost unless you store a token.
3. If you currently or intend to use any recurring billing functions in Event Manager you should store the token.
   Note: In order to use our recurring billing features such as subscriptions and Auto Pay to Balance Owed you must have the stored token to successfully process the credit card.
4. If your gateway requires a full credit card number to process a refund you should store the token.
   Note: Most gateways require only the Transaction ID to process a refund, consult your gateway provider for details.

If you answered NO to all four questions the then there is no commercial reason to store any tokens and you should keep the default settings for the number of days to retain credit card tokens set at one (1). 

If you answered YES to any of the four questions then you must decide how long you want to retain the token for future processing. To change your settings follow the instructions below.

How To: Navigate to “Configuration” by selecting “Settings”.


For quick navigation, type in the word "Token" and search.


By defining a number between 0 to a maximum of 2000 you will define how long (days) you retain the TOKEN for use.

0 (zero days) = The TOKEN is removed immediately after the purchase. (This setting ensures your customers enter a credit card number for every single transaction.)

1 (one day) = The TOKEN is removed after a 24 hour period. (This setting allows multiple purchases without entering credit card information inside a 24 hour period from the start of the original purchase.)  This is the recommended duration and is the default setting.

If you create and sell a product with “Reoccurring Billing” enabled you must have a TOKEN on file complete the Reoccurring Billing orders. In this instance the user-defined-value entered in the “System Configuration” will be overridden and retain a TOKEN for that specific order only for the duration required to fulfill the Reoccurring Billing orders.  Once the order with Reoccurring Billing is completed the Token will no longer be stored.

Enter the value and click “Save” to define the length of time your database will retain the Token.

Note: If, for example, you are a seasonal company, you may wish to input "90" as the number of days to store tokens, so that users who may wish to purchase multiple products during a season can do so without re-entering their credit card number.


Charges may apply to values greater than one (1).