Merchants need to collect high-quality and richer data, such as the device information used by customers when shopping, facial recognition, location data, etc. to assist the issuing bank to make more accurate trading risk decisions.

In 3DS 2, if the relevant data can support the risk decision, the customer does not need to verify in other ways. At this time, the customer has no perception of verification. When the customer needs to enter an OTP or a static password, the page does not need to be forced to redirect and can be seamlessly embedded in the merchant application.

In the 3DS 1 verification process for compulsory authentication of page turn, customers often encounter various problems when paying; The verification code was not received, and the page of the consumer did not turn back to the merchants page after the verification. The mobile terminal could not automatically adapt, resulting in a low conversion rate. 3DS 2 supports multiple terminals, complete transaction security authentication without forced page turn.