A Dataloop product
LoopTrace correlates customers, accounts, addresses, phone numbers and transactions into a single navigable graph — so an isolated alert becomes the full structure that explains it.
Triangulation detected · 3 pass-through accounts
Mexican regulatory scope
Built for the reporting, identification and risk-based-approach obligations of the Mexican financial ecosystem.
The problem
Transaction monitoring systems deliver alerts per operation. But money laundering does not happen in one operation: it happens across a structure of people, accounts and addresses coordinated to look unrelated.
Two seemingly unrelated customers share an address or a phone number. No transactional alert reveals that on its own.
The analyst jumps between queries, spreadsheets and files to assemble by hand what should be visible immediately.
If the structure is never documented, the finding rests on a single operation instead of the network that produced it.
Capabilities
From entity exploration to the regulatory report, without leaving the platform or losing the trail of what the analyst did.
Module 1
The graph is the core of the product. Pick a customer, an account, a phone number or an address and LoopTrace expands its network: who sends money, who receives it, through which counterparties and which pass-through accounts.
Product screen · synthetic data
Module 2
The analyst's starting point. Alerts arrive prioritized and with full economic context, with filters by amount, date, typology, currency, nature and entity — and a direct jump from the case to its network.
Product screen · synthetic data
Module 3
Cross-cutting search over the whole data universe. Customers, accounts, phone numbers and addresses in a single index, with multi-term search and a direct jump to the network of any result.
Product screen · synthetic data
Module 4
Risk matrices that turn the risk-based approach into a reproducible rating. Risk level stops being the analyst's individual judgement and becomes the documented output of a methodology.
Capability shown as a diagram, not a screenshot
Module 5
A matching process against control lists. Screening stops being a manual lookup by name and becomes a systematic step of the identification process.
Capability shown as a diagram, not a screenshot
Every screening performed is recorded against the entity.
Module 6
Five regulatory report layouts and the alert layouts that feed them. The report is generated from the same case file where the investigation happened, without re-entering data into a separate sheet.
Capability shown as a diagram, not a screenshot
Architecture
An institutional buyer asks what each component does and who answers for it. That answer is separated by design.
LoopTrace
Dataloop product
The Mexican compliance logic, the link model, the typologies, the report layouts and the analyst experience. This is the product the user operates.
SAS Viya
Analytical substrate
The data and compute engine the platform runs on. It provides scale, processing and enterprise-grade analytical infrastructure.
For every team
Compliance
Can I defend the finding?
The case file shows the whole network, not a loose operation. The report is generated from there.
Risk
How do I rate this customer?
Risk matrices with per-factor breakdown. Same input, same rating, documented criteria.
Technology
What does it run on?
It runs on SAS Viya, with data sources already correlated and no third-party dependencies in the front end.
Information security
What does the application expose?
An interface hardened against style injection, with no sensitive local state and session delegated to the platform.
Audit
Can I reconstruct what the analyst did?
Every watchlist screening is recorded and every report is traceable to the alert and the network behind it.
FAQ
Not necessarily. LoopTrace consumes alerts and transactions, and its value is correlating them into an investigation with a case file and a report. It can run alongside an existing monitor or receive the alerts the institution already generates.
The eight sources it already correlates: customers, addresses, phone numbers, internal accounts, external accounts, transactions, alerted transactions and alerts. The link model is built from them.
The Mexican framework is being rewritten: the July 2025 decree reforming LFPIORPI requires the general rules to be updated, and the regulation was amended in March 2026. Layouts and matrices are configurable precisely to absorb that movement without rebuilding the platform.
On the institution's SAS Viya platform. Let's discuss your specific environment and available sources.
No. Every public demonstration uses synthetic data generated for that purpose.
Next step
A working session with your compliance team: we start from a real alert in your operation and reconstruct its full network.