<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: 14_DIVYA JAIN </title>
    <description>The latest articles on DEV Community by 14_DIVYA JAIN  (@divyajain14).</description>
    <link>https://dev.to/divyajain14</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4136447%2Fd02f9640-4ab7-4266-bfc5-b2b8b56b07ad.png</url>
      <title>DEV Community: 14_DIVYA JAIN </title>
      <link>https://dev.to/divyajain14</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/divyajain14"/>
    <language>en</language>
    <item>
      <title>Building an Agentic Fraud Investigator with TigerGraph: Moving from Uncertain Signals to Defensible Next-Best Actions</title>
      <dc:creator>14_DIVYA JAIN </dc:creator>
      <pubDate>Mon, 21 Sep 2026 21:27:23 +0000</pubDate>
      <link>https://dev.to/divyajain14/building-an-agentic-fraud-investigator-with-tigergraph-moving-from-uncertain-signals-to-defensible-3nno</link>
      <guid>https://dev.to/divyajain14/building-an-agentic-fraud-investigator-with-tigergraph-moving-from-uncertain-signals-to-defensible-3nno</guid>
      <description>&lt;p&gt;Building an Agentic Fraud Investigator with TigerGraph: Moving from Uncertain Signals to Defensible Next-Best Actions&lt;br&gt;
Submitted for TigerGraph × Hacker House Goa (HHGOA) 2026 Hackathon&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Executive Summary &amp;amp; What We Built
Modern fraud detection in financial institutions faces a fundamental paradox: models produce thousands of probabilistic risk alerts each day, yet human analysts must manually correlate transactions, parse device fingerprints, review bank policies, and decide whether to block an account or file a suspicious activity report. When money is on the line, acting too slowly lets fraudsters drain funds, while acting precipitously on an ambiguous signal blocks innocent customers.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;To solve this, we built the TigerGraph Agentic Fraud Investigator—an autonomous, policy-aware AI agent that investigates fraud alerts, resolves uncertainty through controlled evidence-gathering, detects complex syndicated attack rings, and recommends auditable Next-Best Actions (NBA) with calibrated approval routes (auto, L1, L2).&lt;/p&gt;

&lt;p&gt;Our agent was evaluated on the 20 official benchmark exam cases (HHG-001 through HHG-020) derived from the IEEE-CIS fraud dataset, successfully generating 100% compliant answer files, identifying undocumented bot rings, and producing defensible FinCEN-compliant Suspicious Activity Reports (SAR).&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;System Architecture&lt;br&gt;
The solution couples TigerGraph's high-performance graph database with an agentic reasoning loop:&lt;/p&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;                  [ Incoming Trigger ]
(Risk Score Anomaly / Customer Dispute / Analyst Request)
                            |
                            v
             +-----------------------------+
             |  Fraud Investigator Agent   |
             +-----------------------------+
                            |
    +-----------------------+-----------------------+
    |                                               |
    v                                               v
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;+------------------------+                      +------------------------+&lt;br&gt;
|  TigerGraph Savanna    |                      |  Case Memory Engine    |&lt;br&gt;
|  - Entity Resolution   |                      |  - Precedent Search    |&lt;br&gt;
|  - Shared Device Rings |                      |  - 5,565 Closed Cases  |&lt;br&gt;
|  - Velocity &amp;amp; Traversal|                      |  - Graph Write-Back    |&lt;br&gt;
+------------------------+                      +------------------------+&lt;br&gt;
        |                                               |&lt;br&gt;
        +-----------------------+-----------------------+&lt;br&gt;
                                |&lt;br&gt;
                                v&lt;br&gt;
                 +-----------------------------+&lt;br&gt;
                 |   Uncertainty Evaluator     |&lt;br&gt;
                 |  - Weak Signal Verification |&lt;br&gt;
                 |  - Policy Rules R1 - R10    |&lt;br&gt;
                 +-----------------------------+&lt;br&gt;
                                |&lt;br&gt;
        +-----------------------+-----------------------+&lt;br&gt;
        |                                               |&lt;br&gt;
        v                                               v&lt;br&gt;
+------------------------+                      +------------------------+&lt;br&gt;
| Next-Best Actions      |                      | Regulatory Compliance  |&lt;br&gt;
| - Initial vs Final     |                      | - FinCEN SAR Generator |&lt;br&gt;
| - Routing: auto, L1, L2|                      | - Defensible Narrative |&lt;br&gt;
+------------------------+                      +------------------------+&lt;br&gt;
Core Pipeline Components:&lt;br&gt;
Trigger Intake: Ingests risk-score alerts, customer disputes, or analyst requests.&lt;br&gt;
Graph Expansion: Traverses customer transaction histories, merchant locations, and shared device profiles.&lt;br&gt;
GraphRAG &amp;amp; Case Memory: Searches 5,565 historical closed investigations (CC-0001 to CC-5565) to retrieve relevant precedents.&lt;br&gt;
Policy &amp;amp; Uncertainty Engine: Evaluates evidence under bank rules R1–R10, recognizing when to verify before blocking (Rule R1) or identify disputed subscriptions (Rule R7).&lt;br&gt;
Next-Best Action &amp;amp; Approval Routing: Produces both initial and post-evidence recommendations routed to automated execution (auto), team leads (L1), or fraud managers (L2).&lt;br&gt;
Regulatory SAR Generation: Automatically drafts full FinCEN-compliant narratives (Who, What, When, Where, How, and Why) whenever regulatory thresholds are met.&lt;br&gt;
Graph Write-Back: Persists newly completed investigations back into TigerGraph as new case vertices to enrich institutional memory.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;How TigerGraph Is Used&lt;br&gt;
Graph structures are uniquely suited for fraud investigation because fraudsters do not operate in isolation—they leave relational footprints across shared devices, proxies, cards, and temporal clusters.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;We modeled the domain in TigerGraph using the following schema:&lt;/p&gt;

&lt;p&gt;Vertices: Customer, Card, Transaction, DeviceProfile (DeviceInfo + OS + Browser + Screen), BillingRegion, EmailDomain, and ClosedCase.&lt;br&gt;
Edges: OWNS (Customer → Card), MADE (Card → Transaction), FROM_DEVICE (Transaction → DeviceProfile), BILLED_IN (Transaction → BillingRegion), NEXT (Transaction → Transaction), and ON_CARD (ClosedCase → Card).&lt;br&gt;
Key GSQL Queries Implemented:&lt;br&gt;
FindSharedDeviceRing: Traverses from a card's transactions to its device profiles, and then hops outward to uncover other cards and customers utilizing the identical device footprint. This query unlocked our discovery of the massive SM-G935F bot syndicate in benchmark case HHG-014 (52 linked customer accounts and over $16,500 in exposure).&lt;br&gt;
DetectOutOfRegionUse: Computes geographical consistency by querying the customer's historical billing regions against a flagged card-present transaction. In case HHG-018, this detected physical transactions occurring in two distant regions within an impossible 8-minute window, immediately confirming counterfeit card cloning.&lt;br&gt;
RetrieveSimilarCases &amp;amp; WriteCaseRecord: Treats TigerGraph as a live Case Memory repository, retrieving precedents and writing newly resolved cases back to the graph.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Agentic Capabilities Implemented
Handling Uncertainty (Rule R1): Rather than treating risk scores as verdicts, the agent recognizes that a single weak signal (&amp;lt;0.70 probability) requires verification (VERIFY_WITH_CUSTOMER or STEP_UP_AUTH) before blocking.
Subscription Dispute Recognition (Rule R7): When customer C13171 disputed a $55.68 charge (HHG-008), the agent analyzed historical transaction cadence, discovered identical monthly charges on the 19th of each prior month, and advised customer warning and cancellation assistance without disrupting the cardholder.
Evolving Next-Best Actions: The agent models dynamic decision-making by recording its recommendations before evidence is requested, simulating controlled customer/analyst responses, and updating its final recommendations.
Distinguishing Cases from Reports: The agent distinguishes internal case records (CREATE_CASE) from regulatory filings (FILE_REPORT), reserving SARs strictly for cases exceeding $1,000 exposure, multi-card rings, or undocumented syndicates.&lt;/li&gt;
&lt;li&gt;Key Lessons Learned
Risk Scores Are Not Truth: A 0.87 score can easily be a false alarm on a customer transacting in their own home region (HHG-007), while a 0.05 score can mask a multi-account proxy botnet (HHG-014). Graph context is essential to disambiguate raw model outputs.
Graph Memory Compounds in Value: Grounding agent reasoning in 5,565 closed historical cases allowed the agent to cite exact historical precedent cases (e.g. CC-2649, CC-2971) when categorizing undocumented proxy fraud.&lt;/li&gt;
&lt;li&gt;What We Would Improve With More Time
Real-Time Graph Streaming: Ingest live transaction feeds directly into TigerGraph via Kafka/Flink connectors for real-time edge insertion.
Graph Neural Network (GNN) Embeddings: Train TigerGraph ML Workbench GNN embeddings to automatically score topological anomaly subgraphs before LLM reasoning.
Interactive Analyst Chat: Expand the analyst dashboard with a bidirectional chat interface allowing human investigators to interrogate graph paths conversationally.&lt;/li&gt;
&lt;li&gt;Social Media Post (X / LinkedIn)
Just built an Agentic Fraud Investigator powered by @TigerGraphDB for the Hacker House Goa (HHGOA) 2026 Hackathon! 🚀&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Our AI agent navigates 590k+ transactions, performs multi-hop GSQL traversals to uncover bot syndicates, resolves uncertainty with controlled evidence gathering, and recommends Next-Best Actions under strict banking policies.&lt;/p&gt;

&lt;p&gt;Check out our full architecture, graph schema, and 20 benchmark case findings: &lt;a href="https://github.com/divyajain14/TIGERGRAPH_FRAUD-INVESTIGATION-AGENT" rel="noopener noreferrer"&gt;https://github.com/divyajain14/TIGERGRAPH_FRAUD-INVESTIGATION-AGENT&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  TigerGraph #GraphRAG #AI #FinTech #AgenticAI #FraudDetection #HHGOA
&lt;/h1&gt;

</description>
      <category>tigergraph</category>
      <category>ai</category>
      <category>python</category>
      <category>hackathon</category>
    </item>
  </channel>
</rss>
