GATE — Verify.
Who may enter the ecosystem. GATE provides hosted KYC and party surfaces and is designed to connect verification, screening and review — subject to provider, flag, data and integration coverage.
What GATE owns
- Hosted KYC and party read surfaces; tiered KYB, director and ownership workflows are design targets, while UBO capture is absent from the reviewed UI
- White-label hosted verification and API-led embedding, each conditional on the selected provider and integration
- Identity-document, provenance, reviewer-note and override fields where the producing workflow records them
- Designed step-up and re-verification triggers, subject to configured rules and available events
The target architecture links GATE verification with SENTINEL screening, DOCKET casework and VAULT evidence. In the reviewed status, the KYC review route is feature-flagged, UBO capture is absent, screening uses a labelled demonstration source, and handoff and audit coverage must be verified rather than assumed.
The designed onboarding decision flow
Create party
A configured signup or KYB submission can create a person or business party with the data and documents actually supplied; current UI should not be represented as capturing UBOs.
Assign tier
A designed policy can assign a verification tier from activity and risk. Record the reason only where the engine exposes that field.
Screen
SENTINEL can contribute screening results when an approved provider or list source is integrated. The reviewed source is a labelled demonstration list, not complete sanctions, PEP or adverse-media coverage.
Apply policy
Configured geo, age and product rules can be evaluated against available verified data; coverage depends on the policy and data source.
Decision
Approve, review, step-up or block may be represented in a Decision Record with only the rationale fields actually recorded, plus a DOCKET handoff where that integration is enabled.
Working the KYC review queue
Compliance Console → Verify → Review queue is a designed and feature-flagged route in the reviewed status, not a generally available complete workflow. Where enabled, confirm which documents, extracted data, screening results, SLA fields and actions are present. Capture override rationale only if the workflow records and retains it.
Re-verification and EDD
Risk indicators can be designed to trigger EDD, rescreening or re-verification. Availability, scheduling and cause fields depend on configured rules, provider data and the feature-flagged review workflow; a visible action is not evidence that the end-to-end process is complete.
Use only evidence, metadata, reviewer notes, rationale and provenance actually captured by the workflow. The reviewed GATE surface lacks UBO capture and has a flagged review route, so an evidence pack may be incomplete for a KYB purpose unless supplementary records are added and verified.
Hosted flow vs API-only
The observed hosted KYC surface can support a branded journey where configured. An API-led implementation can place more of the experience in your product, but provider coverage, state transitions, data retention, evidence capture and integration effort must be scoped and validated; neither path is universally fastest or complete.
Want the complete manual as a PDF? Leave us your email and we'll send it over.
Request the manual