Chargent supports Ezidebit tokenization for both credit card and direct debit transactions. This section contains the procedure for configuring the use of tokens that pass between Chargent and Ezidebit. Tokens are used to improve security by replacing account numbers in Salesforce, and referencing the data securely stored at Ezidebit.
This may have been selected during the setup of your Ezidebit gateway in Salesforce, however if you are adding tokenization later or have a need to update how the credit card and bank account information is handled, you can follow the steps to ensure account information is cleared when a token is present.
- On the top left hand side of your Salesforce page, click the App Launcher
- Search for and select the Gateways optionSelect the Ezidebit gateway and click the Edit button on the top right.
- You want to make sure the following two items are configured.
- Use Tokenization is checked
- Credit Card / Bank Account Data Handling is set to Clear When Token Present.
We recommend that you choose the Clear When Token Present option, which would cause the Chargent system to erase the credit card number and expiration date after any transaction (Charge, Void, Refund) for a card only if there is a value in the token field.
Note that payments made through Chargent’s Payment Request and Payment Console features tokenize credit card and direct debit transactions in memory, without ever saving account numbers to Salesforce.
Otherwise, you can choose from among these other options:
- Never Clear – Chargent will not automatically remove card data.
- Clear After Successful Charge – Chargent will clear the credit card number, expiration dates, and card security code only after a successful charge occurs for a card.
- Clear After All Transactions – Chargent will erase the credit card number, expiration date, and card security code after any transaction (Charge, Void, Refund) occurs for a card.
- Click Save to commit your changes.
NOTE: After your first successful transaction, the token is stored in the Chargent Token field in Salesforce and the credit card fields are handled according to the choice in the Credit Card Data Handling field.
If you use tokenization to process credit cards via the Ezidebit gateway, there is currently a transaction limit of $10,000. The reason for this limit is due to a required field in Ezidebit’s API called paymentAmountInCents.
When Chargent sends a transaction to the gateway, it converts the transaction amount to cents to meet the requirements of the gateway’s API. Ezidebit currently restricts the contents of the paymentAmountInCents field to values less than or equal to 1,000,000 cents. A transaction that exceeds $10,000 will result in an error.
For more information about the current limitation, you can view Ezidebit’s API documentation.