Vantiv/Litle Payment Processor Configuration

Summary

This article describes how to configure Vantiv as a token card processor in EngageIP. This integration is not iBiz based.

Vantiv Token card processing works by taking the credit card number, expiry date and security number and converting it to a token which can be used for regular processing so that the card number is not sent across networks every time sales are processed. Address information is NOT stored within the data represented by the token however, so for vantiv, there is an AVS rate and non AVS rate. To get the AVS rate, you will need to have AVS checked in your credit card type to get the preferred rate. With that in place, EngageIP sends the customer name and address along with the Vantiv token for sales and refunds. If AVS is NOT enabled, the address is not sent with the request and you fall back to the non preferred Vantiv rate for processing credit cards.

Testing

Sandbox Environment

Notice: Vantiv test servers and live servers are IP restricted, so if you see an error communicating, check with Vantiv support that the external IP of your test or production system is known and registered with them otherwise EngageIP will not be able to communicate at the URL entered.

Vantiv offers a sandbox environment (simulator) that provides a basic interface for functional level testing of transaction messages. Typically, merchants using one of the available Software Development Kits (SDKs) would use the Sandbox to test basic functionality. This is a stateless simulator, so it has no historical transactional data, and does not provide full functionality. This environment is not intended for certification or regression testing.

See the page http://vantiv-ecommerce.github.io/sandbox/ for details on how to use the Vantiv sandbox.

Testing via EngageIP

In the Card Processor Configuration specify:

Gateway URL: https://www.testlitle.com/sandbox/communicator/online
Attribute: enter the Litle/Vantiv supplied username

Visa numbers can be taken from the sandbox page linked to above. There are card numbers to trigger successful processing and card numbers to trigger different kinds failures, so if you're just looking to test successes, pick the appropriate card number and add it to a user in EngageIP.

Configuration

Token Card Processor Configuration

Create a Card Processor called 'Token Processor' (required so that the card type can be created)

1. In the AdminPortal load the Setup tab

2. Click on Card Processors and configure it as displayed below:

   

3. Click Save

Card Type Configuration

Create the Card Type and assign the Token Processor to it

1. On the Setup tab click on Card Types

2. Click Add

3. Set the Card Name, Type and Processor

   

   Note: you must enable AVS (Address Verification System) if you wish to send data to Level3 in the Credit Card Token Processors configuration

4. Click Save

Credit Card Token Processor Configuration

1. On the Setup tab click on Credit Card Token Processors

2. Click Add

3. Set the Attribute (Vantiv supplied username), Merchant Login (merchantid), Password and the Gateway URL (either Live or Test URL)

   

4. Click Save

Payment Type Configuration

Create a Payment Type and associate it with the Token Processor

1. On the Setup tab click on Payment Types

2. Click Add

3. Set the Name and the Payment Type (must be 'Credit Card Token')

   

   4. Click Save

Testing

To test your configuration:

1. Load a test account in the AdminPortal

2. Click on the Tools tab and then Payment Methods

3. Click Add

4. Select Credit Card Token

5. Populate the required card details and click Save

6. You should see a message indicating the creation was successful, or a failure error

7. If the creation was successful submit a test payment to make sure it goes through (you can refund this amount from the Tools tab as well)

8. When the test payment is made, load the Reports tab and check the Payments report, it should show your test and include the approval code and transaction number

   

Vantiv Payment Reconciliation

To reconcile payments between Vantiv and EngageIP:

1. Access the Vantiv transaction report

2. Log in to EngageIP and click on the Reports tab

3. Under the Owner Reports section click on the Payments report

4. The Transaction Number column vs. the 'Vantiv Payment ID' field should match

5. To filter the report to return the needed results click the Date column and enter the Min (start) and Max
(end) date that matches the period the Vantiv transaction report covers

6. Further filter the list by clicking the Payment Type column and selecting the appropriate payment type
(i.e. 'Credit Card') to filter out other payment results (cash, wire transfer, etc.)

7. Once you have the list filtered down to include only payments made through Vantiv you can compare
the report total (Amount column) vs. the total on the Vantiv transaction report to reconcile payments

Troubleshooting

Some cases come up where there are issues processing or updating credit cards, those scenarios will be listed here as they are encountered:

Card expiry date is reset/will not update when adding a new credit card

If you've added a credit card initially with an incorrect expiry date, Vantiv will have already generated a token with the incorrect expiry date. Adding the card again with a new expiry date may not work (the expiry date of the existing token on file with the same token ID may be used). To permit the expiry date update in situations where the expiry date was added incorrectly initially do the following

1. Ensure you have access to log into the Vantiv portal

2. Contact Vantiv support to have them reveal a hidden button in the portal which temporarily disables the auto updating feature of the expiry date (and the rest of the token info).

3. Log into the Vantiv portal and click the revealed button so that the token can be updatedNote: this feature will turn itself off after one token update 

Changing MID Values (Account Name)

If you need to switch MIDs or Usernames and you need to refund a payment, simply login to the Vantiv gateway using the old account, refund it manually and then add a correcting transaction to EngageIP. Going forward, cards processed using new MID will be able to be refunded as long as they were initially processed with that MID