3-D Secure support

The existing interfaces support 3-D Secure.

Integration	3-D Secure	Alias	Merchant action
Payment Page	✔️	✔️	Apply 3-D Secure
Split Mode	✔️	✔️	Apply 3-D Secure
Mobile SDK	✔️	✔️	Apply 3-D Secure
Secure Fields	✔️	✔️	Apply 3-D Secure
Server to Server only - Alias for CIT	❌	✔️	See one click check out below
Server to Server only - Alias for MIT	⚠️	✔️	Ok, if 3-D Secure is applied at time of creation of Alias.

One Click Checkout

Merchants offering one click checkout often apply the following pattern:

Initial registration with or without 3-D Secure by creation of an Alias in order to register the payment method.
On payment, Alias gets applied by a Server to Server interface.

❗️
Not PSD2 and SCA compliant
Cardholder initiated transactions (CIT) require SCA.

3-D Secure has to be applied for creation of an Alias and registration of a payment method.
3-D Secure has to be applied at each cardholder initiated transaction. Server to server only does not support 3-D Secure.

👍
Merchant action
Switch to an integration supporting 3-D Secure and Alias. Apply 3-D Secure at creation and charge of an Alias.