Transaction intake
Request an inline assessment or submit for later processing. Asynchronous intake provides a receipt and a way to retrieve the completed outcome.
Express-O · Fraud operations
Screen transactions with explainable rules, review activity received from connected systems, and manage fraud investigations with independent approvals and an auditable case history.
Screening and investigation
Give fraud analysts and supervisors one workspace for transaction decisions, manual reviews, and investigations. Teams can see which policy produced an assessment, review even transactions the rules allowed, and record the evidence and approvals behind a case.
The current prototype uses synthetic data, including an isolated transfer between accounts on the same Express-O core. A live rollout requires validation of transaction coverage, bank identity and permissions, policy calibration, financial controls, and end-to-end acceptance testing.
Review your requirements with us →The fraud operations workflow
Received activity stays connected to its assessment and any subsequent review. Investigators can open a case when the evidence warrants one.
Bring in activity from agreed sources and retain its reference.
Apply bank-defined rules and capture the decision and its reasons.
Examine received activity and open an investigation where warranted.
Record evidence, approve the case disposition, and retain the history.
The designated financial system remains authoritative for postings, balances, restrictions, and holds.
Product capabilities
Follow the original decision through analyst review, case resolution, and policy tuning.
Request an inline assessment or submit for later processing. Asynchronous intake provides a receipt and a way to retrieve the completed outcome.
Evaluate transaction signals and recent activity against a versioned policy. Record the rule reasons behind allow, challenge, review, and deny decisions.
Review transactions received by FMS, including allowed, flagged, and pending activity. Apply an independently approved classification while preserving the original assessment.
Log a complaint before its transaction is identified. Assign cases, link activity, retain notes, and route dispositions and closures for independent approval.
Track dispute deadlines, notices, and responses in the case workspace. Retain scoped evidence and capture operational reports as of a defined cutoff.
Draft threshold changes, replay scenarios against the current policy, and require independent approval before handing the new version to operations.
Modular architecture
FMS uses defined API and event interfaces. It retains the fraud decision and case evidence while the designated financial system owns the transaction outcome.
Core banking, payment, or channel systems supply agreed transaction data.
An authenticated interface records the request and supports inline or queued assessment.
Versioned rules evaluate risk and retain the decision with its reasons.
Reviewers classify transactions, investigate cases, and record approvals and evidence.
Retained assessments and case history support review alongside the financial system’s records.
Operational safeguards
A second authorized operator reviews controlled classifications, case decisions, and proposed policy changes.
Original screening results remain available alongside later classifications, case activity, evidence, and the policy version used.
FMS owns screening and investigation records. Connected financial systems enforce approved financial actions through agreed interfaces.
Integration context
FMS is designed to connect to different core banking and financial systems through adapters. Confirm source coverage, available interfaces, and integration responsibilities for your institution.
Explore the core banking platform →Let’s plan your next step
Tell us which systems, transaction flows, and fraud operations you want to evaluate.
Discuss your requirements