Integrating Vantiv and Salesforce using Chargent

Connect Vantiv and Salesforce with Chargent

See all Vantiv transactions, manage refunds, send payment links and more, all inside Salesforce with Chargent, the top rated payments app on the Salesforce AppExchange.

Not yet a Chargent customer?

Contact us for a no-obligation 30 day trial, and see for yourself!


Chargent Payment Processing for Salesforce is the leading payments application available on the Salesforce AppExchange. Chargent can connect Salesforce to Vantiv’s ecommerce payment gateway (formerly Litle Transact) in just a few steps listed below. You will then be able to process credit cards and ACH payments through Vantiv directly from Salesforce.

Installation and Configuration of Chargent

  1. Install both Chargent Base and Chargent Transactions into your Salesforce org.
  2. Configure Chargent according to the step-by-step Installation and Setup Guide.

Vantiv Setup in Salesforce

Connecting Vantiv & Salesforce using the Chargent Setup Wizard

  1. Click on the App Launcher on the top left side in Salesforce.
  2. Select Chargent as the App
  3. Select the Chargent Settings Tab
  4. Choose Chargent Setup Wizard
  5. Select Yes when asked if you have a Payment Gateway account.
  6. Select Vantiv from the dropdown and follow the prompts to configure your gateway
    payment gateway

You will need the following information to configure the gateway:

  • Select Test Transactions for Sandbox or Live Transactions Production.
  • Add your credentials: If testing in Sandbox, Vantiv doesn’t require you to have an account to test with their Sandbox environment. Only Pre-Live, Post-Live, and Production (live) environments will require credentials.
    • Username: Your Vantiv Username (any random username for Sandbox)
    • Password: Your Vantiv Password (any random username for Sandbox)
    • Merchant ID: Your Vantiv Merchant ID (any random username for Sandbox)

Continue through the Setup:

    • Use Tokenization? (recommended)
    • Select your Payment Gateway Currency (USD, CAD, etc..)
    • Do you want to use Payment Console? (Requires Platform Edition and higher)
    • Select the Payment Methods you accept
      • Card: Credit Cards you will accept (Visa, MasterCard, etc…)
      • Bank Account: If your Gateway allows for bank account transactions, you should set the Direct Debit Network to ACH for Vantiv.
      • ACH Validation (optional – disable if you are not using Lyon’s Validation): If you use Lyons ACH verification, you should enable this feature to validate ACH transactions. The ACH Validation feature works with Lyon’s ACH Validation service to validate the bank account and store the validation in your Salesforce Org. During your Gateway Setup, you will authenticate your Lyons credentials, and Chargent uses a referral relationship for all first-time transactions. For more information about implementing validation for your ACH transactions, see our ACH Validation documentation.Select payment methods
  • Setup your Payment Console (Premium feature for Platform Edition)
    • Show Charge Button
    • Show / Create Update Token Button
    • Show Authorize Button
  • Will you be using recurring, scheduled, or installment payments? Do you want to set up Chargent Recurring Billing for subscription billing.
    • If Yes, you will be prompted to select the time. Chargent recommends 3am but you can choose no and select the days and times of the week for the batch to run.

Congratulations! You successfully configured a new gateway. Now you can easily start payments.

Direct Debit Network

Starting with Chargent version 6.15, you can now select the Bank Account network for your region during the gateway setup process. uses the ACH Network. This will allow for the correct Direct Debit Network fields to be displayed on Payment Requests and Payment Console based on your region.

You should choose ACH – US as the network. ACH is also known as echeck or electronic check.

  • US – ACH (also known as echeck or electronic check)

Select the Payment Methods You Accept

Once you have your Direct Debit Network set, you will see the appropriate field names on your Payment Request that are sent as well as your internal Payment Console.

Payment Request Bank Account

Testing Vantiv in Salesforce

Notes on Vantiv Endpoints

Chargent is set up to allow testing using the Vantiv Sandbox and sending live transactions to your Vantiv Production (Live) account. Additional testing may be done using Vantiv Pre-Live and Post-Live environments, which Vantiv may have provided you credentials to. These test environments behave more like the Vantiv production account.

Vantiv Pre-Live environment allows you to run additional tests using test credit card data. The test credit card you use will allow you test your credentials and make sure Chargent is communicating with your gateway properly to approve transactions. Post-Live environment is the one for regression testing of changes to your Salesforce system after you go live and are sending transactions to production.

To send Pre-Live or Post-Live tests from Salesforce, you need to update the Endpoint Override field on the Chargent Gateway record with the correct Endpoint URL, and make sure corresponding remote site settings are active.

    • Vantiv Pre-Live:
    • Vantiv Post-Live:

By default the Test Endpoint checkbox in the Gateway record goes to the Sandbox URL so you want to make sure you have this unchecked if you are using the Endpoint Override.

Testing Using Chargent Anywhere

Testing with Payment Console

To test using the Payment Console, you want to navigate to any record in your Sandbox that has the Chargent Anywhere Component enabled.

  1. Click the [PaymentConsole] button
  2. If you are using multiple gateways select your gateway from the dropdown otherwise continue to step 3
  3. Enter all the Billing Information and click [Next]
  4. Enter in a test credit card number, expiration date, and CVC code based on the Vantiv Test Credit Cards below.
  5. Click the [Charge] button.

You should receive a green box showing Approved.

Vantiv Charge

Testing using Payment Request

To test using a Payment Request you want to be sure you have the Chargent Payment Request feature set up as outlined in our documentation.

  1. Click the [Send Payment Request] button
  2. If you have multiple Payment Request templates set up you will first choose what template you want to use.
  3. Enter an email address where you want to send the test Payment Request along with any amount.
  4. Enter a Contact name (Optional)
  5. Click the [Send Request] button

Send Payment Request

When you receive the email, click the secure link for the Payment Request. Use one of Vantiv credit cards to complete the payform and submit the payment.

You should receive a green box showing Approved.

Card Bank Payment

You should receive a green box confirmation

Card Bank payment

Testing Pre-Live/Post-Live Vantiv from Salesforce

  • Obtain Test Credentials for Vantiv Pre-Live/Post Live environments in Salesforce
    • Contact Vantiv and have your IP addresses whitelisted
    • Obtain the Test Credentials from Vantiv
    • Log into your Vantiv Pre-Live/Post Live Reporting environment
      • Pre-Live:
      • Post-Live:
    • Go to Presenter Credentials
    • Credentials expire every year. If the existing credentials have expired, you may need to generate a new set.
    • Click the Eye icon to decrypt the Password and then copy it.


You also need to make sure you have the Remote Sites added to your Remote Site Settings in Salesforce.

Click the gear icon on the top right and select Settings

  • Under Security select Remote Site Settings
  • Click the New Remote Site Button
    • Remote Site Name = Vantiv PreLive or PostLive
    • Remote Site URL
      1. Pre-Live URL:
      2. Post-Live URL:
    • Check the Active box
    • Click Save

For detailed testing parameters, you may wish to request a reference guide from your Vantiv Implementation Consultant. Chargent’s Salesforce connection to Vantiv has already been certified, so testing is primarily necessary to verify any Salesforce configuration and your merchant credentials.

Vantiv Test Credit Card Numbers

Please note that these test card numbers are only for the test environments, and should never be used in the live, production environment.

If you wish to do more extensive tests, Vantiv can provide detailed transaction data (name, address, amount, card numbers, etc.) and the expected responses that they will return. However, this level of testing is not required as Chargent has already certified its Salesforce pre-built integration with Vantiv.

Vantiv Test Credit Cards

Account Number Card Type CVV2/CID
4457010000000009 Visa 349
4457010100000008 Visa 992
4457010140000141 Visa N/A
4457010200000247 Visa N/A
4100200300011001 Visa 463
4100200300012009 Visa N/A
4100200300013007 Visa N/A
4100200310000002 Visa N/A
4024720001231239 Visa N/A
4457012400000001 Visa N/A
4457013200000001 Visa N/A
4457119922390123 Visa N/A
4457000300000007 Visa N/A
4457000100000009 Visa N/A
4457003100000003 Visa N/A
4457000400000006 Visa N/A
4457000200000008 Visa N/A
4457000800000002 Visa N/A
4457000900000001 Visa N/A
4457001000000008 Visa N/A
4005550000081019 Visa N/A
4000000000000001 Visa 555
5112000100000003 Mastercard N/A
5112002100000009 Mastercard N/A
5112002200000008 Mastercard N/A
5112000200000002 Mastercard N/A
5112000300000001 Mastercard N/A
5112000400000000 Mastercard N/A
5112010400000009 Mastercard N/A
5112000600000008 Mastercard N/A
5112010000000003 Mastercard 261
5112010100000002 Mastercard 251
5112010140000004 Mastercard N/A
5500000254444445 Mastercard N/A
5592106621450897 Mastercard N/A
5590409551104142 Mastercard N/A
5587755665222179 Mastercard N/A
5445840176552850 Mastercard N/A
5390016478904678 Mastercard N/A
5112010201000109 Mastercard N/A
5112010202000108 Mastercard N/A
5194560012341234 Mastercard N/A
5435101234510196 Mastercard 987
5112000900000005 Mastercard 758
6011010000000003 Mastercard N/A
6011010100000002 Mastercard 184
6011010140000004 Mastercard N/A
375000026600004 American Express N/A
375001000000005 American Express N/A
375001010000003 American Express 0421
375001014000009 American Express N/A
341234567890127 American Express N/A

Vantiv Test eCheck Number

accType accNum routingNum
Checking 4099999992 011075150
Checking 1099999003 011100012
Checking 1099999999 011100012

Sending Live Transactions from a Salesforce Sandbox

When Chargent is installed in a Salesforce Sandbox, transactions are typically sent to the payment gateway’s test / sandbox / development environment, regardless of whether Chargent’s Test Endpoint checkbox is checked. This is done as a security precaution, to prevent real transactions from being accidentally sent from a Salesforce Sandbox.

When Chargent is installed in a production or developer Salesforce org, checking the Test Endpoint checkbox on the Gateway record will route transactions to the test environments provided by the gateway.

Note: Some gateways use the same endpoint for live and test environments. For these gateways, the Chargent application does not prevent live transaction processing. As such, it is best practice to deactivate your live gateway records in orgs used for testing.

If you wish to send live transactions from a Salesforce Sandbox, as a final step in testing, simply use Chargent’s Endpoint Override field to enter the production endpoint of your chosen gateway there.

Here is the production endpoint URL for Chargent’s integration with Vantiv:

Note that the full endpoint URL must be entered in the Endpoint Override field and the Remote Site for the domain must be active in your Remote Site Settings.

Moving to Production

Once you have completed testing of your Chargent configuration and Salesforce connection to Vantiv, you are ready to move to processing live transactions.

In your Production Org, delete or deactivate the Vantiv Sandbox / or Pre-/Post-Live and create a new Gateway Record for your Vantiv Live environment:

Complete the Vantiv gateway record in Salesforce using the Gateway Wizard or Manual Setup described above. Your Merchant ID provided to you by Vantiv and the Presenter Credentials available in the live reporting interface:

Test credit card numbers should not be used in the live environment. If you wish to test a few live transactions with your own credit card, you can void them immediately after, to prevent the transactions from settling and capturing funds. Just click on the related transaction record in Salesforce and press the Void button.

Please keep in mind that fees may be charged on all transactions sent to the live, production environment, so a few real tests are recommended, but the majority of testing should be done in the Vantiv Prelive environment.

Vantiv Tokenization

Chargent’s Salesforce integration with Vantiv supports tokenization, which replaces credit card numbers or bank account numbers with a reference code called a token. The account number is then stored in Vantiv’s vault, and the token is stored in your Salesforce account and referenced for future transactions.

Since you do not store the customer’s credit card account information, the scope of PCI compliance is reduced, and if your systems were ever breached only tokens that can only be used with your account are stored in Salesforce, rather than any critical customer account numbers.

AppFrontier recommends that you consult your own legal and PCI Compliance resources regarding how customer data should be handled, but we also offer a Salesforce PCI Compliance guide to provide a useful overview.

Vantiv Token Format

Vantiv Tokens are similar in format to the credit card originally submitted, in that they are the same length as the original credit card number (typically 16 digits), and the last 4 digits of the token are the same as the card. Since Vantiv tokens are stored in the unencrypted Token field in Salesforce by Chargent, this makes them convenient for customer service or other members of your staff to refer to with customers, without knowing or having access to the original account number.

For Vantiv eCheck / ACH tokens, because bank account number length can vary widely, Vantiv made these tokens a uniform length of 17 digits. Unlike credit card tokens, the entire eCheck token number is randomly generated.

To set up Vantiv Tokenization in Salesforce:

  1. Confirm with your Vantiv Account Representative that your account is enabled for tokenization.
  2. Check the Use Tokenization checkbox in the Chargent Gateway record you have set up for Vantiv
  3. Set the Credit Card Handling field (unless you are using Payment Console)
    • 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.

Using Tokens

  • Tokens are obtained either through the Register Token process, which Chargent’s Payment Console feature enables, or when your first approved Charge or Authorization is sent.
  • The Vantiv token is stored in Chargent’s Token field in Salesforce.
  • The Credit Card Number field value will be deleted (based on your Credit Card Handling field settings), and a token will be stored for future transactions (or if you are using Chargent’s Payment Console feature, the card number was never stored during the generation of the token)

If you are migrating from another system, you should be able to import Vantiv tokens into Chargent’s Token field in Salesforce. Tokens would need to be associated with the same customer in Salesforce that the token was generated for. Please contact us for assistance or more information.


Automatic Account Updater (AAU)

Avoid missed / failed payments by enabling Vantiv’s Automatic Account Updater. Contact your Vantiv rep to enable this feature. Once enabled, Chargent will capture a new token for any failed card or ACH payment as long as the new payment data has been updated at the Gateway level.

The next time Chargent attempts to collect the payment with the outdated card information, the transaction has a better chance of success because Vantiv has passed the updated token back to the Chargent Order record.

Chargent supports Vantiv Account Updater beginning in Chargent 5.81, and can update any token in need of repair. When a credit card changes on Vantiv’s side, and the token for the original credit card is sent, Vantiv will send back an updated token related to the new card. Chargent will then write the new token back to the token field on the Chargent Order.

This token replacement will happen seamlessly in the background when the Chargent Recurring Batch runs, or when you process a payment manually using the Payment Console. The following are required

  1. Vantiv’s Token Updater service
  2. Vantiv v12 credentials in your Gateway setup in Salesforce
  3. Select v12 in the “Gateway Version” field in your Gateway setup

Sending Credits

Vantiv gives you the ability to send money from a Chargent Order directly to a customer’s bank account using Credits. Credits allow you to send money to a checking account (ACH/Direct Debit) when the transaction is not a refund of a previous payment. For more information on enabling and processing Credits, visit Sending Credits.

Gateway Version Update

In order to support newer features by Vantiv you should be sure you have Chargent version 5.81 or newer. If you are on an older version of Chargent you will want to upgrade using our PIM (Package Installation Manager). Chargent now supports both Vantiv API v8 and Vantiv API v12. If you recently upgraded Chargent you will need to add the Gateway Version field to your Gateway Page Layout and select the version of Vantiv to work with.

If you have been on Vantiv for some time, you likely will need to select v8. To use newer features such as the Account Updater, request v12 credentials from the Vantiv Implementation team. (Please note that it may take Vantiv 2-6 weeks to generate these credentials).

To add the Gateway Version field to the layout:

  1. Click the gear icon on the top right and select Setup
  2. Under Objects and Fields select Object Manager
  3. Choose the Gateways object
  4. Under Page Layouts select Litle Layout
  5. Drag the Gateway Version field into the Page Layout and click Save


Next you want to update this field on the Gateway record.

  1. Click the App Launcher on the top left side and search for Gateways
  2. Click the Vantiv Gateway record
  3. Click Edit
  4. Click Advanced Features
  5. Select the correct Vantiv version from the drop down.
  6. Click Save


Transaction Sync

ACH transactions take time to settle. Chargent can update your ACH transactions long after the initial transaction, including transactions that are returned for non-sufficient funds (NSF), credit card authorizations that expire, and more. For more information, visit Transaction Sync.

Salesforce to Vantiv Field Mapping

Here are a few relevant fields and their mappings between the Chargent software in Salesforce and the Vantiv system.

Salesforce Field Name
Vantiv Field Name
Gateway ID
Vantiv Transaction Id
Invoice Number
VAT Ref #
Invoice Number
Customer Reference
Salesforce record ID (of Chargent Order, Opportunity, or Case)
Customer ID

Note: If you do not populate the Invoice Number field, Chargent will auto-populate the calls to Vantiv with the format “ChargentOrder071414100533” where the first 6 numeric characters indicate the date.

Congratulations! You have successfully integrated Salesforce and the Vantiv Payment Gateway using the Chargent Payment Processing for Salesforce software. You can now process one-time or recurring credit card payments through Vantiv directly from Salesforce.

If you have any questions or need assistance, please contact us.