VantivExpress connectors

  • Updated

The Optimizely Configured Commerce engineering team now has an integration with Spreedly, a global payments ecosystem. The addition of Spreedly grants clients access to more payment gateway options. Clients implementing new payment gateways on their Configured Commerce storefront must select a payment gateway and a payment method that Spreedly supports.

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 > Settings.
  2. Search for and select "Payment Gateway".
  3. Select VantivExpress from the Payment Gateway menu.
  4. Populate the following setting fields with the criteria provided via your Vantiv account to configure Vantiv's Express as the payment provider in Configured Commerce.
    Setting Name Description/Value
    Live If 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 URLs The Live URL used for Vantiv transactions. Default value:
    Sandbox transaction/account URLs The Sandbox URL for testing VantivExpress transactions. Default value:
    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 ID Unique account identifier.
    Account Token Secret token used for authentication.
    Acceptor ID Unique merchant account identifier.
    Terminal ID Unique terminal identifier. Default value: 0001
    Transaction Timeout Interval of time in seconds provided for a transaction to complete before the transport raises an exception Default value: 300
    Application ID Unique application identifier provided by Insite: 8812
    Prefix for Payment Account Reference Number The string in this field will be submitted as a prefix to the customer number sent to the PaymentAccountReferenceNumber field. This field should not be populated in most instances, unless you are integrating with the Eclipse ERP.

Transaction types

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

  • Credit
  • Void
  • Capture
  • Authorization
  • Sale

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