Active: Enables a Gateway record to be used, in the same way that other parts of Salesforce have an Active checkbox. You may wish to have multiple gateway records, especially if you have a separate test account, and keep some deactivated.
Test Endpoint: Test Endpoint sends transactions to a separate test server or sandbox environment, which cannot be used for live transactions. We recommend testing with Test Endpoint checked and your test credentials, until you are ready to capture live transactions.
Note: If Chargent is installed in a Salesforce Sandbox, for security purposes all transactions are sent to the test endpoint, whether or not this field is checked.
Endpoint Override: This field enables you to enter a custom URL to send transactions to. It is primarily used for payment gateways that run Authorize.net emulation on their own server URLs. It is also required if you want to send live transactions from a Salesforce sandbox account, as a final step in your testing. For security purposes, Chargent sends all transactions to the test account from Salesforce sandboxes, regardless of whether “Test Endpoint” is checked or not. Note that for Endpoint Override to work, the domain must be added under Salesforce’s Remote Site Settings first.
Debug: Debug can be useful for troubleshooting and verifying the values being sent to the payment gateway, but should only be enabled temporarily. It displays the complete XML or HTTPS request that is being sent to the server and response strings in the popup window when you click the appropriate button on your screen (Charge, Authorize, etc.). Note: This feature should only be used by System Administrators or trusted users as it may contain decrypted payment data!
Require AVS: prevents the transaction from being submitted to the gateway without billing address fields being populated. Generally AVS settings are controlled through your payment gateway, but this will prevent Chargent from sending the transactions at all if the address data is not present in Salesforce.
Require Card Security Code: The Card Security Code (CSC, or CVC) is required when processing a charge using the Charge button. When you charge a transaction you will have a pop-up requesting a CVC code. If the Require Card Security Code is checked, then you must enter in a CVC in the pop-up otherwise you will receive a message saying it’s required.
Note: This is only when using the Charge button and does not affect Recurring Billing.
Use Tokenization: should be checked in gateways that support it if you wish to use stored tokens. If the checkbox is unchecked, credit card numbers will be used for transactions.
Accounting Seed Integration: enables the integration with the Accounting Seed accounting software for Salesforce when checked.
Gateway Response: Stores the entire response from the gateway. The same data that debug mode shows in a popup, but the credentials and credit card data is masked.
Credit Card Handling: Allows you to choose if/how credit card data is stored in different scenarios. For PCI Compliance reasons, many customers do not wish to store credit card data. The options are as follows:
- Never Clear: Chargent will not remove any card data automatically.
- Clear After Successful Charge: Chargent will clear the credit card number, expiration dates and card security code only after a successful charge is run.
- Clear After All Transactions: The credit card number, expiration date and card security code will be erased after any transaction (Charge, Void, Refund)
- Clear When Token Present: Only when a token is present in the token field, will the credit card number, expiration date and card security code be cleared. (Recommended)
Chargent supports multiple active gateways. If only one gateway is active, it will be used for each payment transaction. With multiple gateways active, you will need to populate the Gateway lookup field with the desired gateway record for each Chargent Order record..
Many customers use Chargent’s multiple gateway functionality to keep payments for different business entities separate while using a single Salesforce account, or for supporting multiple geographies / currencies that might require multiple payment gateways.