Payment Gateway Development Expectations PDF

Payment gateway development expectations Updated 22 days ago FollowNot yet followed by anyone Optimizely Configured Commerce is an extendable SaaS platform that provides an out-of- the-box commerce solution that an implementation partner can customize to your needs. Third...

Payment gateway development expectations Updated 22 days ago FollowNot yet followed by anyone Optimizely Configured Commerce is an extendable SaaS platform that provides an out-of- the-box commerce solution that an implementation partner can customize to your needs. Third-party application connectors are an important aspect of platform customization. Optimizely owns the design and development of the payment gateway's credit card portion to ensure compliance with Payment Card Industry (PCI). Implementation partners are responsible for implementing and testing the credit card portion of each payment gateway. Payment gateways that support credit card payments typically also support other payment types, including eCheck, ACH, SEPA, and so on. Optimizely may choose to create a connector that supports multiple payment types in these cases. However, implementation partners are ultimately responsible for the design and development of non-PCI-scope payment methods and non-PCI-scope aspects of the gateway, such as the front-end design of credit card payments. Implementation partners must avoid any change to the base code, as such changes may impact the connector's PCI compliance. Implementation partners are responsible for evaluating, designing, developing, implementing, and testing payment gateways without PCI scope, such as eCheck, ACH, or SEPA gateway. Spreedly payment platform Configured Commerce integrates with Spreedly, a global payments ecosystem. Spreedly gives you access to more payment gateway options. See Configure Payment Service to set up this integration. Clients implementing payment gateways on their storefront must select a payment gateway and a payment method Spreedly supports. Although the existing Spreedly integration with Configured Commerce supports Spreedly’s payment gateways and payment methods, clients or partners must submit a Support ticket to indicate their interest in implementing a Spreedly-supported payment gateway. In rare cases, Optimizely must add additional settings to the Admin Console for the specific payment gateway. During the implementation process, have your partner submit a Support request for your intended payment gateway. You can also send requests to your Onboarding Engagement Manager or Customer Success Manager, who will create a ticket for the Optimizely engineering team and provide periodic updates. When submitted, Optimizely will take up to two months to test your payment gateway and, if necessary, add additional settings to the Admin Console. New payment gateways require an upgrade to the most recent version of Configured Commerce. If the selected payment gateway cannot be implemented with Spreedly or in a PCI- compliant manner, Optimizely reserves the right to decline support. Old payment gateways Existing clients that have already implemented an old Optimizely-supported payment gateway can continue using that payment gateway and the associated connector for the foreseeable future. However, Optimizely does not intend to provide future feature enhancements to the old payment gateways. If you require a new feature on the old payment gateway, you must change to a Spreedly-supported payment gateway. Spreedly with Classic sites The Spreedly integration is available for Spire sites only. If your site is on Classic, use the library of existing payment gateways until you upgrade to Spire. Transaction usage for Spreedly Your Spreedly total transaction count for a given year is directly tied to the number of transactional orders on your Configured Commerce subscription. If you have any questions, check the service definition or check with your Customer Success Manager. Payment gateway development expectations Updated 22 days ago  FollowNot yet followed by anyone Optimizely Configured Commerce is an extendable SaaS platform that provides an out-of- the-box commerce solution that an implementation partner can customize to your needs. Third-party application connectors are an important aspect of platform customization. Optimizely owns the design and development of the payment gateway's credit card portion to ensure compliance with Payment Card Industry (PCI). Implementation partners are responsible for implementing and testing the credit card portion of each payment gateway. Payment gateways that support credit card payments typically also support other payment types, including eCheck, ACH, SEPA, and so on. Optimizely may choose to create a connector that supports multiple payment types in these cases. However, implementation partners are ultimately responsible for the design and development of non-PCI-scope payment methods and non-PCI-scope aspects of the gateway, such as the front-end design of credit card payments. Implementation partners must avoid any change to the base code, as such changes may impact the connector's PCI compliance. Implementation partners are responsible for evaluating, designing, developing, implementing, and testing payment gateways without PCI scope, such as eCheck, ACH, or SEPA gateway. Spreedly payment platform Configured Commerce integrates with Spreedly, a global payments ecosystem. Spreedly gives you access to more payment gateway options. See Configure Payment Service to set up this integration. Clients implementing payment gateways on their storefront must select a payment gateway and a payment method Spreedly supports. Although the existing Spreedly integration with Configured Commerce supports Spreedly’s payment gateways and payment methods, clients or partners must submit a Support ticket to indicate their interest in implementing a Spreedly-supported payment gateway. In rare cases, Optimizely must add additional settings to the Admin Console for the specific payment gateway. During the implementation process, have your partner submit a Support request for your intended payment gateway. You can also send requests to your Onboarding Engagement Manager or Customer Success Manager, who will create a ticket for the Optimizely engineering team and provide periodic updates. When submitted, Optimizely will take up to two months to test your payment gateway and, if necessary, add additional settings to the Admin Console. New payment gateways require an upgrade to the most recent version of Configured Commerce. If the selected payment gateway cannot be implemented with Spreedly or in a PCI- compliant manner, Optimizely reserves the right to decline support. Old payment gateways Existing clients that have already implemented an old Optimizely-supported payment gateway can continue using that payment gateway and the associated connector for the foreseeable future. However, Optimizely does not intend to provide future feature enhancements to the old payment gateways. If you require a new feature on the old payment gateway, you must change to a Spreedly-supported payment gateway. Spreedly with Classic sites The Spreedly integration is available for Spire sites only. If your site is on Classic, use the library of existing payment gateways until you upgrade to Spire. Transaction usage for Spreedly Your Spreedly total transaction count for a given year is directly tied to the number of transactional orders on your Configured Commerce subscription. If you have any questions, check the service definition or check with your Customer Success Manager.