KYC, screening, and threshold rules in a form a compliance officer can read and sign off — the same text the engine executes.
The written policy and the implemented policy drift apart immediately
Evidencing a control means asking engineering to read code aloud
No versioned record of when a screening rule changed, or why
Verify identity, sanctions, and document checks for Know Your Customer compliance.
A **customer** passes kyc_screening
if §customer.identity is valid
and §customer.sanctions is valid
and §customer.document is valid.
customer.identity. A **customer** passes identity_check
if the __full_name__ of the **customer** is not empty
and the __date_of_birth__ of the **customer** is not null
and the __date_of_birth__ of the **customer** is earlier than 2008-03-21.
customer.sanctions. A **customer** passes sanctions_check
if the __sanctions_match__ of the **customer** is equal to false
and the __pep_status__ of the **customer** is equal to false.
customer.document. A **customer** passes document_check
if the __id_document_type__ of the **customer** is in ["passport", "drivers_license", "national_id"]
and the __id_verified__ of the **customer** is equal to true.
Change the policy, change the input, evaluate. The same engine your application would call.
Policy
Input
Age Verification
ComplianceVerify that a user meets the minimum age requirement and is in an allowed region.
Transaction Limits
ComplianceClear a payment when it stays under the reporting threshold, avoids blocked corridors, and keeps the day's cumulative total in range.
Expense Approval
HR & PeopleAuto-approve an expense claim when it is under the role limit and has a valid category.
We will implement your first policy with you.
Send us a rule you currently keep in application code and we will show you what it looks like as a versioned, traceable policy.
Talk to us