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

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

This option uses Paystand’s IFrame rather than TokenEx. To update this setting, you need to submit a Support ticket request to update your Sandbox environment with the Payment Gateway IFrame value set to Paystand. Once updated, your Sandbox’s IFrame across all sites uses the Paystand IFrame, and you can no longer use TokenEx. Follow the same process for your production environment when you want to go live.

Due to data incompatibility across iframes, changing to a different iframe (such as TokenEx, Paymetric, Square Drop-in, or Adyen Drop-in) deletes all existing saved payment methods for all web users.


  1. Go to Admin Console > System > Settings. 
  2. Search for and select Payment Gateway
  3. Ensure that Paystand is populated in the Payment Gateway menu (this should have automatically set when the IFrame was set). 
  4. Populate the following fields with the criteria provided via your Paystand account. 
Field Name  Description 
Client Secret  The Client Secret from Paystand. Default Value: Blank 
Client Id  The Client ID from Paystand. Default Value: Blank 
Customer Id  The Customer ID from Paystand. Default Value: Blank 
Publishable Key  The Publishable Key from Paystand. Default Value: Blank 
Live  If Yes, Paystand live endpoints will be used for transactions and charges will be processed. Set to 'No' to have transactions use the Paystand sandbox endpoints for testing. Default value: No 

Paystand transaction types 

Since the Paystand functionality does not have the concept of authorization or void transactions, Paystand transactions are handled differently than is usual in Configured Commerce: 

  • All credit card transactions are treated as a sale. The Credit Card Transaction Treated as a Sale setting in the Payment area of Order Management settings will alter the Paystand functionality as follows: 
    • If set to Yes, Paystand saves the card and captures the transaction as part of the order process. 
    • If set to No, Paystand only saves the card as part of the order process and  does not submit a transaction. Use this option to complete order processing via an ERP or internal system integrated with Configured Commerce. 

    This appears as an authorization in Configured Commerce, but since Paystand does not do authorizations, this should be interpreted as being only a saved card. Since this "authorized" transaction is like a save, it requires the user to capture the transaction first before being able to credit. 

  • Paystand always saves the card, regardless of settings in Configured Commerce. 
  • Since Paystand does not support void transactions, this option is not available in Configured Commerce. 

Important notes

  • For the Paystand IFrame to function properly in Configured Commerce, the country codes in Configured Commerce and the country codes that Paystand uses in the IFrame need to match - if they do not, it results in an error upon selection.
  • Card transactions requiring Admin Console entry are unavailable when using the Paystand gateway.
  • Configured Commerce does not currently support storefront saved cards functionality for the Paystand gateway, and any previously saved cards from other IFrames (i.e., TokenEx) will no longer be accessible via the storefront once Paystand is selected. 

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