Skip to main content
Submit a request
Computop Paygate GmbH
3-D Secure 2
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?
04 August 2020 13:44
No. The capture mode is irrelevant to 3D-Secure.
Articles in this section
The authorization for a credit card transaction has been denied. In the direct API response and in the transaction overview of Computop Analytics I receive the Paygate Parameter "Code" = xxxx1542 / xxxx0366. Whats is the reason for this?
Will I have to manually resubmit each transaction that is rejected in conjunction with Paygate Parameter "Code" = xxxx1542/ xxxx0366?
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?
Was this article helpful?
0 out of 0 found this helpful
Start typing your search...