3D Secure 2.x - Frictionless Transactions & Method URL
HTML-код
- Опубликовано: 30 дек 2023
- 3DS Secure 2.x has a cool feature called Frictionless transactions, which facilitates the Issuers (and participants) to skip the 2nd factor (Challenge Request), thus leading to less cart abandonment.
In this video, i want to present how "Risk Based Authentication" facilitates Frictionless Transactions. How more data points are collected in 3DS 2.x (like Method URL) to achieve the same.
For technical enthusiasts, i recommend to debug your 3DS ecommerce transactions by using Developer Mode on your browsers and analysing the flow of calls.
Really nice..thank you for sharing this useful info..
Hello Satish Sir,
Request if you throw few light on SSL & Signer Certificates with commands.
hello dear, thanks for the explanation
how to increase a share of Frictionless transactions?
Thanks, depends on how you defined the risk rules in your ACS.
Thank you for your videos 👍👍
I have a question : why would the issuer take the risk to skip 2FA (3ds) ? A merchant or an acquiring bank I can understand, they try to offer shoppers a transaction that is as frictionless as possible and increase conversion, but as a cardholder I would not want my bank to skip essential security checkpoints.
Thats a good question. However when you look it from a holistic perspective - cart abandonment and customer frustration for low value payments.
Lets take another example, lets say a customer has been using a Merchant portal registered and has been using the same CC for many transactions, then i believe its easier without a second factor.
Please also note that it is not that Issuer just makes the decision based on the mentioned data points (in the video) alone, Merchant does provide additional data points in the authentication/authorization too.
@@LearnPayments Thank you for replying. There aren't many knowledgeable people around regarding card payments, it's a small world.
Do you know who makes the decision to request a 3DS authentication, is it the issuing or the acquiring bank?
If there's an authorization submitted without authentication, then the merchant keeps the liability of the transaction. Hence it is in the interest of Merchant also to authenticate the customer.
Very nice explantation. Thanks a lot for sharing this.
I have more than 13 years of experience in data technologies, working in roles such as data engineer, data scientist, and Cloud data architect. I also have good knowledge in the payment domain. Currently, I am working partially as a product owner and a Tech lead in a payment aggregator startup company, where I am involved in developing data lakes and AI products.
I am thinking about transitioning to a full-time product owner role in my career, using my technical skills and domain knowledge. I am becoming more interested in the domain and want to move towards techno-functional roles. I believe that becoming a product owner is the best option for me. Although I have only been in the partial product owner role for a few months, I am considering it for my long-term career goal. Do you think this is a wise decision, or should I also explore opportunities in a Business Analyst role?
I think you can only decide what u like do in future..only constant in life is change..even if u start now as BA or PO.. Roles &Responsibility may completely change in next 5-10 years..u r too young to think about retirement job now..I would suggest try it out..first come first serve..
requirement engineering (BA) is also part of product current PO responsibilities anyways..from the below the way u have described..it appears u like to try out PO role.. try it out..
Hello Raghav,
I've been a Product Owner for a Payments product, and i can certainly say that Data Analysis/Science skills do help in doing the job very well. Not to mention the domain and the technology expertise and experience matter a lot. So i believe PO is a good role IMO.
My approach/suggestion is to always enrich your domain knowledge (in this case payments) even though you are working on a tech role. That is very important.
@@LearnPayments Thanks for your response. That brings more clarity to me