Fraud and financial crime

How to build real-time fraud detection on a lakehouse

Real-time fraud detection on a lakehouse streams transactions through Kafka into open tables, scores each event with a model trained on governed history, and pushes decisions back to payment systems in seconds. On DataNature, StreamHouse, DataNature AI and AI360 Studio do this inside your jurisdiction.

Published . Last updated

On this page

What does the architecture look like?

  1. Connect captures transactions with change data capture.
  2. StreamHouse streams them into Bronze tables.
  3. A model trained on Gold history scores each event.
  4. AI360 Studio pushes decisions and alerts to payment and case systems.
  5. Atlas logs every score for audit.

Why use a lakehouse rather than a separate fraud engine?

One copy of data serves real-time scoring, investigation and model retraining. Analysts see the same events the model saw.

What data improves fraud models most?

Transaction history, device and channel data, customer tenure and behaviour, and network features such as shared devices or beneficiaries.

How do you keep it compliant?

Keep data and models in-country, mask personal data for analysts who do not need it, and keep lineage from alert to source event.

What does the build look like in DataNature, component by component?

StepComponentDetail
Capture transactionsStreamHouseChange data capture from the card or core banking database, or events from the payment switch, into managed Kafka
Enforce event contractsStreamHouse schema registryProducers cannot break the schema scoring depends on
Maintain short-window featuresStreamHouse in-flight processingVelocity counts, new-device flags, merchant risk per card, keyed by card or account
Slow featuresdbt Gold and the feature storeCustomer tenure, historical spend profile, chargeback history
ScoreDataNature AIModel versioned in the DataNature AI registry, served for real-time inference
Decide and actAI360 Studio and VoirRules plus model score → approve, step up or hold; analyst case created with context
AuditIceberg and AtlasEvery event, feature value, score, model version and decision written back for audit and retraining

Mask card numbers with a "show last 4" mask and hash customer IDs for analysts, while fraud investigators get an exempt policy. Reconcile hot-path transaction counts against the batch path daily to catch dropped events. See StreamHouse: the real-time hot path for the streaming design.

How does DataNature Atlas keep this secure and compliant?

Investigators see what they need; analysts see masked identifiers; every score and decision is auditable. DataNature Atlas is the platform's governance module:

  • Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
  • Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
  • Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
  • Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
  • Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.

See it on your own data.

Book a demo

Demos and quotes are handled by Dlytica, the company behind DataNature.