The mule account is the real weapon.
Pratyaksh is the receiving‑side defence.
Eight vendors compete to score the sender. None rate the receiver, freeze inside the golden window, or join bank‑side mule signals with payer identity. We do all three.
The numbers we operate on
Trying to make customers un‑foolable
is an unwinnable war.
Fraudsters no longer need an OTP. They socially‑engineer victims over days or weeks until the customer authenticates the transaction willingly. That single word — willingly — flips the legal question from did the bank fail? to did the customer fail?
The signals exist. Bureau, Signzy, Clari5, Wibmo, Hyperverge, IDfy, Effectiv, NPCI EFRM — eight vendors actively sell sender‑side detection to Indian banks. RBI's own MuleHunter.AI is free to 23 banks.
No incumbent operates on the receiving side, with consumer transparency, in the 24‑hour golden window where money becomes recoverable.
Where the effort lives today
Three checkpoints. Two milliseconds.
One audit trail.
Pratyaksh is a Rust SDK + service that plugs into your routing path. Before money moves, we score the receiving account on behavioural heuristics + bank‑side mule signals. If the transaction goes through and turns out to be flagged, we file the CFCFRMS report inside the 24‑hour golden window automatically. Every decision is anchored to a verifiable consent ledger.
What we shipped to do this differently.
Pre-routing destination‑bank mule‑risk score
Before your routing engine commits to a corridor, Pratyaksh scores the receiving account on dormancy × sudden inflow, cashout velocity, and fan‑in from many distinct senders. Composes any/all of NPCI EFRM hash signals and (where opened) MuleHunter.AI emissions.
CFCFRMS auto‑reporting in the 24h golden window
The single biggest leverage point in the Indian fraud stack: most CFCFRMS reports miss the first‑hour reversal window. Pratyaksh pre‑files the structured report the moment a flagged transaction posts — turning the fastest possible report into a default rather than a procedural fight.
KYA × mule‑flag consent join
Joins your KYA identity on counterparties with bank‑side mule‑flag emissions where consented. The policy plane and the routing plane stay in one decision, anchored to a Kavach consent ledger. Future‑proofs the "we never settled to a flagged account" guarantee.
Numbers we didn't make up.
Pratyaksh's design rests on five RBI / Medianama / SOP-data points that we ground‑truthed against multiple sources before writing a line of code. Caveats and corrections from our research briefing.
Built for the rails that need this most.
Beta cohort prioritises operators who can act on a receiving‑side score immediately. Larger commercial banks already have MuleHunter; we'll come to them when the integration story justifies it.
Join the beta. Move first.
We're rolling beta invites from June 2026 to a small cohort of SFBs, NBFCs, and forward‑leaning underwriters. Early partners shape the integration surface and get founder access through the build.
If receiver‑side mule risk is in your remit and the 24‑hour golden window is a number you've measured (or wish you could), we want to hear from you.