3-D Secure 2
- Do we have to make changes regarding 3D-Secure 2?
- We are currently not using 3D-Secure at present. Do we have to amend our acquiring contract?
- How will 3DS 2 affect merchants that only instigate 3D-Secure where the transaction value is above a certain value?
- How high is the effort for the merchant if they use Computop payment forms (minimal requirements)?
- Do I as a merchant have to support both version 1 and 2 in regards to 3D-Secure?
- Which Schemes/Brands are supported by 3D-Secure 2?
- Do I have to note anything regarding 3D-Secure while implementing various brands?
- In regards to 3D-Secure 2 I´ve heard about "Merchant Whitelisting".What is it about?
- We have already implemented "Card on file". Do we have to amend our implementation?
- A Merchant prefills the token (pseudo card number) on their own template/form. Does the payment require a card on file (COF) flagging as Merchant Initiated Transaction or Customer Initiated Transaction?
- We currently delay the capture from the authorization. Are there any changes to be aware of regarding 3D-Secure 2 if we switch to immediate captures without delay?
- Does merchant whitelisting by the customer have an impact on the merchants liability shift?
- Does frictionless authentication have an impact on the liability shift for the merchant?
- Should we call forms by using POST or GET?
- Which functionalities have already been implemented using Private Protocol Extensions?
- How and where is the whitelist processed in the authentication flow?