Five stages, and none of them waits for a person.
Each stage does one job and hands off cleanly. Capture is isolated from matching, matching from deciding, and deciding from reporting, so pressure in one stage never becomes a stall in another.
- 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
- Separates pools by rail, so a UPI payment is never reconciled 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 ambiguous 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's 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.
Reused references, cross-pool duplicates and mismatched resubmissions are surfaced with their history attached, so a reviewer spends seconds deciding rather than minutes investigating.
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 on your own server.
Nothing in the approval path depends on a third party service. The browser, the engine and the database all live on infrastructure you control.
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.