Five stages, and none of them waits for a person.
Each stage does one job and hands off cleanly. Reading payments, matching them, deciding and reporting all run separately. If one part is slow, the others keep working.
- 1
Capture
Read every gateway
Loop Trade continuously reads the transaction lists from each configured gateway: Google Pay and your bank portals.
- Extracts UTR, amount, sender name and sender detail from every row
- Runs many gateways in parallel across a small pool of browser tabs
- Keeps one persistent, logged-in session per site
- Keeps each payment method separate, so a UPI payment is never matched against a bank transfer
- 2
Match
Compare on UTR and amount
A dedicated matching engine compares incoming payments against the pending deposit queue, keyed on UTR and amount together.
- Runs on its own tight loop, independent of the browsers
- Never matches on amount alone
- Deduplicates on capture and again on match
- Keeps synthetic resubmission references out of real payment counts
- 3
Decide
Approve, hold, or time out
A verified match is approved immediately. A request that never receives a matching payment is auto-rejected when its timeout expires.
- Auto-approve the instant a verified match exists
- Auto-reject after a configurable timeout
- Verify the result on the platform before writing it to the database
- Hold anything unclear for a human instead of guessing
- 4
Sync
Mirror both directions
Approvals and rejections are mirrored onto the trading platform, and decisions your team makes there are read back into the dashboard.
- The platform status always wins, the dashboard follows it
- Team decisions made on the platform are imported automatically
- New entries found on the platform are created in the dashboard
- No divergence, and no question of which system is right
- 5
Report
Stream the whole day
Every event streams into a live dashboard: payments received, requests processed, automation rate, gateway performance and profit or loss.
- Live streaming dashboard, sub-second on events
- Daily ledger grouped by day and by gateway
- Profit and loss across today, this week, this month and all time
- Complete audit log with the actor and timestamp on every change
The remainder is the safety margin.
Around nine in ten requests never touch a person. The rest are not failures, they are the cases where a human decision is genuinely the correct answer.
We show reused references, duplicates and mismatches. Each one comes with its full history. Your reviewer decides in seconds, not minutes.
The engine stops at the point where evidence runs out. It does not estimate, and it does not approve on a partial signal.
Cadences you set, not hard-coded delays.
Gateway polling, platform sync and the reject timeout are all configurable per deployment.
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
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.