Request an authentication for an initial recurring payment.
This API endpoint triggers a 3-D Secure (3DS) authentication without processing a payment. It is used to verify a customer’s identity before completing a transaction or for regulatory compliance (e.g., Strong Customer Authentication - SCA).
The customer must be on-session to complete the authentication. Commerce utilizes the action_requirement mechanism to request any necessary interaction with the customer. The interactions are supported with SDKs. See the SDK documentation for more information.
The amount given in minor units (e.g. use 700 for 7€). Some currencies do not support minor units (e.g. Japanese Yen). In this case send in the full value, .i.e. 100 for 100 JPY.
x >= 0The date when the recurring should expiry.
Indicates the minimum number of days between authorisations.
The payment credentials for this authentication request.
| Type | Description |
|---|---|
| token | An already existing Commerce token can be used as source for the authentication. |
The preference with respect to an eventual challenge.
There is no guarantee that the preference can be fulfilled.
CHALLENGE, NO_PREFERENCE, NO_CHALLENGE The data when the purchase was made. Requires the
format yyyyMMddHHmmss and defaults to now.
The ID of the merchant for whom the authentication is requested
Authentication created
The ID of the authentication
The amount given in minor units (e.g. use 700 for 7€). Some currencies do not support minor units (e.g. Japanese Yen). In this case send in the full value, .i.e. 100 for 100 JPY.
x >= 0The date-time the authentication was created (following ISO 8601)
PROCESSING, COMPLETED, FAILED The payment credentials for this authentication request.
| Type | Description |
|---|---|
| token | An already existing Commerce token can be used as source for the authentication. |
ONE_OFF, INITIAL_RECURRING, INITIAL_INSTALLMENT, SUBSEQUENT_RECURRING, SUBSEQUENT_INSTALLMENT The final result of the authentication. It holds in the cardholder authentication data (CAVV) and if there is a network token present, the token authentication data (TAVV).
The preference with respect to an eventual challenge.
There is no guarantee that the preference can be fulfilled.
CHALLENGE, NO_PREFERENCE, NO_CHALLENGE The date when the latest subsequent authentication can happen.
Requires the format yyyyMMdd.
Indicates the minimum number of days between authentications.
The reasons why an authentication failed during processing in Commerce.
The date-time the authentication was finished (following ISO 8601)
The ID of the original authentication in case of subsequent authentications
The ID of the merchant for whom the authentication is requested
Indicates the maximum number of authorisations permitted for installment payments.
The data when the purchase was made. Requires the
format yyyyMMddHHmmss and defaults to now.