
Fraud is a billion-dollar business and it is increasing every year. The PwC global economic crime survey of 2009 suggests that close to 30 percent of companies worldwide have reported being victims of fraud in the past years. Since we are living in the digitalized world where technology evolves fast and number of transactions grows rapidly, the development of new technologies has provided fraudsters more ways to smuggle money out from person’s or organization’s pocket via using IT system vulnerability or snatching digitalized transactions. Fraud Detection System is developed to detect and prevent such attempts from fraudsters with features like analyzing and monitoring malice transactions.
How does it work?
Early fraud detecting techniques were oriented toward extracting quantitive and statistical data characteristics. These techniques facilitate useful data interpretations and can help to get better insights into the processes behind the data to detec and prevent frauds. However, it required numbers of human analysts and was a time consuming task. Therefore, many fraud detection systems are using statistical techniques combining with machine learning algorithms nowadays. They detects frauds by collecting data, calculating various statical parameters such as averages, quantiles, probability and etc., separating malice transactions from normal transactions. Compare to the traditional fraud detection techniques, they facilitate automated detection and preventing of fraud activities and, more importantly, could provide such services in real-time.
Isn’t it enough with what we have?
It is true that conventional fraud detection system did a quiet good job to protect organizations from fraud attempts. However, since fraud involves one or more persons who intentionally act secretly to deprive another of something of value, for their own benefit, conventional way of calculating probability and discrete analyses is becoming hard to prevent advanced fraud techniques, which is to exploit the weaknesses of discrete analysis. Moreover, since speed of network and computer are growing faster, organizations have less time to analyze fast passing transactions, and it makes harder to catch fraud activities in real-time. To solve above mentioned problems and enhance their systems, an increasing number of companies are starting to use graph databases.Unlike conventional ways of looking at data, graphs are designed to express relatedness. Graph databases uncover patterns that are difficult to detect using conventional techniques such as relational databases.
“Catch ‘em all!” with Graph Database
While most of fraud activities can and does involve criminal rings, even a single well-informed fraudster can create a large number of synthetic identities and to carry out sizeable schemes. Consider an online transaction with the following identifiers: user ID, IP address, geo location, a tracking cookie and a credit card number. Typically, the relationships between these identifiers should be one-to-one(well, most of the time). Some variations naturally account for shared machines, families sharing a single credit card number, individuals using multiple computers and such. However, as soon as the relationships between these variable exceed a reasonable number, fraud should be considered as a strong possibility. The more interconnections exist amongst identifiers, the greater the cause for concern. Large and tightly-knit graphs are very indicators that fraud is taking place. Thus, by putting checks and event triggers into pathways of transactions, we can detect, monitor possible fraud activities and catch fraudsters’ malice attempts on people and organizations in real time.
Common questions
Why use a graph database instead of SQL joins for fraud detection?
Relationships like shared devices or chains of transfers are stored directly as edges, so walking from one entity to its connections does not require rebuilding the path through repeated joins. This becomes significant once queries need to follow several hops, since join cost in a relational model grows with each additional hop.
Can a fraud detection graph run on PostgreSQL?
Yes. Apache AGE is an open-source PostgreSQL extension that adds openCypher graph queries on top of a regular PostgreSQL database, which lets a team keep the graph and the relational data in one system. Dedicated graph databases such as Neo4j are also common, usually chosen when the graph workload is large or heavily algorithm-driven.
What algorithms actually find fraud rings in a graph?
Community detection algorithms such as Louvain or label propagation group accounts that act together, centrality measures like PageRank highlight accounts with unusually central roles, and bounded cycle or path queries catch specific shapes such as a loop of transfers. These typically run through a graph analytics library such as Neo4j Graph Data Science or Apache Spark GraphX rather than as hand-written queries alone.
Does adding a graph database replace rule-based fraud systems?
No. Graph output is a score or a flagged pattern, and it is normally combined with existing transaction rules and any statistical model already in production, then routed to a case queue for review. Treating a graph alert as an automatic final decision, without that combination, is one of the more common implementation mistakes.
Sources
About this page
Last reviewed October 30, 2026 by the Nine Bits editors. Read our editorial policy or report an error.