A Payment Gateway is set up for eBusiness transactions and is related to a Business Group. Each Business Group - with a few exceptions - should only have one Payment Gateway. If additional Payment Gateways are required, then multiple Business Groups may need to be configured. Speak to your implementation specialist for options in these scenarios.

3DS2 Reminder

As a part of the Payment Services Directive 2 (PDS2) security requirements from the European Union, Fonteva has accommodated the SCA (Strong Customer Authentication) by enabling 3DS2 (3D secure 2.0) as part of the previous Fonteva 20 Spring release. SCA requires that consumers authenticate with two of three categories: something you know (knowledge), something you possess (possession), or something you are (inherence). 3DS2, the next generation of 3D Secure (3DS), is a multi-factor authentication protocol used to confirm digital identity at checkout. It meets the authentication requirements for SCA.

The deadline for compliance with PDS2 is December 31st, 2020. This means that 3DS2 must be implemented by that date. Fonteva must be updated to at least 2019 R1 1.0.33 in order to implement 3DS2 and comply with SCA and PDS2. We encourage our customers to use the latest version.

To learn more about 3DS2 and SCA requirements, please read Meeting SCA Requirements With 3DS2.


It is possible to have multiple Payment Gateways set up for a Business Group, but it must be noted that only one Payment Gateway can be set up per Store (excluding PayPal) and only one Gateway type can be selected for a Payment Gateway. If your organization requires two separate Payment Gateways, then a separate Store and Site will need to be configured for each individual Payment Gateway. 

Related Documentation

To view which specific gateways are supported by Fonteva and Spreedly, please read Supported Gateways.

Payment Gateway Prerequisites: Content Security Policy (CSP)

Prior to setting up a Payment Gateway, you will need to add the Spreedly URL to your list of trusted sites on your Content Security Policy (CSP) for your Community Portal. This will enable you to successfully make transactions through Spreedly Payment Gateways.

  1. Navigate to Setup and type All Communities in the Quick Find search bar.

  2. Select All Communities from the generated results in the sidebar. The All Communities page will open.

  3. Click the Builder link for your Community Portal. The Builder will open in a new tab.

  4. Click the gear icon to open Settings. Click Security.

  5. Scroll down to the Content Security Policy (CSP) section and locate the + Add Trusted Site button.

  6. Click + Add Trusted Site. The Add Trusted Site window will open.

  7. Type Spreedly in the Name field and paste the Spreedly URL ( into the URL field.

  8. Check the Active box.

  9. Click Add Site to add the site to your list of Trusted Sites.

  10. Return to your original tab in Salesforce. Make sure you are still under Setup.

  11. Type CSP Trusted Sites in the Quick Find search bar and select CSP Trusted Sites from the results that generate.

  12. Click New Trusted Site on the table. The CSP Trusted Site Definition page will open.

  13. Type Spreedly as the Trusted Site Name and paste the Spreedly URL ( into the URL field.

  14. Make sure the Active checkbox is checked.

  15. Select All for the Context picklist field.

  16. Check all of the CSP Directives.

  17. Click Save.

Spreedly is now a trusted site for your CSP, and you are ready to begin creating Payment Gateways.

Next Steps: