{"title":"SCA requirements based on business models","category":"default","creationDate":1556539740,"content":"

This page is an overview of all PSD2 SCA requirements, organized by business model. It also shows transaction types within business models, whether these transaction types require SCA, and which payment request parameter values<\/a> to use.<\/p>\n<\/p>\n

Business models<\/h2>\n

The following table shows common business models and whether SCA is required for each type of transaction:<\/p>\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Business model<\/th>\n Transaction type<\/th>\n SCA required?<\/th>\n Payment request parameters<\/th>\n <\/tr>\n
shopperInteraction<\/code> value<\/th>\n recurringProcessingModel<\/code> value<\/th>\n <\/tr>\n
Online purchase with shopper in-session<\/td>\n \n

One-off online purchase where a shopper enters card payment details on the checkout page.<\/p>\n <\/td>\n

Yes, unless exemption applies.<\/td>\n Ecommerce<\/strong><\/td>\n <\/td>\n <\/tr>\n
\n

Online purchase where shopper agrees to store card details for future use on your website or app. This can be a zero-value transaction.<\/p>\n <\/td>\n

Yes, unless exemption applies.<\/td>\n \n Ecommerce<\/strong>\n <\/td>\n \n CardOnFile<\/strong>\n <\/td>\n <\/tr>\n
\n

Online purchase where shopper uses previously stored card payment details.<\/p>\n <\/td>\n

Yes, unless exemption applies.<\/td>\n \n ContAuth<\/strong>\n <\/td>\n \n CardOnFile<\/strong>\n <\/td>\n <\/tr>\n
Subscriptions<\/td>\n First transaction where shopper agrees to the contract. This can be a zero-value transaction. The terms and conditions should describe the policy for later subsequent charges, for example, fixed or variable amounts.<\/td>\n \n

Yes, if the first transaction is made on or after PSD2 SCA compliance is made compulsory.<\/p>\n <\/td>\n

\n Ecommerce<\/strong>\n <\/td>\n \n Subscription<\/strong>\n <\/td>\n <\/tr>\n
Subsequent subscription charges as described in the initial terms and conditions during the sign-up transaction, following equal time intervals.<\/td>\n No, this falls under

MIT<\/a>.<\/td>\n

\n ContAuth<\/strong>\n <\/td>\n \n Subscription<\/strong>\n <\/td>\n <\/tr>\n
Contracts with non-fixed time interval, such as auto account top-ups<\/td>\n Initial transaction where shopper agrees to the terms and conditions of later subsequent charges. This can be a zero-value transaction.<\/td>\n Yes, if the first transaction is made on or after PSD2 SCA compliance is made compulsory.<\/td>\n \n Ecommerce<\/strong>\n <\/td>\n \n UnscheduledCardOnFile<\/strong>\n <\/td>\n <\/tr>\n
Subsequent charges as described in the initial terms and conditions during the sign-up transaction, following non-fixed time intervals.<\/td>\n No, this falls under

MIT<\/a> provided that the cardholder is off-session at the time when the charge occurs.<\/td>\n

\n ContAuth<\/strong>\n <\/td>\n \n UnscheduledCardOnFile<\/strong>\n <\/td>\n <\/tr>\n
One-off account status check<\/td>\n Transaction with a zero-value authorization to validate the shopper's account status.<\/td>\n Generally does not require SCA.<\/td>\n \n Ecommerce<\/strong>\n <\/td>\n <\/td>\n <\/tr>\n
Transaction with a USD\u00a01 authorization, for issuers that do not accept zero-value authorization.<\/td>\n Generally requires SCA, unless exemption applies.<\/td>\n \n Ecommerce<\/strong>\n <\/td>\n <\/td>\n <\/tr>\n
Purchase through MOTO<\/a><\/td>\n \nMail Order \/ Telephone Order transaction. For example, a shopper calls a travel agency and the agent initiates a transaction.\n <\/td>\n \nNo, this transaction is out of scope of PSD2 SCA.\n <\/td>\n \n Moto<\/strong>\n <\/td>\n <\/td>\n <\/tr>\n
Purchase through POS<\/td>\n Regular purchase at a payment terminal in a store<\/td>\n This is a shopper-present transaction where shopper performs SCA in-store, for example, through chip-and-pin authentication.<\/td>\n \n POS<\/strong>\n <\/td>\n <\/td>\n <\/tr>\n
Authorization adjustment<\/td>\n Transactions submitted with the Classic\/adjustAuthorisation<\/a> or Checkout\/amountUpdates<\/a> endpoint, used for example in tipping scenarios.<\/td>\n No, this falls under

MIT<\/a>.<\/td>\n

<\/td>\n <\/td>\n <\/tr>\n <\/tbody>\n <\/table>\n

Payment request parameters<\/h2>\n

Use the following values for shopperInteraction<\/code> and recurringProcessingModel<\/code> parameters:<\/p>\n