Which accounts need a closer look?
Group transfers with SQL. Compare counts and totals using your application's review rules.
SQL aggregates All solutions Follow the records.
Fraud investigation · SQL + graph
Follow the records.
Investigate the connection.
Query transactions and trace related accounts, devices and beneficiaries in the same database.
A connection is a starting point.
A shared device or beneficiary adds context to an account. Inspect the underlying records and their timing before deciding what the connection means.
Follow a connection
account-AStarting account
device-31Device reference
account-BRelated account
payee-08Beneficiary
Inspect the link Evidence · device referenceTwo accounts.
Two accounts.
One recorded device.
Both account records reference device-31. That connection is a reason to investigate, not a finding of fraud.
- Starting point
- account-A
- Related record
- account-B
- Next question
- Was this a shared household device?
Evidence · transfer recordsTwo transfers.
Two transfers.
One beneficiary.
The transfers from both accounts reference payee-08. Review the original records and their timestamps before drawing a conclusion.
- Transfer sources
- account-A · account-B
- Shared reference
- payee-08
- Next question
- Is this an expected merchant or recipient?
Highlighted lines show the selected relationship. All records are illustrative.
From signal to case
Let the query explain
why you looked.
OriginChainDB retrieves records and relationships. Your application defines the review criteria, assembles the case and routes it to an analyst.
- 01
Select a candidate
Use SQL to group transfers by account and examine counts or amounts. Your application chooses thresholds and the time window.
- 02
Expand the context
Follow declared relations from the candidate. Bound the number of hops and retain the identifiers behind each connection.
- 03
Make a reviewable decision
Attach source records, query parameters and timestamps to the case. Approval, escalation and account restrictions remain application decisions.
Ask a specific question.
Choose the query for the evidence you need. A graph pattern describes a relationship; it does not establish intent.
Who else references this device?
Inspect neighboring records and reverse relations to trace a shared identifier.
Neighbors and relationsHow are these accounts connected?
Use bounded traversal or path queries, with explicit depth and result limits.
Bounded traversalKeep the evidence traceable
Model facts.
Preserve their source.
Give accounts, devices and transfers stable IDs. Declare relations on columns holding the target record's key.
Define a graph relation- Accounts
- Account ID and device reference
- Transfers
- Transfer ID, source, beneficiary, amount and timestamp
- Case evidence
- Application-owned query context and review outcome
Bound the search. Keep the judgment.
Graph capability must be enabled for the selected instance. Start with a narrow frontier; broad paths can exceed query budgets. Review the documented limits before expanding a case.
Shared identifiers can have ordinary explanations. Verify identity, timing and source quality, and let your application or analyst decide whether to act.