In order to make payments using 3-D Secure 2, there are some changes on the integration to take account of.

The main enhancements of EMV 3DS 2.0 compared to 3DS 1.0 are:

  • Support of in-app purchases on mobile phone and other customer devices.
  • Enable merchants to integrate the authentication process into their checkout experiences, for both app and browser-based implementations.
  • Enable the issuing banks to perform risk-based decisions on the transaction authorization that enables frictionless consumer authentication when the customer is not required to perform an additional authentication to the bank.
  • Enables non-payment customer authentication that allows services like Identification & Verification (ID&V) for mobile wallets and secure request of tokens for card on file.

OPP COPYandPAY

For users of COPYandPAY, minimal additional effort is required compared to the current integration. The workflow is identical to the current 3D Secure 1.0 implementation. OPP COPYandPAY will handle the entire additional communication and will be responsible for collecting required browser based information automatically.
Following data must be collected by the merchant and send in via

  • Server/Server, create checkoutId
  • being collected by adding additional input fields to the payment widget

table

CommentFileSizeAuthor
2019-12-03_17-12-58.png78.8 KBjrochate

Comments

jrochate created an issue. See original summary.

agoradesign’s picture

agoradesign commented
Status: Active » Fixed

Thank you Joao for this detailled feature request, that makes it easy to review existing features and identify missing ones. The good news is: we are already sending every necessary information. In order to raise the chance of frictionless payment flow, we are even sending other information like shipping information (if available), full name, IP address,..

The card holder is collected via widget then, so there's no need to ask that information before on the Drupal side

Here's the code to review: https://www.drupal.org/project/commerce_opp/issues/3098483

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.