Skip to content
Start free
All industries

Banking · Customer and transaction context

Every case has a history.
Keep the records connected.

Bring account data, transaction relationships and policy search into one database for the applications your banking teams build.

Discuss your workload Explore the quickstart

Build the case from its sources.

Start with an account, inspect its transfers, and follow the recorded recipient. Your application brings that evidence together for an analyst.

Account → transfers → counterparty → reviewIllustrative records
Case context · account AC-104Open the transfer records ↓
Two recorded transfers
TX-21009:12 · outgoing
From
AC-104
To
CP-08
Source
payments / TX-210
TX-21109:18 · outgoing
From
AC-104
To
CP-08
Source
payments / TX-211
Shared recipient CP-08Harbor Supplies

Two transfers resolve to the same recorded counterparty.

Supporting policy evidenceRecipient review · version 3

Passage: “Check the recipient’s recorded details.”

Policy PL-07 · passage 12
Application + analystReview before deciding.

Compare the transfer sources with the relevant policy. Record the finding and the next action in the case.

Illustrative account, transfers and policy text. The application retrieves the policy and assembles the case; the relationships do not establish a risk finding.

Three places the context matters.

01

Customer servicing

Bring an account's recent activity and related customer records into the service application, with the source IDs available for follow-up.

SQL
02

Transaction investigations

Move from a transfer to its recorded beneficiary and related accounts. The analyst interprets the connection and records the decision.

SQL + graph
03

Internal policy retrieval

Retrieve a policy by its exact wording or meaning. Show the passage, document version and source alongside the application's answer.

Full-text + vector

Use the query that fits the question.

Share stable record IDs across your models so the application can resolve each result back to its source.

SQL

What happened on this account?

Filter transactions by account and time. Join customer records and aggregate the result.

Query the records
Graph

Which records are connected?

Declare account and counterparty references, then traverse the relationships with a bounded query.

Follow a relationship
Full-text

Where is this policy mentioned?

Find exact terms or rank matching passages. Keep the document ID with every search result.

Search policy text
Vector

Which passages discuss this issue?

Retrieve similar text using your embeddings, then fetch the source passage for review.

Model the embeddings

Text indexes and vectors use their own write endpoints. Your ingestion pipeline manages their updates and records the source version.

A focused first build

Start with one investigation path.

Use representative sample records before introducing customer data.

Review the design with us
  1. 01

    Define the records.

    Model accounts, transfers, counterparties and source documents with stable IDs.

    Schema reference
  2. 02

    Test one complete case.

    Query the transfers, traverse their references, and check every returned source. Set result and traversal limits.

    Graph quickstart
  3. 03

    Connect the review application.

    Keep credentials server-side. Apply the application's access rules and retain the analyst's decision with its evidence.

    Authentication reference