Skip to content
Start free
All industries

Financial services & payments

Follow the payment.
Keep the evidence in view.

Connect processor events, merchant records and settlement evidence for the applications that investigate payment operations.

Discuss your payment workflow Start with a SQL query

Compare the sources. Keep the gap visible.

A processor event and a settlement entry tell different parts of the story. Join their references and let the operations team inspect what is present or still missing.

Payment and settlement evidenceIllustrative reconciliation worksheet
Source AProcessor eventsPayment ID + provider reference
Join by reference
Source BSettlement entriesSettlement ID + provider reference
REF-410Payment recordedSettlement recorded
Payment recordPAY-42

Merchant M-18
Provider ref: REF-410

Settlement recordSET-88

Batch B-09
Provider ref: REF-410

What the join shows

Both sources carry REF-410. The application can present the pair for comparison; matching a reference alone does not complete reconciliation.

REF-411Payment recordedNo settlement in sample
Payment recordPAY-43

Merchant M-18
Provider ref: REF-411

Settlement recordNo matching row

Check the source feed and the selected batch.

A question for the operator

Has the settlement arrived in a later batch, or is source data missing? Keep the payment reference with the follow-up.

Extend the investigation
M-18Merchant relationships
Source documentsReceipts, notes and policy versions

Illustrative records. Queries expose source relationships; your application sets the reconciliation rules and the operator reviews exceptions.

5 use cases / Payments

The right modalities for your workflow.

Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.

Payments: use cases, recommended query modalities and why each combination fits.
Use caseRecommended modalitiesWhy this combination fits
Settlement reconciliation

Compare payment, settlement and refund records.
SQL

SQL joins records on transaction references, compares amounts and groups unresolved differences for review.
Merchant network investigations

Explore shared accounts, devices and other recorded merchant connections.
SQL Graph

SQL selects a merchant or transaction cohort. Graph traverses the shared relationships an investigator needs to inspect.
Dispute document lookup

Find receipts, correspondence and policy wording for a chargeback.
SQL FTS

SQL retrieves the dispute and transaction details. FTS searches the indexed evidence for relevant terms and phrases.
Connected fraud case review

Bring transaction links and documentary evidence into the same case.
SQL Graph FTS

SQL filters payment activity, Graph follows merchant and account connections, and FTS locates matching language in case documents.
Merchant support knowledge

Retrieve troubleshooting guidance for a payment issue.
SQL FTS Vector

FTS matches error codes, Vector finds related explanations, and SQL adds merchant context and the source article's version.

Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.

Four models, specific jobs

Match the query
to the evidence.

Use stable IDs to resolve every result back to the transaction, entity or document it represents.

SQL
Filter events, join references and aggregate a selected batch.SQL reference
Graph
Follow declared merchant, account and terminal relationships.Relationship schema
Full-text
Find exact references, phrases and ranked document matches.Full-text reference
Vector
Find similar issue descriptions using embeddings you supply.Vector schema

Build a path an operator can inspect.

Start with a representative payment batch and its settlement file.

  1. 01

    Retain source references.

    Store the provider reference, merchant ID, batch and event time with each record. Keep ingestion retries and ordering in your application's design.

    Row API
  2. 02

    Make updates explicit.

    Define the relationships you need. Write document text and vectors through their separate endpoints, with IDs that resolve to the source rows.

    Schema reference
  3. 03

    Test the exception path.

    Include a missing settlement record and a corrected source. Check what the reviewer sees, which identity can access it, and how the decision is retained.

    Authentication reference

OriginChainDB stores and queries the evidence. Your application owns reconciliation rules, payment actions and the review process.

Review your design