Exemptions to Strong Customer Authentication
There are some e-commerce transactions which are out of scope of the regulation, and others that may be exempt.
Obtaining Strong Customer Authentication can add friction and increase Customer drop-off and therefore you should make use of exemptions to reduce the number of times you will need to authenticate a Customer.
However, the bank has the right to refuse any requested exemption and decline the payment insisting that SCA be obtained. Refer to the SCA Soft-Decline section for further information on this soft decline.
Exemptions must be agreed with your Acquirer prior to use.
The following exemptions are available:
Mail Order / Telephone Order Payments
Card details collected via mail or over the phone (MOTO) fall outside of the scope of SCA and do not require authentication.
You can flag such payments by passing a value of ‘2’ in the type and 'consumer' in the initiator request fields.
Merchant Initiated Transactions (including recurring transactions)
Payments made with saved cards when the Customer is not present in the payment flow may qualify as Merchant Initiated Transactions. These payments fall outside of the scope of SCA however it is still up to the bank to decide whether authentication is needed for the payment.
The initial payment that saved the card will still need to have obtained SCA or be exempt and agreement must be obtained from the Customer to charge their card at a later point.
You can flag such payments by passing a value of '2' (Customer Not Present) or ‘9’ (Continuous Authority) in the type request field and 'merchant' in the initiator request field. You should also use the rtAgreementType request field to provide the reason for the transaction.
Low Value Exemption
Payments below €30 are considered low value and are generally exempt from authentication. However, if the Customer initiates more than five consecutive low value payments or if the total payments value exceeds €100) then SCA will be required.
You can request this exemption by passing a value of ‘lowvalue’ in the scaExemption request field, or it may be automatically applied by the Issuer.
Trusted Beneficiary Exemption
The Customer can opt to trust you as a Merchant during their first authentication, then subsequent payments with you are likely to be exempt from future SCA.
You can request this exemption by passing a value of ‘trusted’ in the scaExemption request field to allow this trust to be taken into consideration.
For a subset of Acquirers when processing Visa transactions, you must also send the schemeMerchantID which is an 8 digit value that Visa assigns. If you are unsure of this value, you must check this with your Acquirer. This can be sent for other schemes but will be ignored.
Trusted Risk Analysis (TRA) Exemption
If the payment provider, having in place effective risk analysis tools, assesses that the fraud risk associated with the payment is low then they can allow this exemption.
You can request this exemption by passing a value of ‘risk’ in the scaExemption request field if agreed to by the payment provider.
Secured Corporate Payment Exemption
Payments initiated by a business rather than a Consumer and processed through a secured dedicated payment protocol can be exempt from SCA provided alternative controls are sufficiently secure.
You can request this exemption by passing a value of ‘corporate’ in the scaExemption request field to indicate such a secure transaction.
Delegated Authentication Exemption
If you already require your Customers to perform sufficient authentication on your website, such as secure account logins etc, then you can use this exemption to request that further SCA is not required.
You can request this exemption by passing a value of ‘delegated’ in the scaExemption request field to indicate such a secure transaction.
For a subset of Acquirers when processing Visa transactions, you must also send the schemeMerchantID which is an 8 digit value that Visa assigns. If you are unsure of this value, you must check this with your Acquirer. This can be sent for other schemes but will be ignored.