DEMO — SENTRYFOX — REGULATED COMMERCE CONTROLRepresentative data. Nothing here is a real merchant or a real transaction.ALL DEMOS →
SENTRYFOX
CONTROL
Eligibility
The pre-authorization decision. Merchant, buyer, product, geography and transaction, evaluated before anything is submitted.
Merchant
requests
SentryFox
verifies
Bank policy
decides
Processor
receives
Only eligible transactions are submitted. The institution defines eligible.
What is evaluated, in order
- Platform
- Policy version in force, then institution and program halts.
- Participant
- Program membership, state, documentation currency, surface scan posture.
- Product
- Approved class, approved item, current documentation.
- Order
- Composition, and cumulative quantity ceiling per item.
- Buyer
- Geography, qualification, second factor, attestation, sanctions.
- Portfolio
- Institution thresholds, then the eligible rail set.
Halts run before anything about the product
A suspended participant with lapsed documentation stops at the halt and the documentation check never runs. The order is deliberate: the most absolute stop comes first, so a halted program cannot be reasoned past by anything downstream of it.
Blocked is not declined
A compliance block and a payment decline are different events with different screens, different records and different buyer messages. They are never merged, and a block never offers a retry or an alternate rail.
DEMO — FIXTURES ONLY, NO DATABASE