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

When considering the existing Stripe integration for an implementation, note that it does not support 3D secure.

Stripe is a plug-in that you can configure to process payments when completing an order on your Optimizely Configured Commerce website.

Since Configured Commerce (via Tokenex) interacts with the Stripe APIs directly, you must enable the "Handle card information directly" setting in the Stripe portal for both test and production environments. Note that all card information sent to the endpoint is PCI-compliant with this setting enabled; the information is encrypted and sent via Tokenex. Neither Configured Commerce nor any customer environment receives PCI data.

Optimizely cannot test Stripe with TokenEx in Sandbox, so if you want to test it, submit a ticket.

Settings

  1. Go to Admin Console > Settings.
  2. Search for and select Payment Gateway.
  3. Select Stripe from the Payment Gateway menu.
  4. Populate the fields listed below with the criteria provided via your Stripe account to configure Stripe as the payment provider in Configured Commerce.
    Field Name Description
    Live API Secret Key

    Enter the Live API Key from Stripe into this field.

    This can be found in the Stripe Dashboard and the value begins with 'sk_live_'.
    Live API Secret Key

    Insert the Test API Key from Stripe into this field.

    This can be found in the Stripe Dashboard and the value begins with 'sk_test_'.
    Test Mode If Yes, Stripe will be in test mode and no actual transactions will take place. Default value: Yes.

    Use Payment GatewayVault

    		 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: No.

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