Choose one workflow
Name the fraud decision, the bank owner, and the question the controlled review should answer.
Security and deployment
Work beside the systems your bank already trusts
Test Rule of Record without replacing the bank's fraud tools or decision process.
Start with approved data
Use approved exports or read-only integration points for the first controlled review.
Approve each input
Use approved exports or read-only integration points for the records the bank chooses.
Run beside the current process
Compare the records without changing the bank's live fraud workflow or decision authority.
The bank defines the data boundary
The bank decides what enters, where it is processed, who can access it, and how long it stays.
Data and processing
Define which information may enter, where it may be processed, and which systems remain authoritative.
Access and review
Name who may open evaluation records, how access is granted, and how access is reviewed.
Retention and correction
Agree on retention, deletion, legal hold, export, and later corrections before bank information enters.
Test security and operating controls
Review security, failure behavior, incident response, operating ownership, and support before live use.
Security testing
Review the safeguards and testing required for the agreed data and workflow.
Failure behavior
Define what happens when a connection, check, or record is unavailable.
Incident response
Set the notification, investigation, and escalation path before live use.
Operating ownership
Name the bank and Rule of Record owners responsible for support and change control.
Keep deployment and exit under bank control
The bank approves production integration, third parties, operating changes, and its exit path.
Review the wire fraud evaluation