Inspect an unresolved reference.
Compare payment and settlement rows by provider reference and batch. Your application routes unresolved records to an operator with both source IDs.
Query related rows All industries Follow the payment.
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.
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.
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.
Operations in context
From one exception
to the records behind it.
Follow the declared connections.
Trace a payment to its merchant, terminal or account references. Inspect the recorded relationship before interpreting activity across those entities.
Traverse merchant relationshipsFind the supporting document.
Retrieve a receipt, support note or policy passage. Keep its original reference and version available to the person handling the case.
Search the textFour 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.
- 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 - 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 - 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