Configure a Test Payment Gateway
Configure a Test Payment Gateway
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.
Navigate to the Business Group record that will be linked to the new Payment Gateway.
Scroll Down to the Payment Gateways related list and click New. The Payment Gateway configuration page will open.
Enter a name in the Payment Gateway Name field. It's recommended you include "Test" in the name to remind you that this Payment Gateway is a test.
Click the Business Group lookup field and select your Business Group from the selections that generate.
Optional configurations can be selected to add different settings to your Test Gateway. They are as follows:
Supported Credit Cards Image: Click Browse to browse for a file on your machine or enter an image URL to display credit card icons on the community portal checkout page. This image should be 30px tall and up to 500px wide.
There is a default image configured for all Gateways that displays an image with Visa, Mastercard, Discover, and American Express on the checkout page in the portal, but it will not display in the Supported Credit Card Images field. It can only be accessed by right-clicking the image form the Store's checkout page and selecting Open Image in New Tab. Any image that you upload in the Supported Credit Card Image field will override this default image - so long as the checkout page is a Lightning Events Checkout Page. Work is currently underway to resolve this issue for Visualforce Checkout Pages.
Check the Require CVV (i.e., security code), Require Email and/or Require Phone checkboxes for gathering further information on the credit card holder.
Check Enable 3D Secure to use 3D Secure 2.0 (3DS2).
Spreedly supports the following Payment Gateways for 3DS and 3DS2.
Check Offsite to test offsite payments (e.g., allowing users to pay with their Paypal accounts).
When testing offsite payments, the tester will be redirected to an external page, which allows the tester to see what different responses from the system will be when a live transaction is processed.
AVS Configuration has the following options:
Validate Billing Address - Requires the user to populate the City, State, Street, Zip, and Country fields.
Validate Postal Code - Requires the user to populate only the Zip field.
Disable AVS - The entire Billing Address section will not be visible in the New Payment Method modal.
Click Connect to a Test Gateway to create your Test Gateway.
Your Test Gateway is now set up and ready to use for purchases made in the staff view. When you set up your Store(s), you will link to the Test Gateway to test community portal checkout.
If you are using Paypal or Direct Debits, you will need to set up a Custom Payment Type on the Store before the new payment tab will appear in the community portal. Follow the steps on the Adding a Custom Payment Type page.
Next Steps:
Test credit cards for your test payment gateway are available here.
When you’re ready to create a live payment gateway, directions are available on Configure A Live Payment Gateway.
If you have enabled 3DS2 for your test payment gateway, you will need to create a Merchant Profile. Directions are available on the Merchant Profile and SCA Provider Key page.
To learn more about 3DS2 and SCA requirements, please read Meeting SCA Requirements With 3DS2.