Double verification

A payment is only trusted when the regex and the AI parser agree — this page defines what “agree” means.

Comparison mode

Which parser results must match before an order can be approved.

Require regex match The deterministic rule engine decides; AI output is logged only. Fastest, but blind to message formats without a rule.

Require AI match The model must extract every required field correctly. Handles any format, but a single payment trusts one call.

Require both Regex and AI must extract the same values independently. Strongest guarantee — this is the recommended mode.

Allow AI fallback when regex fails

If no rule matches the message, continue with AI alone — capped at manual review unless the amount and reference match exactly.

The final score decides the outcome. Type a number to move the band edges.

Manual review from (%)

Auto-approve at (%)

Reject — below 70%

Manual review — 70–94%

Auto-approve — 95% and above

Today: 93% of verified payments cleared the auto-approve band without human touch. Lower the review edge and more cases are checked by your team.

Fields a matched transaction must satisfy before the order can be approved.

Transaction ID must match

The submitted UTR / reference must appear exactly in the bank confirmation.
Amount must match

Detected amount must equal the order total — short payments go to manual review.
Currency

The confirmation must be in the order’s currency — no implicit conversion.
Receiving account

Money must have landed in the account shown at checkout (HDFC ····4921).
Sender name

Compare the payer name with the checkout customer when the source exposes it.
Payment window

Confirmation must arrive within ± 24 hours of the submitted reference.

Required rules that fail send the transaction straight to manual review, whatever the confidence score says.