Merchant application
The entity and proprietor pass document checks with a newly created mobile and narrow operating history.
Check the merchant behind the settlement account.
Detect merchant identities and clusters built to receive fraud proceeds under the appearance of ordinary commercial payments.
A valid merchant record can hide a receiving endpoint.
The onboarding entity may have documents, a bank account and a plausible category while its operating footprint remains thin or shared with other merchants.
Shared infrastructure
Devices, addresses, websites or settlement beneficiaries recur across unrelated merchant records.
Payment intake
Fraud proceeds arrive disguised as customer transactions or ordinary merchant volume.
Rapid exit
Settlement destinations change or funds move before post-onboarding behaviour produces a strong alert.
More than 1,000
Banks, third-party app providers and payment system operators using FFRI
Department of Telecommunications via PIB, 22 December 2025
A merchant category is not evidence that an operating business exists behind an account.
Connect merchant and proprietor evidence.
Entity verification and human control need to be evaluated together, then connected across the merchant base.
Personhood Score
Human control
Assess the proprietor or controller attached to the merchant application.
Cluster Intelligence
Merchant graph
Find common infrastructure across supposedly independent merchants and settlement accounts.
Sleeper Watch
Early life
Re-score after operating and settlement evidence begins to accumulate.
Workbench
Review
Give merchant-risk teams one linked case with exportable evidence.
Compare onboarding evidence with merchant outcomes.
The backtest ranks historical merchants using only evidence available at their onboarding time, then compares the result with chargeback, law-enforcement and confirmed-fraud outcomes supplied by the aggregator.
Keep the evidence tied to the onboarding decision.
Reason codes record why a merchant entered review. Transaction monitoring remains a separate control with a later observation window.
Run the Payment aggregators backtest.
The first output is a ranked historical file and a precision curve at your available review capacity. No production integration is required.
Book a backtest