Strong Customer Authentication (SCA) Support
For more information on SCA, see guidance from Financial Conduct Authority.
You will be able to use the SCA ready connections without a package upgrade. All you need to do is to create a new connection from Unaric Payments Setup tab.
Supported SCA
The following PSPs support SCA.
- Adyen
- Braintree (A Paypal company)
- Checkout.com
- Cybersource
- Stripe
- Sagepay
- Worldpay
SCA behaviour for internal agents (MOTO vs ECOM)
When processing card payments internally, the SCA behaviour depends on the payment route being used.
ECOM route
If an internal agent is prompted by SCA, with OTP or 3D Secure challenges while creating an Authorisation, this indicates that the payment is being processed via the ECOM route. The ECOM route enforces SCA and will require authentication when applicable.
MOTO route
For internal agent workflows where SCA is not required, payments should be processed using the MOTO route, which does not require 3D Secure authentication. You can initiate a MOTO payment in the following ways:
- From the Payment record UI Use the Process Payment button on the payment record. This automatically routes the transaction as MOTO. See Process Payments.
- Via flows or custom integrations If you are generating payment URLs programmatically (for example, from Salesforce flows or custom automation), you must explicitly route the payment as MOTO. To do this, add the following parameter to the ECOM payment URL: DLcnp=jdi. When this parameter is present, the payment is processed via the MOTO route and SCA (3DS / OTP) is not required.
Setup SCA connection
For SCA support, you need to create a new connection from Unaric Payments Setup tab. For PSD2 supported PSPs you will find a new PSP in the list with SCA appended to it.
Some cards require authentication every time a transaction is made. For such cards, future payments will fail.
Below are the instructions for setting up SCA on supported PSPs.