Vantiv/Litle/WorldPay VAP Configuration

Payment Provider	Geographies	Currencies	Payment Methods	Retain Support	Automatic Chargeback Feed	Account Updater	API Version	Microservice?
Vantiv/Litle/WorldPay VAP Payment Processor	Global	All	Credit/Debit Cards -Yes SEPA DD- No Tokenized Credit Card- Yes Hosted Pages - No Alternative Payments - No Digital Wallets - Yes, Apple Pay	Tokenized Credit Card - Yes Detokenize PAN - No Detokenize BIN- No Partial Auth - Yes Forced Deposit - Yes	Yes	YesReal -Time AU also supported if merchant-enabled	V9, V12	No

Required Merchant Information

[

](../images/Vantiv.xlsx)

Name	Expected Value	Description
Litle:divisionNumber	ex. 12345	Merchant division ID from processor. Can be used in routing.
Litle:reportGroup	ex. US_group	Merchant report group from processor. Can be used in routing.
Litle:tokenizedPaymentMethods	0/1	Set to 1 if merchant will send tokens to Retain.
XML VersionLitle:xml_v12	0/1	The version of Litle XML in use. Set to 1 if XML version 10 or above is used
Does provider need to whitelist IPs	No
Does the merchant need to authorize Vindicia as a presenter on their MID(s)	- Vindicia Token User: VINDICIATKN - Vindicia Credit Card (i.e. non-Token) User: VNDCIA - Vindicia Chargeback Retrieval User: VINDICIA	Provide the following information to Litle to allow Vindicia to submit payments on your Litle merchantIds: - Vindicia Token User: VINDICIATKN - Vindicia Credit Card (i.e. non-Token) User: VNDCIA - Vindicia Chargeback Retrieval User: VINDICIA Enable all of Vindicia’s users to submit on all your merchantId’s. Enable the Chargeback datafeed for Vindicia on all Litle merchantIds for the Vindicia Chargeback Retrieval User.
Chargeback feed	Yes
Account Updater	Yes
Real-Time account Updater	Yes	If Real-time account updater was enabled by merchant on their merchant instance (for V9 and V12)

Desired Merchant Configuration

Name	Value	Comments
Litle:AUDisabled	0/1	Disable AU requests
Litle:AU_period	Recommended is ‘2’	Regularly scheduled sweep for AU, typical is quarterly (2)
Litle:AU_prebill	Recommended is ‘8’	Days before billing to send AU request
Litle:customerServiceNumber		Cust service number from billing descriptor
Litle:mccNumber		Merchant Commerce Code from billing descriptor
Litle:IntlAuthAmountDivisionNumbers		Divisions listed will use a $1 auth instead of a$ 0 auth for all card types. Mostly used for EU/UK merchants. Can be comma-separated list.
Litle:auth_response_priority		Note: Relevant for merchants using XML 12 only (see required configuration above) The order that authorization response codes are prioritized when deciding to retry Transactions. Supported Authorization Response Codes: Payment Provider Response (P), MAC (M) - Mastercard Merchant Advice codes, and Network Response (N)
fraudfilteroverride	true/false	The capability to override (disable) Worldpay Litle Fraud filters during transaction submission or authorization

Parent topic:Payment Provider Specific Configuration

Vantiv/Litle/WorldPay VAP Merchant Setup Instructions

The following Instructions are written for Vindicia CTS and services delivery staff. To configure a merchant to use Vantiv (Litle) payment processor:

Merchant Payment Providers

In Subscribe Portal 1.0, using you’re admin account, go to Admin > Merchant Configurations.
Select the relevant Merchant from the drop-down list.
Click Edit Merchant Configurations.
Enter the Jira Ticket # for configuring your merchant payment setup.
Add Litle to Merchant Payment Providers:
Payment Provider Name Account Number PP Type Active
Litle (1011) <Merchant Id> (Must remove leading ‘0’s) BRD(1) 1
Litle (1011) <Merchant Id> (Must remove leading ‘0’s) Chargeguard(2)
1. Select Litle (1011) as the payment provider and click ADD.
2. Leave Account Number blank.
3. Set PP Type as BRD.
4. Set Active to 1.
5. To enable the chargeback feed, select Litle (1011) as the payment provider and click ADD.
6. Set PP Type as Chargeguard(2).
7. Set Active to 1.

Payment Provider Name	Account Number	PP Type	Active
Litle (1011)	<Merchant Id> (Must remove leading ‘0’s)	BRD(1)	1
Litle (1011)	<Merchant Id> (Must remove leading ‘0’s)	Chargeguard(2)

Routing Rule

Add a Routing Rule for Vantiv (Litle).
Ordinal Payment Provider Value Rule Method Active
1 Litle (1011) default_method(1) 1
1. Select Litle (1011) as the payment provider and click ADD.
2. Add an Ordinal value of 1.
3. Leave Value blank.
4. Add a Rule Method value of default_method(1).
5. Set Active to 1. Note: If the test payment provider is configured, set its Active value to 0.

Ordinal	Payment Provider	Value	Rule Method	Active
1	Litle (1011)		default_method(1)	1

Note: If a merchant account is set up with several payment providers, the payment provider with highest Ordinal value has priority. If routing will be shared amongst payment providers, see Configuration Method - Payment Providers Routing Rules for examples of possible configurations.

Name/Value Pairs

The below api_key value is an example for Vindicia internal testing and should not be shared with merchants.

ID	Name	Value
100000527	Litle:divisionNumber	!division_name%4230552
100000622	Litle:reportGroup	ReportGroupName
100000866	Litle:customerServiceNumber	800-742-3653
100005608	Litle:tokenizedPaymentMethods	0
100010592	Litle:divisionNumber:4230553	4230553
100010593	Litle:divisionNumber:4229343	4229343
100010594	Litle:divisionNumber:4230549	4230549
100010600	Litle:divisionNumber:4230550	423550
10010601	Litle:divisionNumber:4230551	423551
10010602	Litle:divisionNumber:423552	423552

Parent topic:Vantiv/Litle/WorldPay VAP Configuration

Vantiv/Litle/WorldPay VAP Detailed Information on Integration

Vindicia supports the following Payment Operations for Vantiv (Litle):

Payment Operation	Yes/No	Notes
Standard Implementation Features
Verification (no Auth)	Yes
Minimal Authorization ($0) policies, by card type)	Yes
AVS check with standard result mapping	Yes
CVV/CVN check with standard result mapping	Yes
Support real-time authorization (stand-alone Auth)	Yes
Void	Yes
Conditional deposit (auth and capture combination)	Yes
Capture (stand-alone capture)	Yes
One-time transactions (real-time)	Yes
Recurring transactions (flagged recurring)	Yes
Refunds - Full	Yes
Refunds - Partial	Yes
3DS	No
CITMIT/Card On File	Yes
Map error/response/result codes to standard actions (Success/Decline/Reject)	Yes
Special Implementation Features
Implemented via Payments Microservice	No
Retrieve and store paymentProcessorTransactionId	Yes	Litle uses Vindicia transaction ID.
Retrieve and store Extended Card/Auth Attributes	Yes
Support tokenization (for Retain)	Yes
Support BIN/Last-4/Expiry Retrieval from external Token	No	Merchant should provide BIN in the API
Support detokenization (Subscribe retrieves full PAN/CC details	No
Support Card Type identification (from BIN or API)	No
Support Visa/general “Stored Credential” flags	Yes
Account Updater/Amex Card refresher	YesAlso supports Real-time Account Updater if merchant-enabled	See NVP for RT AU enablement
Automated/manual chargeback feed	Yes
Retain Support
Support token as payment method	Yes
Support detokenization to full PAN	No
Support detokenization to get BIN	No
Support Partial Authorization	Yes
Support Forced Deposit	Yes
Parent topic:Vantiv/Litle/WorldPay VAP Configuration

Home

Guides

APIs

Required Merchant Information

Desired Merchant Configuration

Vantiv/Litle/WorldPay VAP Merchant Setup Instructions

Merchant Payment Providers

Routing Rule

Name/Value Pairs

Vantiv/Litle/WorldPay VAP Detailed Information on Integration

​Required Merchant Information

​Desired Merchant Configuration

​Vantiv/Litle/WorldPay VAP Merchant Setup Instructions

​Merchant Payment Providers

​Routing Rule

​Name/Value Pairs

​Vantiv/Litle/WorldPay VAP Detailed Information on Integration

Required Merchant Information

Desired Merchant Configuration

Vantiv/Litle/WorldPay VAP Merchant Setup Instructions

Merchant Payment Providers

Routing Rule

Name/Value Pairs

Vantiv/Litle/WorldPay VAP Detailed Information on Integration