FraudNet
When processing transactions through the IXOPAY platform, FraudNet external risk checks can be utilized to enhance your transaction security. This guide covers the necessary steps to initiate these checks.
Transaction extra data
The proper implementation of FraudNet risk checks requires specific extraData
to be incorporated into calls to the Transaction API.
For the specific details on what needs to be included, please refer to Adapters: External Risk - FraudNet External Risk Adapter.
Initializing the risk script
Depending on the configuration of your risk profile or connector, you might need to manually initialize the FraudNet risk scripts. There are two scenarios:
- Using payment.js
- Without payment.js
In cases where the connector or risk profile associated with your Public Integration Key isn't set to automatically initialize FraudNet, you need to manually initiate it with payment.js. If Init Scripts Automatically is enabled, no further javascript steps are required for embedding FraudNet.
<script>
const payment = new PaymentJs("1.2");
payment.init("public-integration-key", "number_div", "cvv_div", (payment) => {
// ...
try {
payment.initRiskScript({ type: "fraudNet" });
} catch (exception) {
//this might happen on an invalid configuration at risk profile or connector level
}
});
</script>
If you are not utilizing PaymentJS, you can still manually initialize the FraudNet risk script with the following steps.
<script src="https://gateway.ixopay.com/js/risk-scripts/fraudNet-dc.min.js"></script>
<script>
const fraudNetHandler = new FraudNetDcHandler();
fraudNetHandler.initFraudNetDc((fraudNet_fingerprint_id) => {
// provide as transaction extra data FRAUDNET_DEVICE_FINGERPRINT_ID or fraudNet_fingerprint_id
document.getElementById("hidden-fraudNet-fingerprint-id").value = fraudNet_fingerprint_id;
});
</script>
Remember to accurately include all necessary information for successful risk checks with FraudNet. If you encounter issues, review your connector configuration or the extra data you're providing.