One engine, from capture to ledger.
Everything below runs on its own, all the time. The only step that waits for a person is the one that should.
Payment capture
Reads every configured gateway and extracts the fields that matter from each row.
- Google Pay over UPI, plus bank portals over IMPS, NEFT and UPI
- UTR, amount, sender name and sender detail extracted per row
- Parallel capture across a small pool of tabs with one live session per site
- Separate pools per payment type, so rails never cross-match
Matching engine
Compares incoming payments against the pending queue on its own loop, independent of any browser.
- Matches on UTR and amount together, never on amount alone
- Runs every second or two as pure database work
- Deduplicates on capture and again on match
- Keeps synthetic resubmission references out of real counts
Approval automation
Resolves the routine volume without a human and proves the result before recording it.
- Auto-approve the instant a verified match exists
- Auto-reject after a configurable timeout when no payment arrives
- Verify-before-persist, so the database cannot drift from the platform
- Stuck entries cleared automatically
Deposits and withdrawals
The same matching, decision and audit rules apply to money moving in either direction.
- Pending withdrawals picked up and matched like deposits
- Identical approval rules and identical audit trail
- One view of net movement per day
Human in the loop
The genuinely unclear cases go to a person, instead of being automated away.
- Reused references, amount mismatches and cross-pool duplicates
- Each row arrives with its prior history already attached
- Reviewer spends seconds deciding instead of minutes investigating
- Every manual decision is recorded with its actor
Two-way platform sync
Keeps the dashboard and the trading platform in permanent agreement.
- Decisions made here are mirrored onto the platform
- Decisions made there are imported automatically
- New platform entries are created in the dashboard
- The platform status always wins
Live dashboard and alerts
Streamed in real time, so the state of the day is never a guess.
- Cards and counters update as events happen, with no refresh
- Today's requests, approvals, pending, rejections and profit or loss
- In-app notifications for the events that need attention
- Optional alert on session expiry, so you are never silently offline
Reporting and audit
Finance-ready numbers that do not need re-keying, and an answer for every number.
- Daily ledger grouped by day and by gateway, with per-day totals
- Profit and loss across day, week, month and all time, plus a 30 day trend
- Gateway performance, match rates and health
- Per-client deposit history and approval rates
- Every action logged with its actor and timestamp
Four layers, one process per isolated environment.
Nothing in the approval path depends on an outside service. Your browser, your engine and your database all run in your own setup. No other company shares it.
Sources
- Google Pay (UPI)
- Bank portals (IMPS, NEFT, UPI)
- Trading platform
Capture
- One persistent browser
- Isolated session per site
- Parallel tab pool
Engine
- Matching loop
- Decision rules
- Audit writer
Surface
- Live dashboard
- Ledger and P/L
- Alerts and notifications
How fast each stage runs.
A new payment is matched and approved in seconds after it appears in your gateway. Not in minutes, and not at the end of a shift.
Cadences are configurable per deployment. The matching engine is deliberately separated from the browsers, so a slow page load never delays an approval.
Watch it clear your queue.
Bring a day of real deposit activity to the demo. We will run it through the engine and show you exactly what it resolves on its own.