Evo 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.

Evo is a payment service you can configure and customers can use when completing orders in Optimizely Configured Commerce. You typically enable this at the global level, but you can also enable it for a specific subsite, if desired.


There are several settings to configure prior to using Evo as a payment gateway. To configure these settings, first follow these steps.

  1. Go to Admin Console > Settings.
  2. Search for and select "Payment Gateway".
  3. Select Evo from the Payment Gateway menu.
  4. Populate the fields shown below, and then click Save.

The following settings are used to configure Evo as a payment service in Configured Commerce.

Name Value
Device ID The Device ID for your Evo Payments account. Include the starting number and colon.
Device Password The Device Password for your Evo Payments terminal used for integration.
Test Mode Turning this option on will use the Evo Payments est URL. Turning this option off will use the production URL. The default is On.
PFP/Gateway Name The PFP is available from the Name/Setup ID field of your gateway in PayFabric.
Use Payment Gateway Vault This option, when set to Yes, enables using credit card tokens from the payment gateway that can then 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. The default value is No.

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