Transaction Monitoring
Transaction monitoring is the core Loci integration path. A financial institution sends transaction events to Loci, Loci evaluates them in real time, and the client system receives a decision that can be applied immediately.
The same events also feed alerts, entity intelligence, investigation workflows, rule testing, and audit records.
End-To-End Flow
- The client system sends a transaction event to Loci.
- Loci validates the organization, payload, and tenant context.
- MADIE evaluates the transaction against active rules and supporting data.
- Loci returns an approve, review, or decline response.
- Reviewable or risky activity appears in alert queues.
- Analysts investigate alerts, group them into cases, and record outcomes.
- Outcomes inform rule tuning and control improvements.
Transaction Payloads
A useful transaction payload should identify the event, the customer or entity, counterparty details, amount, channel, transaction type, timestamp, and any client-specific context needed by rules.
Common fields include:
- transaction_id
- entity_id or customer_id
- amount and currency
- transaction_type
- source account and bank details
- beneficiary account and bank details
- channel or device context
- timestamp
- geolocation or branch context, when available
- custom_data for institution-specific fields
Custom fields should be stable and consistently typed. If a field is expected to drive a rule, treat it as part of the integration contract.
Decisions
Loci responses are designed for online systems:
- Approve: no configured control requires intervention.
- Review: route to queue or step-up according to client policy.
- Decline: block or hold according to client policy.
The decision response can include risk score, matched rules, rule evidence, and explanatory metadata. The client system remains responsible for applying its operational policy to the returned decision.
Alerts
A reviewable transaction can become an alert. Alerts are the triage surface for single suspicious events or rule hits. Analysts can claim alerts, assign them, mark them false positive, link them to cases, or escalate them into deeper review.
See Alerts API.
Entity Intelligence
Loci builds context around entities and counterparties, including relationship graph and centrality views where available. This helps analysts understand whether a transaction is isolated or part of broader behavior.
See Entity Centrality And Network Intelligence and Entity Intelligence API.
Custom Data And Tables
Many deployments need client-specific reference data such as watchlists, trusted entities, product thresholds, dormant account states, branch codes, or segment-specific limits. Loci supports custom data as part of payloads and through managed tables depending on the deployment design.
Use custom data when the value belongs to the event. Use managed tables when the value is reusable reference data that many rules need to consult.
Online Reliability
Real-time transaction monitoring should stay on the hot path. Heavy reporting, large exports, and historical analysis should run through asynchronous jobs or read replicas so they do not affect online evaluation latency or uptime.