Vantiv eCommerce Sandbox

Document created by gjsissons on May 10, 2016•Last modified by bfinn on Jan 4, 2019

Version 20Show Document

Like • Show 1 Like1
Comment • 16
View in full screen mode

Vantiv has multiple environments that developers can use to progress an application integration from development, through the certification process and onto production. These include our Sandbox environment, the Pre-Live environment and the Post-Live environment. (see links below)

An overview of Vantiv's various environments is included in the document Certification and Testing environments.

The Vantiv eCommerce Sandbox Environment

The eCommerce Sandbox functions as a simulator of our production environment. Developers can send transactions to the sandbox environment the exact same way you’d send them to our certification or production systems.

The Sandbox validates the transaction format and approves it if it matches our requirements. The Sandbox server makes it easy to get started using our SDKs or XML endpoints. There are no forms to fill out, no credentials required, and no special access needed.

The endpoint for our Sandbox environment is: https://www.testvantivcnp.com/sandbox/communicator/online

A working example of an authorization using the sandbox endpoint is provided below. You should be able to run this on any platform with internet access that support cURL and Linux / UNIX bash including OS/X. The values provided in the authentication tags do not matter for the Sandbox. Similarly, values provided in the authorization tag are ignored.

#!/bin/sh
curl
 https://www.testvantivcnp.com/sandbox/communicator/online
 --tlsv1.2 \

 -H "Content-Type: text/xml; charset=UTF-8" \
 -X POST \
 -d \
 '<?xml version="1.0"?>
 <litleOnlineRequest version="8.10" xmlns="
http://www.litle.com/schema
" merchantId="default">

 <authentication>
 <user>MyStore</user>
 <password>VantivR0ck$</password>
 </authentication>
 <authorization id="ididid" reportGroup="Money2020" customerId="12345">
 <orderId>1</orderId>
 <amount>1000</amount>
 <orderSource>ecommerce</orderSource>
 <billToAddress>
 <name>Jane Doe</name>
 <addressLine1>20 Main Street</addressLine1>
 <city>San Jose</city>
 <state>CA</state>
 <zip>95032</zip>
 <country>USA</country>
 <email>
my-email-address@vantiv.com
</email>

 <phone>978-551-0040</phone>
 </billToAddress>
 <card>
 <type>MC</type>
 <number>5454545454545454</number>
 <expDate>1112</expDate>
 <cardValidationNum>123</cardValidationNum>
 </card>
 </authorization>
 </litleOnlineRequest>'

Assuming your device is able to reach the sandbox endpoint, you should receive a response like the one below from the Sandbox.

<litleOnlineResponse version='8.10' response='0' message='Valid Format' xmlns='
http://www.litle.com/schema
'>

 <authorizationResponse id='ididid' reportGroup='Money2020' customerId='12345'>
 <litleTxnId>571289423901768000</litleTxnId>
 <orderId>1</orderId>
 <response>000</response>
 <responseTime>2017-03-16T12:42:43</responseTime>
 <message>Approved</message>
 <authCode>47767</authCode>
 </authorizationResponse>

The example above shows a test card data being passed inside the <card> XML tags. Additional information about test card numbers for the sandbox is provided below. For developers who want to reduce PCI scope and avoid directly handling and transmitting card holder data, you can use Vantiv's eProtect service (formerly known as paypage) and submit a low-value token that represents vaulted payment card credentials instead. For details, consult the eProtect Integration Guide.

IMPORTANT: PLEASE DO NOT USE REAL CARD NUMBERS WHEN TESTING AGAINST THE SANDBOX

The eCommerce Sandbox supports online transactions only and needs at least version 8 of cnpAPI. It has no state and doesn't actually tie the transactions with one another, but it does simulate responses for tied transactions. To test your batch transactions, you'll need access to our "Pre-Live" environment.

The Vantiv eCommerce Pre-Live Environment

Once you have applications working in the Sandbox, you can request access to our Pre-Live environment for additional testing. You can request an account here. All you need is your e-mail address and organization name. After you register for an account in the Pre-Live environment you will receive an e-mail with four pieces of information:

The on-line test URL: https://transact.vantivprelive.com/vap/communicator/online
A Merchant Id
A Username to authenticate to the pre-live environment
A Password to authenticate to the pre-live environment

The same test script above can be adapted to use the Pre-Live environment by updating the endpoint, ensuring that the valid Username and Password values are entered in the <authentication> tag, and passing the proper Merchant Id (referred to as the "id") in the <authorization> tag.

The Prelive environment uses a simulator for responses. There are specific test cards that produce specific test responses. Please see the XML Reference Guide Section 2.4.1 for the specific test cards. Any test card sent into the Pre-live environment that is not listed in the XML Reference Guide and passes mod10 will Approve.

Sandbox environment features

The Sandbox uses the request to calculate the response. This is done so that any response that our systems can generate can be retrieved through the Sandbox as well. For Sale and Auth transactions, the last three digits of the credit card will be used for the response reason code. Some sample numbers/responses include:

Desired response	Credit card number
000: Approved	4470330769941000
010: Partially Approved	4658512425423010
100: Processing Network Unavailable	4215176886320100
101: Issuer Unavailable	4215176886320101
110: Insufficient Funds	4488282659650110

Other numbers in the credit card can be used to simulate a variety of features, including AVS, CVV, Auto AU, etc. To identify the feature, characters two to four are used and depending on the feature, other characters will be used. The following shows how we count the characters from the card number and highlighted in green are the three character feature identifiers.

A simple example is the following card number:

Characters: 0123456789012345

4100280190123000

The green characters specify the feature (in this case Vault). The red characters specify the token response code. The blue digits specify the response reason code, as explained above.

So for example, to simulate a transaction that will respond with insufficient funds, we can use a different test card number (a VISA card in this case) ending in the digits 110 as below:

#!/bin/sh
curl
 https://www.testvantivcnp.com/sandbox/communicator/online
 --tlsv1.2 \

 -H "Content-Type: text/xml; charset=UTF-8" \
 -X POST \
 -d \
 '<?xml version="1.0"?>
 <litleOnlineRequest version="8.10" xmlns="
http://www.litle.com/schema
" merchantId="default">

 <authentication>
 <user>MyStore</user>
 <password>VantivR0ck$</password>
 </authentication>
 <authorization id="ididid" reportGroup="Money2020" customerId="12345">
 <orderId>1</orderId>
 <amount>1000</amount>
 <orderSource>ecommerce</orderSource>
 <billToAddress>
 <name>Jane Doe</name>
 <addressLine1>20 Main Street</addressLine1>
 <city>San Jose</city>
 <state>CA</state>
 <zip>95032</zip>
 <country>USA</country>
 <email>
my-email-address@vantiv.com
</email>

 <phone>978-551-0040</phone>
 </billToAddress>
 <card>
 <type>VI</type>
 <number>4488282659650110</number>
 <expDate>1118</expDate>
 <cardValidationNum>123</cardValidationNum>
 </card>
 </authorization>
 </litleOnlineRequest>'

As expected, this script responds with a message indicating there are insufficient funds to process the transaction.

<litleOnlineResponse version='8.10' response='0' message='Valid Format' xmlns='
http://www.litle.com/schema
'>

 <authorizationResponse id='ididid' reportGroup='Money2020' customerId='12345'>
 <litleTxnId>149986033714496110</litleTxnId>
 <orderId>1</orderId>
 <response>110</response>
 <responseTime>2017-03-16T12:55:49</responseTime>
 <message>Insufficient Funds</message>
 </authorizationResponse>

The following table shows all the features available and the meaning for the special characters. You can try with different values for each one of them and check the responses that you get back.

Example Card Number	Feature Identification	Feature	Other characters
4100117890123000	001	Account Updater	Nothing needed, new randomly generated card number will be returned
4100280140123000	002	Vault/Tokenization	5-7 - Token response code
4100322311199000	003	Enhanced Authorizations	5 - Funding Source Type 6 - Reloadable 7 - Prepaid card type 8 - Affluence 9 - Issuer Country
4200410886320101	004	Address Verification (AVS)	5-7 - AVS response code
4100521234567000	005	Card Security Code Validation	5 - Card validation result

The Sandbox and Apple Pay

Use a three-digit amount to specify the desired responses, Some sample numbers/responses include:

Desired response	Transaction amount
000	Approved 000
010	Partially Approved 010
100	Processing Network Unavailable 100
101	Issuer Unavailable 101
110	Insufficient Funds 110

For Apple Pay, when the amount is not in this table or not a three digit number, the transaction will automatically be approved and return '000' as the response code, 'Approved' as the response message.

Learning more

Documentation about the Sandbox and other Vantiv certification environments are provided in the Certification and Test Environment guide.

The URL to send your transactions to our Sandbox is the following:

https://www.testvantivcnp.com/sandbox/communicator/online

Sample XML transactions and command lines using curl are provided on the eCommerce GitHub site that exercise the Sandbox.

http://vantiv.github.io/sandbox

Attachments

Outcomes

16 Comments

tovermier Nov 16, 2017 8:45 AM
The link to request a pre-live account is broken.
Like • Show 0 Likes0
Actions
- Worldpay Bot @ tovermier on Nov 17, 2017 10:06 AM
  Thanks Travis for notifying us.
  
  brian.arnold or gjsissons have we made changes to the this end point? https://www.testlitle.com/sandbox
  Like • Show 0 Likes0
  Actions
brian.arnold Nov 17, 2017 10:45 AM
Hi,
The URL for the eCommerce Sandbox has changed. We have updated the links on Vantiv ONE, but certainly may have missed a couple.
The new URL is: https://www.testvantivcnp.com/sandbox
If you can let me know where the URL is still incorrect I will make sure it gets updated ASAP.
Thanks,
Brian
1 person found this helpful
Like • Show 1 Like1
Actions
- tovermier @ brian.arnold on Nov 17, 2017 1:29 PM
  Sure, it is this link.
  
  Also, I've attempted to register for a sandbox account a few times and it appears to work (says I should check my email for a username and password), but I never get the email. I also checked the spam folder.
  Like • Show 0 Likes0
  Actions
  - brian.arnold @ tovermier on Nov 21, 2017 12:03 PM
    Hi Travis,
    Can you please contact sdksupport@vantiv.com? We will be able to help with recovering the prelive accounts you created through that channel.
    Thanks!
    Brian
    Like • Show 0 Likes0
    Actions
cswycliffe Apr 4, 2018 8:13 AM
cjennings The link http://vantiv.github.io/sandbox/#howItWorksis pointing to the wrong place even though the text is right. I think it should be

Developers | Vantiv
Like • Show 0 Likes0
Actions
- Worldpay Bot @ cswycliffe on Apr 4, 2018 8:26 AM
  Thank you CS. I’ll make sure the link navigates to the top of the GitHub page when redirected.
  
  Regards,
  Chris
  1 person found this helpful
  Like • Show 0 Likes0
  Actions
aandrew12 Apr 5, 2018 3:58 PM
I went on https://vantiv.github.io/sandbox/ and the information about submitting curl commands with a proxy is incomplete.
Like • Show 0 Likes0
Actions
- Worldpay Bot @ aandrew12 on Apr 11, 2018 11:35 AM
  Thanks for letting us know Antonio. I will pass this along to our eComm team that manages the GitHub account.
  Like • Show 0 Likes0
  Actions
- swapnil.hande @ aandrew12 on Apr 12, 2018 7:28 AM
  Hi Antonio, the missing curl commands with proxy have been added to the vantiv.github.io page. Thanks.
  Like • Show 0 Likes0
  Actions
cbae Apr 19, 2018 6:35 PM
We want to be able to test both eProtect and payments in a pre-live environment that is currently configured to reject SSL/early TLS protocols.

The pre-live environment that we have already been set up on is:
https://payments.vantivprelive.com/vap/communicator/online
rather than the URL indicated in this document:
https://transact.vantivprelive.com/vap/communicator/online

Is the "payments" subdomain pre-live environment already configured to reject the deprecated protocols?
Like • Show 0 Likes0
Actions
tboumil Apr 20, 2018 8:30 AM
Support for SSL3 and TLS1.0 in the test environments was switched off in February.
Like • Show 0 Likes0
Actions
tuntunaung05 Jun 5, 2018 3:05 PM
I am testing eCommerce Pre-Live Environment and it return nothing Like below "Message: <br>Vantiv eCommerce Transaction ID: ". I manage to run the code in Sandbox environment.

My code is written in PHP and running on CentOS server. I run using this command "php xxxx.php".
Please let me know anything I need to change to get the proper response.

litle_SDK_config.ini
user =u82923312652451874
password =EvfwCxHF26LgMV2
currency_merchant_map ['DEFAULT'] =01380155
url =https://transact.vantivprelive.com/vap/communicator/online
proxy =
batch_requests_path =testdir
litle_requests_path =testdir
sftp_username =
sftp_password =
batch_url =
tcp_port =
tcp_timeout =
tcp_ssl =1
print_xml =0
timeout = 500
reportGroup = Default Report Group

Response
<?xml version="1.0" encoding="utf-8"?>
<litleOnlineRequest merchantId="01380155" version="11.0" merchantSdk="PHP;11.0" xmlns="http://www.litle.com/schema">
<authentication>
<user>u82923312652451874</user>
<password>EvfwCxHF26LgMV2</password>
</authentication>
<sale reportGroup="Stratcom" id="1">
<orderId>123213</orderId>
<amount>106</amount>
<orderSource>ecommerce</orderSource>

<billToAddress>
<name>Jane Doe</name>
<addressLine1>20 Main Street</addressLine1>
<city>San Jose</city>
<state>CA</state>
<zip>95032</zip>
<country>USA</country>
<email>my-email-address@vantiv.com</email>
</billToAddress>

<card>
<type>VI</type>
<number>4488282659650110</number>
<expDate>1118</expDate>
<cardValidationNum>123</cardValidationNum>
</card></sale>
</litleOnlineRequest>
Message: <br>Vantiv eCommerce Transaction ID:
Like • Show 0 Likes0
Actions
danielon87 Jun 5, 2018 3:17 PM
can you help me try the payment method with PHP SDK does not let me do the test for test
Like • Show 0 Likes0
Actions

higherlink Aug 6, 2018 1:12 PM

I have been looking through a lot of PDFs and all I am looking for is what this ID field is for and what should be put in it.
Is there a reference guide for all the Fields? I am using PHP and your SDK.

id="ididid"

I am using your sample

$sale_info = array(
   'reportGroup' => 'Default Report Group',
   'id' => '456',
   'orderId' => '1',
   'amount'  => '10010',
   'orderSource' => 'ecommerce',
   'billToAddress' => array(
      'name' => 'John Smith' ,
      'addressLine1' => ' 1 Main St.',
      'city' => 'Burlington' ,
      'state' => 'MA' ,
      'zip' => '0183-3747',
      'country' => 'US'),
   'card' => array(
      'number' => '5454545454545454',
      'expDate' => '0112',
      'cardValidationNum' => '349',
      'type' => 'MC' )
);
$initialize = new litle\sdk\LitleRequest();
$saleResponse =$initialize->saleRequest($sale_info);

$ret = new stdClass();
$ret->response = (litle\sdk\XmlParser::getNode($saleResponse,'response'));
$ret->message = litle\sdk\XmlParser::getNode($saleResponse,'message');
$ret->transaction_id = litle\sdk\XmlParser::getNode($saleResponse,'litleTxnId');

Actions

tboumil @ higherlink on Aug 7, 2018 5:45 AM
Take a look at Worldpay cnpAPI Reference Guide API 12.8 V2.7 .
We use the id attribute for duplicate transaction detection. You will find it mentioned in section 1.4.2 of the guide. Chapter 4 provides definitions for all elements and attributes. The attribute definitions are in tables under the parent element (e.g., sale, authorization, capture, etc.).

Tom
Like • Show 0 Likes0
Actions