VantivExpress connectors

  • Updated

Optimizely Configured Commerce has an integration with Spreedly, a global payments ecosystem, to give you access to more payment gateway options. When implementing new payment gateways on your Configured Commerce storefront, you must select a payment gateway and a payment method Spreedly supports. The previous payment connectors are no longer supported.

Optimizely Configured Commerce supports the use of Vantiv's Express payment gateway.

Settings

  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 in your Vantiv account to configure Vantiv's Express as the payment provider in Configured Commerce.
    • Live – Uses the live URL for transactions and processing charges. Set to No to use the Vantiv sandbox URL for testing transactions.
    • Live transaction/account URLs – The live URL for VantivExpress transactions. The default values are https://transaction.elementexpress.com/express.asmx and https://services.elementexpress.com/express.asmx.
    • Sandbox transaction/account URLs – The sandbox URL for testing VantivExpress transactions. The default values are https://transaction.elementexpress.com/express.asmx and https://services.elementexpress.com/express.asmx.
    • Use Payment Gateway Vault – The option to use credit card tokens from the payment gateway that can be submitted to the ERP. Enable this option only if the ERP requires the payment card token to process a transaction instead of the authorization token. The default value is Yes.

      The Payment Gateway Vault token is stored in Token2.

    • Account ID – The unique account identifier.
    • Account Token – The secret token used for authentication.
    • Acceptor ID – The unique merchant account identifier.
    • Terminal ID – The unique terminal identifier. The default value is 0001.
    • Transaction Timeout – The interval of seconds provided for a transaction to complete before the transport raises an exception. The default value is 300.
    • Application ID – The unique application identifier provided by Optimizely: 8812.
    • Prefix for Payment Account Reference Number – The string submitted as a prefix to the customer number sent to the PaymentAccountReferenceNumber field. Do not use this field unless you integrated 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.