The Optimizely B2B engineering team will evaluate, design, and develop connectors to support nearly any payment gateway that a client chooses but requires at least 120 days of notice before a new connector will be available for implementation and testing by the client or its implementation partner.
The B2B Commerce Cloud platform is an extendable SaaS solution that provides an out-of-the-box B2B Commerce solution that can be extensively customized to the needs of each client by an implementation partner.
Connectors to third-party applications are an important aspect of the customization of the platform.
Expectations for non-payment connectors
For most connectors, the implementation partner is responsible for the evaluation, design, development, implementation, and testing of the connector.
Although the Optimizely team has created several connectors to common ERP, PIM, tax, and other data providers, these connectors should serve as a starting point, only, upon which the implementation partner may need to extend further to fit the unique needs of each client.
Expectations for payment gateways
The one exception to this above process is payment gateways. Payment gateways that allow for the use of credit cards must be implemented in a specific way to ensure PCI compliance.
As such, the Optimizely team will own the design and development of the credit card portion of payment gateways to ensure PCI compliance. The implementation partner will still be responsible for the implementation and testing of the credit card portion of each payment gateway.
Those payment gateways that support credit card payments typically also support other payment types, including eCheck, ACH, SEPA, etc. In this case, Optimizely may choose to create a connector that supports multiple payment types.
However, the ultimate responsibility for the design and development of non-PCI scope payment methods and non-PCI scope aspects of the gateway (such as frontend design of credit card payments) rests with the implementation partner. Implementation partners must avoid any change to the base code, as such changes may have an impact on the PCI compliance of the connector.
For those payment gateways that have no PCI scope, such as an eCheck, ACH, or SEPA payment gateway, the implementation partner is responsible for the evaluation, design, development, implementation, and testing.
How to request a new payment gateway
Optimizely encourages each client to select the payment gateway the best fits their unique needs.
Although Optimizely has created connectors to several payment gateways, clients may request support for a new payment gateway or additional functionality within an existing payment gateway. Requests should be made to your Onboarding Engagement Manager, Customer Success Manager, or Partner Manager, who will be able to create a ticket for our engineering team and provide periodic updates.
Once the request has been submitted to the Optimizely engineering team, our team will evaluate whether the payment connector can be implemented in a PCI compliant manner.
If so, our team will aim to have the connector available for implementation and testing within the client’s environment within 120 days (about 4 months). As such, we recommend requesting support for a new payment gateway as soon as possible and, ideally, immediately after the sales contract has been signed. Expedited requests will be considered on a case-by-case basis and may require an additional fee.
If the selected payment gateway cannot be implemented in a PCI compliant manner, Optimizely reserves the right to decline support for that payment gateway.