While EMV 3DS has many benefits, adoption may be slow in the regions where EMV 3DS is not mandatory. Reasons may include the following: Data inconsistency. The quality of merchant data provided in EMV 3DS plays a critical role in issuer fraud detection. Merchants may be reluctant to share more data and may decide to provide a minimum set of data elements excluding optional data elements. There are cases when the data provided is not accurate, causing issues in fraud engines. Approval rates and cardholder friction. Shopping cart abandonment has been one of the major reasons that EMV 3DS adoption is low. Many enhancements have been added to the protocol from EMV 3DS 1.0 to EMV 3DS 2.x to challenge the cardholder only when needed. Complexity of integration. EMV 3DS integration is complex and adds an additional layer of authentication flow before authorization, resulting in higher implementation costs. Most systems are built with synchronous authorization request and response; EMV 3DS is a major change since it requires an asynchronous transaction processing flow with multiple steps. Liability shift. EMV 3DS is designed to help with fraud. However, determining if, how and when a liability shift occurs for merchants is not a simple answer and depends on several factors. Payment network and local regulatory requirements should be checked for specific use cases to assess any applicable liability shifts. Some factors are: Region and payment network. It is important to be familiar with payment network rules for EMV 3DS usage. Merchant category code (MCC). Not all MCCs are allowed for a liability shift.