Prerequisites and caveats

1. To use the WL Engine via PIQ, you need:

   1. A contract with DevCode Identity

   2. PayInsight API Credentials

2. Please note that when utilizing the WL Engine through PIQ, it operates as a Fraud Provider. This means that while using the PayInsight WL Engine, you are unable to employ other Fraud Providers for the same transaction. The following are examples of such providers, though the list is not exhaustive:

   1. Featurespace

   2. Sift

   3. Seon
      Please refer to the PaymentIQ documentation for a more up-to-date list of PIQ fraud providers.
      https://docs.paymentiq.io/docs/configuration_and_administration/kyc_index/

3. There are a few issues identified when using the engine via PIQ due to the rule flow of PaymentIQ. Some notable examples include, but are not limited to

   1. Fallback Logic Failure

      1. PIQ selects a PSP before engaging a fraud provider. Consequently, if a player is redirected from the original PSP (YYZ) to PSP (123), the effectiveness of your fallback rules will depend on your configuration. For instance, if you have set a fallback to PSP YYZ, it may not function as intended because PIQ records the initial PSP as YYZ, even if it was never utilized.

   2. Forex Rule Order Issue

      1. Forex rules are evaluated before fraud rules.
         If the original PSP YYZ processes in EUR, but the fraud-based re-routing
         switches to PSP 123 (GBP), the transaction may fail due to currency

         mismatch.

4. Fraud conditions
   The fraud conditions in PaymentIQ are reversed. This means you should out the smallest score, ex. 4, in the “Fraud score max” condition and the bigger score, ex. 10, in the “Fraud score min.”