SCA is not required for an authorization adjustment or for subsequent payments related to a subscription or contract. However, the initial authorization or the first transaction for the subscription or contract does require SCA.
Requirements
Before you begin, take into account the following requirements:
| Requirement | Description |
|---|---|
| Integration type | An online payments integration. |
MIT
Card schemes refer to payments initiated by merchants (instead of directly by shoppers) as merchant-initiated transactions or MIT. Payments made to adjust the initial transaction made by a shopper or subsequent payments in a subscription or contract fall under the scope of MIT.
To ensure that a transaction can be correctly classified as MIT, subsequent payments or authorization adjustments must be linked to the first payment using a network transaction reference.
Authorization adjustments
The pre-authorization transaction requires SCA, but any transaction made to adjust the amount of the pre-authorized amount or to extend the validity of the initial payment is classified as MIT, exempting it from SCA compliance.
Adyen automatically sends the additionalData.networkTxReference when you adjust the pre-authorized amount or extend the validity of the authorization.
Subscriptions and contracts with non-fixed time intervals
The first payment in a subscription or a contract falls under the SCA because the shopper initiates the transaction. This means that SCA is required on the sign-up for a series of Subscription or UnscheduledCardOnFile payments. All subsequent payments in a subscription or a contract are classified as MIT and do not fall under the scope of SCA compliance.
How the subsequent payments are linked to the first payment depends on how you tokenize card details.
