Disclaimer: This website requires Please enable JavaScript in your browser settings for the best experience.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide

InsiteConnect for VantivExpress

Describes InsiteConnect for VantivExpress in Optimizely Configured Commerce.

Optimizely Configured Commerce supports the use of Vantiv's Express payment gateway. This article calls out the required Settings for proper configuration.

  1. Go to Admin Console > System > Settings.
  2. Search for and select "Payment Gateway".
  3. Select VantivExpress from the Payment Gateway menu.
  4. Populate the setting fields listed below with the criteria provided via your Vantiv account:

The following Settings are used to configure Vantiv's Express as the payment provider in Configured Commerce.

Setting NameDescription/Value
Payment GatewaySelect VantivExpress from the menu
LiveIf Yes, the live URL will be used for transactions and charges will be processed. Set to No to have transactions use the Vantiv sandbox URL for testing. Default value: No
Live transaction/account URLsThe Live URL used for Vantiv transactions. Default value:`https://certtransaction.elementexpress.com/express.asmx`
Sandbox transaction/account  URLsThe Sandbox URL for testing VantivExpress transactions. Default value:`https://certtransaction.elementexpress.com/express.asmx`
Use Payment Gateway Vault

Enables using credit card tokens from the payment gateway that can be submitted to the ERP. This option should only be enabled if the ERP requires the payment card token to process a transaction as opposed to the authorization token. Default value: Yes.

The Payment Gateway Vault token is stored in Token2.

Account IDUnique account identifier.
Account TokenSecret token used for authentication.
Acceptor IDUnique merchant account identifier
Terminal IDUnique terminal identifier. Default value: 0001
Transaction TimeoutInterval of time in seconds provided for a transaction to complete before the transport raises an exception Default value: 300
Application IDUnique application identifier

Transaction types

The following transaction types are can be triggered from within Configured Commerce when completing or updating a transaction.

  • Credit
  • Void
  • Capture
  • Authorization
  • Sale

️ IMPORTANT

Configured Commerce does NOT store sensitive credit card or profile information.