Simulate assisted 3DS authentication - OTP 2FA
Simulate Assisted 3DS authentication - OTP 2FA allows you to emulate the behavior of an assisted 3D Secure verification process. This facilitates testing and validation of your integration’s handling of authentication flows, ensuring a smoother user experience during real-world transactions.
Prerequisites
- The partner program has already been enabled and configured for Assisted 3DS authentication — OTP 2FA.
- The partner must subscribe to the following webhook to receive the payload containing the OTP that will need to be passed to the end-user.
| Webhook message sent by the MatchMove platform containing the authentication details based on the enabled 3DS authentication mode configured for the program. |
API Workflow
Note:
The set of endpoints below is only available and enabled in the staging environment.
These endpoints allow you to simulate Initate Card Authentication, Resend Card Authentication, and Verify Card Authentication, and test Assisted 3DS Authentication - OTP 2FA before the live environment.
1
Initiate a card authentication request
The Simulate Initiate Card Authentication (POST /simulate/cards/authentication/start) will simulate an authentication request for an OTP code.
This API will trigger the platform to send a CARDS.3DS.AUTHENTICATION webhook to your backend.
Request parameters:
card_id- Required. Card ID.challenge_method- Required. Verification method. Allowed value:otptype- Required. OOB category. Allowed value:email,sms
Simulate Initiate Card Authentication request
curl --location 'https://{{cards_simulation_base_url}}/{{program_code}}/v1/simulate/cards/authentication/start' \
--header 'X-Auth-User-ID: 08dcfa7946874386a3c081571efc0abc' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic ==' \
--data '{
"card_id": "{{card_id}}",
"challenge_method": "otp",
"type": "email"
}'
Simulate Initiate Card Authentication response (success)
{
"message": "authentication started and email otp sent successfully",
"transaction_authentication_id": "01a1ab48-269b-7620-9978-9c6eaf6d3f98"
}
Simulate Initiate Card Authentication response (card network validation error)
{
"id": "0cbf291b-7b86-480f-a185-77fbba14fde0",
"status": 400,
"code": "missing_required_param",
"title": "Parameter validation failed",
"detail": "card_network is a required field",
"timestamp": "2023-05-18 12:57:19.107844122 +0000 UTC"
}
Simulate Initiate Card Authentication response (invalid card error)
{
"id": "0cbf291b-7b86-480f-a185-77fbba14fde0",
"status": 400,
"code": "card_not_supported",
"title": "Unsupported Card",
"detail": "Currently card is not supported",
"timestamp": "2023-05-18 12:57:19.107844122 +0000 UTC"
}
2
Resend another card authentication request
The Simulate Resend Card Authentication (POST /simulate/cards/authentication/resend) will simulate a fresh authentication request for an OTP code. This process is needed when the previous OTP has expired and is invalid for authentication.
This API will re-trigger the platform to send a CARDS.3DS.AUTHENTICATION webhook to your backend.
Request parameters:
transaction_authentication_id- Required. Transaction ID received from Simulate Initiate Card Authentication response.
Simulate Resend Card Authentication request
curl --location 'https://{{cards_simulation_base_url}}/{{program_code}}/v1/simulate/cards/authentication/resend' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
"transaction_authentication_id":"fc35d12cc5c14b3187fbee26368467d9"
}'
Simulate Resend Card Authentication response
{
"message": "Message resent"
}
3
Verify the card authentication request
The Simulate Verify Card Authentication (POST /simulate/cards/authentication/verify) will simulate the verification of the 3DS OTP code entered by the customer. This OTP must be the same OTP that was sent and received in any of the allowed communication channels.
Request parameters:
transaction_authentication_id- Required. Transaction ID received from Send OTP Responsetransaction_authentication_value- Required. This is the 3DS OTP that was received from the end-user (the OTP sent through the allowed communication channels). Must be of length = 6.
Simulate Verify Card Authentication request
curl --location 'https://{{cards_simulation_base_url}}/{{program_code}}/v1/simulate/cards/authentication/verify' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
"transaction_authentication_id":"fc35d12cc5c14b3187fbee26368467d9",
"transaction_authentication_value":"595347"
}'
Simulate Verify Card Authentication response (success)
{
"message": "Verification done"
}
Simulate Verify Card Authentication response (invalid OTP)
{
"id": "0cbf291b-7b86-480f-a185-77fbba14fde0",
"status": 400,
"code": "invalid_value_param",
"title": "Parameter validation failed",
"detail": "transaction_authentication_value contains invalid value",
"timestamp": "2023-05-18 12:57:19.107844122 +0000 UTC"
}
Related Links
On this page
- Simulate assisted 3DS authentication - OTP 2FA