What is Strong Customer Authentication? #
The European Payment Services Directive (PSD2) aims to provide more secure credit card transactions and protect cardholders from fraud by adding an extra layer of security to customer-initiated transactions (CIT). This is called Strong Customer Authentication (SCA).
SCA is a two-factor authentication requirement wherein, during a consumer-initiated transaction (CIT), the cardholder must provide two of the three elements:
- Something the cardholder knows (such as passwords, passphrases, PIN, sequences, and secret facts)
- Something the cardholder owns (such as cellphones, smartwatches or other wearable devices, smart cards, tokens, and badges)
- Something the cardholder Is (fingerprints, facial recognition, voice patterns, iris format, and DNA signatures)
SCA works with Customer Initiated Transactions (CIT), so when you use Chargent’s Payment Request feature or Take Payments in Communities, the person entering the credit card will receive a pop-up asking them to authenticate in order to process the payment The SCA authentication is a process dictated by their issuing bank. For some banks, you must log in using your Username and Password; for others, the issuing bank may use a key generator to authenticate on your mobile device or computer.
SCA currently works with the Adyen Gateway. You will need to work with your Adyen to have SCA enabled on the gateway side.
- Adyen – Once enabled with Adyen, you won’t need to enable it within your Salesforce Gateway Record. SCA is built into the Adyen integration and will automatically detect EU merchants and EU Credit Cards.
What Chargent Features Use SCA? #
Payment Requests: When you send a Payment Request, the customer will receive a link to a payform. When they enter in their credit card information, they will receive a pop-up notification asking for authentication.
Take Payments Component in Communities: The Take Payments component is part of our Platform Edition. It allows you to add a payform within your community site. Your users can access their account information, allowing them to sign in to your community portal and pay using your payform.
Testing SCA #
Each Gateway uses its own 3DS test credit card numbers to allow for testing before rolling it out. These are different from the test credit cards provided for standard testing. You should always test in Sandbox before rolling out to Production in order to make sure all customizations still work as expected in your Org.
Testing via Payment Request
To test using a Payment Request, you want to be sure you have the Chargent Payment Request feature set up as outlined in our documentation.
- Click Send Payment Request
- If you have multiple Payment Request templates set up, you will first choose what template you want to use.
- Enter an email address where you want to send the test Payment Request and any amount.
- Enter a Contact name (Optional)
- Click Send Request
When you receive the email, click the secure link for the Payment Request. Use one of Adyen’s test credit cards to complete the payform and submit the payment.
When you click Pay, you will see a pop-up asking you to authenticate by entering in a password or whatever your issuing bank uses for verifying it’s you making the payment. This is the second layer of security using SCA.
Once you submit your authentication, you will receive a message stating, ‘Your payment was submitted successfully’.
Adyen Test Credit Cards
|Card Type||Card Number||Expiry Date||Security Code|
|Visa||4917 6100 0000 0000||03/2030||737|
|Visa||4212 3456 7891 0006||03/2030||737|
|Mastercard||5212 3456 7890 1234||03/2030||737|
|American Express||3714 4963 5398 431||03/2030||7373|
|Discover||6011 1111 1111 1117||03/2030||737|
|Diners||3056 9309 0259 04||03/2030||737|