📘
Q: Why transaction on 3DS 1.0 is denied?
A: As we know, 3DS 1.0 is already outdated and is mostly decommissioned on mid-October 2022.
Some transactions using 3DS 1.0 may still be successfully authenticated, but it will potentially be denied/rejected by the Acquiring bank, Issuing bank, or Principle because 3DS 1.0 is not supported anymore.

📘
Q: Why transaction on 3DS 1.0 is still successful?
A: As we know, 3DS 1.0 is already outdated and is mostly decommissioned on mid-October 2022. But some Acquiring banks and Principles (such as Visa, Mastercard, JCB, or Amex) still accept 3DS 1.0
To avoid sudden drop-off transactions if at any time 3DS 1.0 is no longer supported, we recommend Merchant to immediately use 3DS 2.0 implementation

📘
Q: Why transaction is still routed to 3DS 1.0?
A: There are some possible reasons why a transaction is still routed to 3DS 1.0:

Card issuer doesn't support 3DS 2.0

Acquiring Bank and Principle still doesn't support 3DS 2.0

Channel doesn't support 3DS 2.0 (resolved on Midtrans side by migrating to channels that support 3DS 2.0).

Timeout to 3DS Server or Principle during 3DS 2.0 Process, which will initiate fallback flow to 3DS 1.0

Merchant still creates token with secure parameter (Old Flow). To enable 3DS 2.0 Merchant needs to create token without secure parameter and send Authentication: true on Charge Request.

📘
Q: After migrating to 3DS 2.0, why are there customer complaints of being stuck when opening the OTP Page?
A: There are some possible reasons:

Customer doesn't have a stable connection.

There is an issue on the OTP Page provided by the Issuing bank.

The service is currently degraded on Midtrans, please contact support@midtrans.com.

Merchant may not be following of our official guideline/docs for integration correctly.

Most of our merchants don't experience this issue by following our official guideline/docs for implementation on their native mobile apps, which can be implemented using the following options:

Using Midtrans mobile SDK UIKit flow.

Using Webview to display Snap integration.

Using Webview to display Core API web-based Card payment flow (PCI Lisence required).

Please refer to 3DS 2.0 Implementation

📘
Q: Any specific 3DS 2.0 migration date for each Acquiring Bank and Principle?
A: 3DS 2.0 Migration schedule:
Host to Host:

BNI Visa - 26 Sept 2022

CIMB Visa & Mastercard - 26 Sept 2022

MTI Mandiri Visa & Mastercard - 11 Oct 2022

Mega Visa - 12 Oct 2022

BNI Mastercard - 17 Oct 2022

Mega Mastercard - 17 Oct 2022

MPGS:

Migrate MIGS BCA to MPGS BCA - 27 Sept 2022

Migrate MIGS BRI to MPGS BRI - 7 Oct 2022

MIGS:

Maybank Visa & Mastercardd - 29 Sept 2022

Cybersource:

CIMB Visa & Mastercard - 26 Sept 2022

BCA Visa, Mastercard, and Amex - 28 Sept 2022

BRI Visa & Mastercard - 28 Sept 2022

BNI Visa & Mastercard - 28 Sept 2022

All JCB Acquiring bank - 18 Oct 2022

📘
Q: If Merchant has 2 MIDs with same Acquiring bank on different channels, which channel will be used?
A: Transactions will be routed based on channel prioritization.
Currently Core API has six channels sorted by priority:
Channel Available
DRAGON ✅
MTI ✅
MIGS ✅
CYBERSOURCE ✅
BRAINTREE ✅
MPGS ✅

📘
Q: Is it possible if Merchant send specific bank and channel on Charge request?
A: For this inquiry, please contact support@midtrans.com