The following is a list of our Fraud Detection Modules documentation:   


  • What is 3-D Secure and how does it impact a transaction?

    3-D Secure is an online transaction authentication method, which you can best compare with entering a PIN-code or writing a signature for a transaction on a physical terminal (e.g. in a shop or a restaurant).

    3-D Secure allows you, as a merchant selling online, to demand your customer to identify himself as the rightful owner of his (credit) card. Ultimately, the goal is to reduce fraud cases.

    There are several forms of 3-D Secure authentication. Depending on the customer's bank and originating country, this can be in the form of using a card reader or digipass, entering a PIN-code, or even entering a piece of data that only the cardholder can know.

    For more information about 3-D Secure (Fraud detection documentation), go to the Back-Office under the support tab.

  • What is the difference between 3DS v2.1 and v2.2?
    The latest version of the specification includes:
    • Further promotion of frictionless flow
    1. Improved communication between merchants and issuers to maximize available exemptions for SCA.
    2. Expansion of existing data elements to promote communication of pre-checkout authentication events and support of the FIDO Alliance standards
    • Two new features that provide offline authentication capability for various transaction scenarios, including MOTO transactions (mail order and telephone order):
      1. The addition of 3DS Requestor Initiated (3RI) payments. This provides the ability for a merchant to initiate a transaction even if the cardholder is not present. This channel supported previously only non-payment transactions for v2.1.0
      2. The inclusion of the new authentication method ‘decoupled authentication’. This allows cardholder authentication to occur if the cardholder is offline. However, this authentication method can also be used if the cardholder is online via browser and app channels
    • Improvements to the user experiences and checkout flows
    • Improvements to the EMV 3DS caching process via additional data elements in the PReq/PRes cycles