LOADING
Four products, each with an account loaded with representative data, and the shared services you can walk through underneath them. No signup, nothing to install. Demo and production run the same code against different data, so what you click through is what the product does.
Pick Professional services, then Specialty & regulated, and watch the requirement count change from four to nine.
Open Northgate Reagents. The timeline says the merchant was suspended but not why — that is the agent scope boundary in practice.
The compliance tab shows the finding reached you, the processor and the sponsoring bank at the same second. Nothing was routed through anyone first.
Open Findings. There is no close button anywhere on the screen, because the operation does not exist in the platform.
Services live in the Cloud rather than inside any one portal, so most of them are experienced through whichever product surfaces them. Status is honest — partial means part of it exists and part does not.
Open Program Builder and look at the rules reading unconfigured. They are stops, not blanks — an unset ship-to classification is why orders are failing closed on Geography, and nothing had to remember to prevent it.
Pick a scenario from the demo bar. 'Patented compound' stops before payment renders; 'Ordinary order' clears and shows two rails, not three, because one SKU restricts ACH.
Eighteen gates, deterministic, failing closed on every unknown. Run 'Unknown jurisdiction' — no rule on file for the ship-to region blocks rather than defaulting to permitted.
BRD-9002 sits suspended on an expired certificate. The document drives the product state, and no role can lift it.
Northbeam Utilities shows EXPIRED with no second factor. The merchant sees that state and can act on it, and never sees the identity documents behind it.
Version history and expiry on every document. The expired COA is why a SKU cannot be sold — the document is upstream of the product state.
A named contact assigned at activation rather than a queue, with the ticket history attached to the account.
Ask whether a support agent can close a finding. It retrieves the no-suppression rule and the Compliance Engine's never-holds list — assembled, not authored.
Demo and production are one build. There is no separate demo application that could drift from the real one.
No merchant in these accounts exists. No transaction settled. No finding was raised against anyone.
Every surface reads fixtures. Changes you make in a demo are not saved and affect nobody.
