---
title: Strong Customer Authentication
(SCA) Support
slug: payments/strong-customer-authentication-sca-support
docTags: 
createdAt: 2026-01-08T16:11:11.317Z
---

:::hint{type="info"}
For more information on SCA, see guidance from [Financial Conduct Authority](https://www.fca.org.uk/firms/strong-customer-authentication).
:::

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](docId\:Yx2a4LiXsfJDYL7_kLfTg). 
- **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. 

::Image[]{src="https://asperato.github.io/userdocs/img/SCAConnections.png" size="66" width="689" height="571" position="center" darkWidth="689" darkHeight="571" showCaption="false"}

:::hint{type="danger"}
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.

:::ExpandableHeading{isOpen="true"}
### Ayden

1. Navigate to the **Unaric Payments Setup** tab.
2. Click on **New PSP Connection**. In the popup screen, complete the connection details:
   - Currency, i.e. GBP
   - Mode as "ECOM" or "MOTO"
   - PSP as “Adyen SCA”
   - Description - Of your choice
   - Merchant account
   - API Key - Generate API key as per the steps given here
   - Client Key - Generate Client key as per the steps given here
   - URL Prefix - Enter as \[A random string of hex-encoded bytes to make the hostname unpredictable]-\[Company Name]. Refer Adyen documentation here for more details.
3. Upon save, if the connection is established successfully, you will see a green tick besides the connection just created. Refer here for Adyen PSD2 testing guidance.
:::

:::ExpandableHeading{isOpen="true"}
### Braintree

1. Navigate to the **Unaric Payments Setup** tab.
2. Click on **New PSP Connection**. In the popup screen, complete the connection details:
   - Currency, i.e. GBP
   - Mode as "ECOM" or "MOTO"
   - PSP as “Braintree SCA”
   - Description - Of your choice
   - Merchant Id - same as used for non-sca connection
   - Public Key - same as used for non-sca connection
   - Private Key - same as used for non-sca connection
   - Click on "Save PSP Connection" button
3. Upon save, if the connection is established successfully, you will see a green tick besides the connection just created. Refer here for Braintree PSD2 testing guidance.
:::

:::ExpandableHeading{isOpen="true"}
### Cybersource

1. Navigate to the **Unaric Payments Setup** tab.
2. Click on **New PSP Connection**. In the popup screen, complete the connection details:
   - Currency, i.e. GBP
   - Mode as "ECOM" or "MOTO"
   - PSP as “Cybersource SCA”
   - Description - Of your choice
   - Merchant Id - same as used for non-sca connection
   - Security Key
   - Org Id
   - Click on "Save PSP Connection" button
3. Upon save, if the connection is established successfully, you will see a green tick besides the connection just created.
:::

:::ExpandableHeading{isOpen="true"}
### Stripe

1. Navigate to the **Unaric Payments Setup** tab.
2. Click on **New PSP Connection**. In the popup screen, complete the connection details:
   - Currency, i.e. GBP
   - Mode as "ECOM" or "MOTO"
   - PSP as "Stripe SCA"
   - Select, Use custom Gateway detail
   - Description - any of your choice
   - Secret API Key - You can get it from the stripe dashboard (via "Developers" and "API keys" on left hand menu). Refer help page: https\://dashboard.stripe.com/test/apikeys
   - Publishable Key - You can get it from the stripe dashboard (via "Developers" and "API keys" on left hand menu). Refer help page: https\://dashboard.stripe.com/test/apikeys
3. Upon save, if the connection is established successfully, you will see a green tick besides the connection just created. Refer here for Stripe PSD2 testing guidance.
:::

:::ExpandableHeading{isOpen="true"}
### Sagepay

1. Navigate to the **Unaric Payments Setup** tab.
2. Click on **New PSP Connection**. In the popup screen, complete the connection details:
   - Currency, i.e. GBP
   - Mode as "ECOM" or "MOTO"
   - PSP as “Sagepay SCA”
   - Description - Of your choice
   - Vendor name - Use same name as you have used for Sagepay (without SCA) connection.
3. Upon save, if the connection is established successfully, you will see a green tick besides the connection just created. Refer here for Sagepay PSD2 testing guidance.
:::

:::ExpandableHeading{isOpen="true"}
### Worldpay

1. Navigate to the **Unaric Payments Setup** tab.
2. Click on **New PSP Connection**. In the popup screen, complete the connection details:
   - Currency, i.e. GBP
   - Mode as "ECOM" or "MOTO"
   - PSP as “Worldpay SCA”
   - Description - Of your choice
   - API Id (iss) - From Worldpay dashboard after changing to Test mode, go to Integration->3DS Flex
   - Merchant Code - You will get it from Worldpay dashboard under Account-> Profile
   - Password - Use the XML password which can be generated by following the steps in Worldpay documentation here
   - Org Unit ID - From Worldpay dashboard after changing to Test mode you will get it under Integration->3DS Flex
   - API key - From Worldpay dashboard after changing to Test mode you will get it under Integration->3DS Flex
3. Upon save, if the connection is established successfully, you will see a green tick besides the connection just created. Refer here for Worldpay PSD2 testing guidance.
:::