What, Who and Why
In the fight against financial crime, transactions tell you what—but only context tells you who and why. That’s where masterdata comes in.
At Legatus, we treat masterdata as a critical component of modern fraud prevention. It refers to relatively static entity-level information—such as customer profiles, account details, merchant records, or KYC attributes. While transaction data captures the events, masterdata explains the actors and their environment.
Without it, you’re flying blind.
Smarter Investigations
Masterdata is indispensable during case analysis. It equips investigators with immediate access to rich entity information (e.g. date of birth, customer segment, account status, onboarding channel). When an alert is triggered, investigators can drill down into associated masterdata—without jumping across systems.
Precise Rules, Fewer False Positives
Fraud rules become sharper when context is available. Instead of one-size-fits-all logic, Legatus allows rule conditions based on masterdata:
Treat a high-value transaction differently if the account is less than 30 days old
Flag travel-related anomalies only for customers with fixed domestic addresses
Apply velocity thresholds based on customer type or risk score
The result: better accuracy, fewer false positives, and protection that adapts to each entity’s profile.
A Clean Source of Truth
Masterdata is more than enrichment—it’s governance.
Legatus includes a managed, versioned masterdata layer that ensures consistency and traceability. It eliminates brittle logic caused by mismatched values across CRM, Core Banking, and fraud systems.
You define the truth once—Legatus uses it everywhere.
Don’t Let Siloed Data Weaken Detection
Many legacy systems rely on transaction-only data and overlook masterdata, either due to siloed architectures or limited integration capabilities. This leads to blind spots in profiling, weak correlations across channels, and ultimately—missed fraud.
With Legatus, you don’t have to choose between real-time detection and deep context. You get both.
Why LegatusMasterdata is not optional. It’s foundational.
And in Legatus, it’s built in by design.