AppFrontier

Vantiv Salesforce Integration Chargent

Integrating Vantiv and Salesforce using Chargent


Overview


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'll then be able to process process credit card and ACH payments through Vantiv directly from Salesforce.


Vantiv Setup in Salesforce


  1. Install both parts of Chargent Payment Processing for Salesforce into your Salesforce org.
    • Note that Chargent is a paid application, but it has a 30 day trial.

  2. Configure Chargent according to the step by step documentation.

  3. Obtain Test Credentials for Vantiv Pre-Live Testing in Salesforce

    • Contact Vantiv and have your IP addresses whitelisted
    • Obtain the Test Credentials from Vantiv
    • Log into your Vantiv PreLive Reporting environment at https://reports-prelive.litle.com/ui/home
    • Go to Presenter Credentials
    • Credentials expire every 6 months. If the existing credentials have expired, you may need to generate a new set.
    • Copy the Username
    • Click the Eye icon to decrypt the Password and then copy it
    • Enter these in the correct fields in step 6

    Vantiv Presenter Credentials


  4. Add a Gateway record for Vantiv in Salesforce
    • Switch to the Chargent application in Salesforce
    • Go to the Gateways tab
    • Click New

  5. Select Vantiv as the record type from the list of pre-integrated payment gateway integrations for Salesforce that Chargent provides.

    6. Select the Vantiv Gateway in Salesforce


  6. Complete the Vantiv gateway record in Salesforce using the Merchant ID provided to you by Vantiv and the Presenter Credentials available in the Prelive reporting interface:

    • Gateway Name: Any name you choose, for example "Vantiv Test"
    • Merchant ID: Username
    • Merchant Security Key: Password
    • Merchant Reference: Merchant ID provided by Vantiv
    • Active: checked
    • Test Endpoint: not checked
    • Endpoint Override: should equal https://transact-prelive.litle.com/vap/communicator/online (see notes on Vantiv endpoints below for more information)
    • Click Save

    Vantiv Gateway Settings in Salesforce


    Notes on Vantiv Endpoints

    Vantiv has several different endpoints for testing, and one endpoint for live transactions. Prelive is the environment you will use to run initial tests. Postlive is the environment for regression testing of changes to your Salesforce system after you go live and are sending transactions to production. The Vantiv Sandbox (testlitle.com) is not used, as Chargent has already done the functional integration between Salesforce and Vantiv.

    • Vantiv Sandbox     http://www.testlitle.com
    • Vantiv Pre-Live     https://transact-prelive.litle.com
    • Vantiv Post-Live     https://transact-postlive.litle.com
    • Vantiv Live     https://transact.litle.com

    By default the Test Endpoint checkbox in the Gateway record goes to the Postlive environment, so your initial tests should be done using the Endpoint Override field.

  7. For security purposes, you need to add the Prelive environment as a remote site available in Salesforce as well.

    • Go to Setup > Security Controls > Remote Site Settings
    • Click New Remote Site
    • Enter "VantivPrelive" for the Remote Site Name
    • Enter https://transact-prelive.litle.com for the Remote Site URL
    • Click Save
    • Go to the Gateway Record you have set up for Vantiv
    • Make sure the Endpoint Override field of your Vantiv gateway record is set to https://transact-prelive.litle.com/vap/communicator/online
    • Uncheck the Test Endpoint checkbox

    Testing Vantiv from Salesforce


    Once you have set up the Vantiv Test Gateway record in Salesforce and the Endpoint Override / Remote Site to enable the Vantiv Prelive test environment, you are ready to run some test transactions in Salesforce.

    For detailed testing parameters, you may wish to obtain a copy of the current LitleXML Reference Guide PDF from your Vantiv Implementation Consultant. Chargent's Salesforce connection to Vantiv has already been certified, so testing is primarily to verify your Salesforce configuration and merchant credentials.

  8. Create test records in Salesforce to run test credit card transactions
    (either Chargent Order, Opportunity, or Cases records depending on which Chargent Transaction package you have installed).

    • Billing First Name, Billing Last Name, Billing Address, Zipcode should be completed
    • Total (or Amount if using Opportunities / Cases) should match what Vantiv specifies
    • Test Credit Card numbers should match what Vantiv provides below
    • Expiration Month and Expiration Year should be in the future
    • For more information on the fields required to run transactions, please see What Fields are Required? in the Chargent documentation.

    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, the current LitleXML Reference Guide PDF is available from your Vantiv Implementation Consultant, and provides detailed transaction data (name, address, amount, card numbers, etc.) and the expected responses that Vantiv will return. However, this level of testing is not required as Chargent has already certified its Salesforce pre-built integration with Vantiv.

  9. Vantiv Test Credit Cards

    10. 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 N/A
    6011010000000003 Discover 758
    6011010100000002 Discover 184
    6011010140000004 Discover 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

    Sending Live Transactions from a Salesforce Sandbox

    When Chargent is installed in a Salesforce Sandbox, transactions are always 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, the Test Endpoint checkbox on the Gateway record will select between sending to the payment gateway's live and test environments. (There are a few exceptions, such as Stripe, which has a single endpoint to send transactions to, and different credentials for live versus test transactions).

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

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

    https://transact.vantivcnp.com/vap/communicator/online

    Note that the full endpoint URL must be entered in the Endpoint Override field, and the domain must be present in the Remote Site Settings (for standard Chargent integrations it should be already present).


    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.

    Deactivate or delete the Vantiv Prelive Gateway record. Then create a new Gateway Record for your live system:

  10. Complete the Vantiv gateway record in Salesforce using the Merchant ID provided to you by Vantiv and the Presenter Credentials available in the live reporting interface:

    • Gateway Name: Any name you choose, for example "Vantiv Live"
    • Merchant ID: Username
    • Merchant Security Key: Password
    • Merchant Reference: Merchant ID provided by Vantiv
    • Active: checked
    • Test Endpoint: not checked
    • Endpoint Override: blank
    • Click Save

    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 your liability may be limited, since only a token is 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.

  11. To set up Vantiv Tokenization in Salesforce:

    • Confirm with your Vantiv Account Representative that your account is enabled for tokenization.

    • Check the Use Tokenization checkbox in the Chargent Gateway record you have set up for Vantiv

    • 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.


  12. 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. Please contact us for assistance or more information.

     

    Chargent connects Vantiv to Salesforce


     

    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 Direction Vantiv
    Gateway ID < Vantiv Payment ID
    Invoice Number > Merchant Order Number
    Invoice Number > Merchant Transaction ID
    Salesforce record ID (of Chargent Order, Opportunity, or Case) > Customer ID

    Note: If you do not populate the Invoice Number field, Chargent will autopopulate 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.