MaxMind
Configure MaxMind minFraud to assess website checkout attempts and reject those exceeding your chosen risk limits.
Accessing the Screen
Open Settings → Fraud Protection → All Modules and click Configure on the MaxMind card. Address: {admin}/module/fraud?module=MaxMind.
Screen Overview
Preparing minFraud Access
Prepare your MaxMind account ID, license key and available minFraud credit. Confirm access to the service you select. See MaxMind's account and testing guidance. No server record, hosting plan or product mapping is required.
Understanding the Scope
The module sends available identity, IP, browser, billing, telephone, order amount, currency and coupon information. It does not send card details or install device fingerprinting. Score evaluates the risk score; the additional email, country and anonymous-network checks require details returned by Insights or Factors.
Only active fraud modules participate in website checkout. The first refusal stops order creation. Earlier orders are not rescored, and paid services are not automatically canceled. This integration has no catalog import, scheduled synchronization or transaction-feedback action.
Configuration Fields
Tasks
Saving the Configuration
- In Configuration → Status, select Enable to unlock the fields.
- Enter User ID and License Key. Choose Service Type, a whole-number threshold and the rejection rules.
- Click Save Changes below the form. Reopen the module and verify the saved selections.
Saving checks that credentials are present; it does not authenticate with MaxMind. There is no connection-test button. The MaxMind sandbox requires a separate endpoint and key; this module has no endpoint selector. Do not put a sandbox key into this production-service configuration.
Checking a Refusal
- Open Records and search for the relevant customer, IP address or reason.
- Compare the reason and timestamp with the checkout message and MaxMind account result.
- Check the selected service and rule before adjusting the threshold. Risk scoring does not establish misconduct.
Billing lookup warnings can also refuse an attempt when the affected address field was supplied. Such warnings are not always saved as detection records. An empty list does not prove that every attempt passed.
Important Notes
A controlled checkout test sends a real minFraud request and can consume credit; define its scope first. With error blocking off, provider errors allow the attempt to continue to other checks. 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. Its success message is not proof of deletion.
Required Permissions
Requires SETTINGS_FRAUD_PROTECTION to open and configure the module.
Related Articles
Thanks for your feedback!
Our support team is here around the clock for anything you can't find above.