Chargent Payment Processing for Salesforce includes prebuilt integrations with 25+ payment gateways, giving you the most options of any Salesforce payment processing solution. No integration work required, just cut and paste your credentials into a Salesforce Gateway record and you are ready to go.
Payment Gateways supported by Chargent via Authorize.net Emulation
Please note that any gateways that support Authorize.net AIM emulation work with Chargent, but some functionality may be limited.
Gateway-Specific Integration Guides
Is your payment gateway not on our list? We offer custom gateway setup for a one-time fee, please contact us for more details.
Chargent's payment gateway integrations can support merchants in many countries around the globe, and process payments from hundreds of countries and currencies. Please see our International Payment Gateways for Salesforce page for more information.
Chargent connects directly from Salesforce to a number of different Payment Gateways. You can use any Payment Processor on the back end to process the payments, as long as it works with one of the Gateways that Chargent connects to. You can think of Chargent as a "virtual terminal" that lives 100% within Salesforce, and sends secure credit card and ACH transactions to a gateway, which then sends it to a merchant account and eventually your bank.
To begin credit card and ACH transactions through Salesforce with Chargent, you need a merchant account from a payment processor as well as a payment gateway. Some companies bundle the two services together but they can also be purchased separately.
The gateway is a service running on servers that securely connects the purchase platform (eg. Salesforce with Chargent installed, or an eCommerce web site) to the payment processor. When you process a transaction through Chargent, the credit card info is sent through the gateway to the processor.
The processor hosts the merchant accounts. It is responsible for securely receiving the data sent by the gateway. When it obtains the information needed to process the payment, it begins to handle the transaction and transfer money from the customer to the merchant's bank account.
Many large payment processors support multiple payment gateways. This is often hard to find on their web site however, since they typically prefer that you use their own gateway or a private labeled gateway, but if you contact them they should provide you with the information.
As an example, if you use Chase Paymentech for your Payment Processor, you can use Chase's Orbital Payment Gateway, but you can also choose Authorize.net as your Payment Gateway.
Vantiv (formerly Litle & Co.)
You can use any of these payment processing services with Chargent if you choose Authorize.net as your payment gateway:
You can use any of these payment processing services with Chargent if you choose Payflow Pro as your payment gateway:
Tokenization is a security technology that replaces credit card numbers with "tokens" generated by a payment processor. This means that merchants are not required to store the credit card numbers, and the secure token replaces the credit card number for processing transactions and being stored in your database. Each token is specific to a merchant, so it is useless to anyone else in the event of a security breach.
Chargent currently supports tokenization through most of our payment gateway partners. Please contact us for details.
So consider using tokenization with Salesforce and Chargent. Unlike a credit card or account number, you can store tokens without the possibility of exposing customer information, greatly lowering your PCI compliance scope. And the payment gateways store the information in their secure systems, and access it only when you submit a transaction using the token stored in Salesforce.
Please note that some gateways may assess a fee the first time a token is generated. For more information on tokenization for credit card payments directly from Salesforce, please contact us.