01 Settlement intelligence

Money moves.Clarity follows.

Resolve settlement questions across gateway, bank, and ledger—with evidence for every answer.

Sign in
Settlement supportExplore ↓
SettleLensMOCK TRACE
PAYMENT CAPTURED
₹8,499.00
Customer payment confirmed by the gateway.
TXN-1041
Captured₹8,499.00Fee₹169.98=Net payable₹8,329.02
01 / Gateway record verified
MERCHANT BANKAwaiting credit
EXAMPLE PAYMENT / SUCCESSFUL RETRY

Where is
my money?

One payment question. One place to investigate.

One question.
One connected trace.

Three systems.
One true story.

Every answer links to its evidence.

01 / GATEWAY

Confirms the payment and its settlement ID.

Say what happened.
Show your work.

Status. Reason. Next step. Evidence.

Sign in
SettleLens
Settlement copilotEvidence-first answer
Why hasn’t TXN-1042 settled?
●   FAILED

The payment succeeded.
The payout didn’t.

The bank rejected the ₹2,450 settlement because the beneficiary details are invalid.

▣ Gateway ↗▥ Bank ↗▤ Ledger ↗

What we can’t confirmNo subsequent retry appears in the loaded records.

No evidence?
No invention.

See what’s missing and what to verify next.

  • 01Missing bank outcome
  • 02Conflicting statuses
  • 03Unexplained amount difference

Built for the work
after payment.

For support, payment operations, and finance teams that need the same answer.

01

Trace every event

Follow capture, fees, payout attempts, retries, and bank credits in one timeline.

Gateway → Bank → Ledger
02

Explain the delay

Turn settlement records into a clear reason and a support-ready next step.

Status → Reason → Action
03

Reconcile the money

Compare captured, deducted, payable, and credited amounts using exact values.

Captured − Fees = Payable
04

Keep gaps visible

Surface missing evidence, conflicting statuses, and unexplained differences.

Known · Missing · Review
YOUR PAYMENT STACK

Connect the records you already use.

Start with structured files. Add read-only gateway, bank, ledger, and support connectors as you move to production.

Payment gatewaysBank outcomesMerchant ledgersSupport toolsCSV & API
PRODUCTION STANDARD

Evidence first. Access controlled.

  • Read onlyInvestigate without moving money
  • Scoped accessKeep every merchant workspace isolated
  • Audit readyRetain sources, decisions, and analyst actions

These controls describe the production deployment standard. The public experience uses synthetic data and has no live payment connections.

12Synthetic
transactions
03Connected
data sources
04Hard-case
exceptions

Synthetic sample data. No live payments.

Make every settlement
make sense.

Sign in
EXAMPLE CASEOne settlement, completely traced

Captured → rejected → explained.

A ₹2,500 payment is captured. The ledger records ₹2,450 payable after fees. The bank rejects the payout because the beneficiary details are invalid. SettleLens connects the three records and names the missing retry.

Sign in to investigate ↗