DEMO — SENTRYFOX — REGULATED COMMERCE CONTROLRepresentative data. Nothing here is a real merchant or a real transaction.ALL DEMOS →
SentryFoxby Altiras
SENTRYFOX
SYSTEM
Institution Rules
The institution's risk appetite as data. What it will accept, what it will not, and what needs an exception.
RULEKINDSET BYPROGRAMSEXCEPTION
Prohibited categories
Absolute
INST-A
All
NONE
Participant cap
Threshold
INST-A
Research Commerce
BY APPROVAL
Monthly volume ceiling
Threshold
INST-A
All
BY APPROVAL
Rail availability
Enumeration
INST-A
All
BY APPROVAL
Sanctioned jurisdictions
Absolute
Statutory
All
NONE
Dispute ratio ceiling
Threshold
INST-A
All
AUTOMATIC REVIEW
Exceptions
- An exception is a record
- Granting one writes who granted it, against which rule, for which participant, for how long, and on what reasoning. An exception nobody can find later is indistinguishable from a rule that was never enforced.
- Absolute rules have no exception path
- Prohibited categories and sanctioned jurisdictions carry NONE, and the product provides no route to an exception. A field that exists gets used.
- Exceptions expire
- Every granted exception carries an end date. Permanent exceptions are rule changes, and rule changes go through a policy version.
Risk appetite is data, not documentation
These rows are what the eligibility engine actually reads. A risk appetite that lives in a policy document and a system that enforces something slightly different is the gap examinations are designed to find.
DEMO — FIXTURES ONLY, NO DATABASE

