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

Orbital, a Chase provided payment gateway, is a plug-in that you can configure to process payments when completing an order using Optimizely Configured Commerce. For specific product information on Orbital, provided by Chase, you can review their website.


  1. Go to Admin Console > Settings.
  2. Search for and select "Payment Gateway".
  3. Select Orbital from the Payment Gateway menu.
  4. Populate the following fields with the criteria provided via your Orbital account.

    There are several settings that need to be configured prior to using Orbital as a payment gateway. The information for these settings should come from your Orbital service representative.

    Application Setting Description
    Connection Username The connection username for the Orbital account.
    Connection Password The connection password for the Orbital account.
    Live If Yes, the live URL will be used for transactions and charges will be processed. Set to 'No' to have transactions use the Orbital sandbox URL for testing. Default value: No
    Live URL

    The Live URL used for Orbital transactions. Default value: https://ws1.chasepaymentech.com/PaymentechGateway

    Sandbox URL The Sandbox URL for testing Orbital transactions. Default value: https://wsvar1.chasepaymentech.com/PaymentechGateway
    Merchant ID Gateway merchant account number.
    BIN Transaction routing definition
    Terminal ID

    Merchant Terminal ID. Default value: 001

    Use Payment Gateway Vault If YES, 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.

All settings are global with the exception of Merchant ID, BIN and Terminal ID, which can be set uniquely per website.

Transaction types

The following transaction types are 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.