Fintegrity replaced the ad hoc scripts with a single compliance decisioning API called at the point of transaction. Customer tiers based on CDD level (BVN-verified, NIN-only, unverified) were encoded directly into the rule engine, so wallet limits and monitoring sensitivity adjust automatically as a customer's verification status changes.
Every decision — CLEAR, FLAGGED, HELD_FOR_REVIEW, or BLOCKED — is written to an append-only evidence store with a server-side timestamp, the rule version that produced it, and the inputs considered. When a regulatory request for a specific customer's history came in, the compliance team retrieved a complete, exportable record in minutes rather than reconstructing it from application logs.
Because the decision layer sits in front of the transaction rather than behind it, high-risk transactions from unverified accounts are held for review before funds move, not flagged for cleanup afterward.