At a glance
eSentinel vs Open FRMS: side by side
Open FRMS and eSentinel start from the same place: a locally built, locally supported engine that scores transactions in real time against rules a bank’s own analysts write. The difference shows on the regulatory and dispute side. eSentinel is built against SBP BPRD Circular 4, opens 1LINK FTDH disputes inside the case that raised the alert, names IBFT, FT and RAAST as monitored rails, and has banks on record running it. For a bank whose examiner asks for Circular 4 evidence and whose fraud desk lives in FTDH, that is the gap worth testing.
eSentinel compared with Open FRMS (Paysys Labs)| Capability | eSentinel | Open FRMS (Paysys Labs) |
|---|
| Real-time transaction monitoring | Yes | Yes |
|---|
| Configurable rules written by the bank's own analysts | Yes | Yes |
|---|
| Behavioural analysis and risk scoring | Yes | Yes |
|---|
| Case management for investigators | Yes | Yes |
|---|
| Built for SBP BPRD Circular 4 | Native | Not stated |
|---|
| Native 1LINK FTDH dispute and chargeback handling | Native | Not stated |
|---|
| IBFT, FT and RAAST named explicitly | Native | Instant payments |
|---|
| Channels named | 14 in one dashboard | Cards, digital banking, remittances, instant payments |
|---|
| Non-financial events and device telemetry | Yes | Not stated |
|---|
| Customer-assisted alert closure (robocall, WhatsApp, in-app) | Yes | Not stated |
|---|
| PCI SSF compliance | Yes | Not stated |
|---|
| Deployment model published | On-prem or cloud | Not stated |
|---|
| Named bank deployments published | Yes | Not stated |
|---|
The Open FRMS (Paysys Labs) column records what Paysys Labs publishes on its own Open FRMS product page. "Not stated" means the capability is not claimed there, which is not the same as the product lacking it. Ask the vendor directly before deciding.