FraudLabs Pro
Configure FraudLabs Pro to screen website checkout attempts and stop orders that match your chosen risk rules.
Accessing the Screen
Open Settings → Fraud Protection → All Modules and click Configure on the FraudLabs Pro card. Address: {admin}/module/fraud?module=FraudLabsPro.
Screen Overview
Preparing Your Account
Prepare a FraudLabs Pro account with an API key, available screening credits and a plan covering your chosen checks. See the official Screen Order documentation. No server record, product mapping or separate module license field is required here.
Understanding Order Checks
The website checkout sends available customer identity, IP, billing address, telephone, order total, currency and coupon information. It does not send card numbers or a device fingerprint. A setting cannot supply information absent from the provider response.
Active fraud modules check the attempt before the order is created. The first refusal stops checkout. These checks do not review earlier orders or automatically cancel paid services. This integration provides no catalog import, periodic synchronization or provider feedback action.
Configuration Fields
Tasks
Saving the Rules
- In Configuration → Status, select Enable; the remaining fields become editable.
- Enter API Key, set the threshold and choose the blocking rules.
- Click Save Changes below the form. Reopen the module and check the saved settings.
Saving validates the required key and threshold, without contacting the provider. There is no connection-test or sandbox selector. A controlled checkout test makes a real screening request and can consume credits; agree its scope before testing.
Reviewing a Refusal
- Open the module's Records tab and search for the relevant customer, IP address or reason.
- Compare the date and reason with the customer's checkout message and the FraudLabs Pro account result.
- Review the rule responsible before changing settings. A refusal is a risk signal, not proof of misconduct.
Important Notes
With error blocking off, provider failures allow checkout to continue to other checks. REVIEW blocking refuses the attempt; it does not create a pending-review order. Client API and administrator-created orders do not share this website checkout check.
The Records tab's Clear Logs action currently leaves detection records in place. A success message does not confirm deletion. Successful screening attempts are not listed as detection records.
Required Permissions
Requires SETTINGS_FRAUD_PROTECTION to open and configure the module.
Related Articles
Vielen Dank für Ihre Rückmeldung!
Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.