Precise answers about what AMIN does.

AMIN is a multi-tenant operating environment for governed compliance work. It connects customer and entity intelligence, due diligence, screening, cases, decisions, evidence and trusted client collaboration across dedicated staff and client workspaces.

Point tools usually address one check. AMIN coordinates the work around those checks: requests, review queues, case ownership, permissioned decisions, evidence and follow-up obligations. It collects identity evidence and supports sanctions screening; it does not claim automated identity verification, biometrics or autonomous compliance decisions.

Yes. AMIN supports governed customer onboarding and entity onboarding with KYB records, ownership and UBO information, configurable forms, document requests and review. Identity Evidence means collecting and reviewing identity information and supporting documents—not automated document-authenticity or liveness verification.

AMIN implements sanctions-list ingestion, matching, alert creation and disposition against configured UN, OFAC, EU, UK HMT and UAE Local list versions. Alerts can move into review and escalation with recorded context. PEP, adverse-media coverage and continuous automatic re-screening are not presented as current capabilities.

Cases move through permissioned states with owners, tasks, queues and accountable decisions. Supported workflows can include role-scoped review and approval controls, including Compliance Manager and MLRO involvement. AMIN does not imply that every operation is governed by a universal maker/checker rule.

AI can assist with context assembly, summaries and review preparation inside governed workflows. It does not autonomously approve, reject or determine compliance outcomes: people retain decision authority, while AMIN governs and records the process.

The dedicated Client Portal gives authorised clients OTP-protected access to requests, forms, documents, KYC information, renewals, requirements, vault items and profile functions. Staff and client access use separate route and authentication boundaries.

Obligations, policies, requirements and follow-up work can be connected to cases and operating context so teams can see why work is required and what remains due. Exact regulatory content and coverage are confirmed during solution scoping.

AMIN records workflow history around actors, actions, authority and case context. Evidence packages and controlled reporting outputs can support review and reconstruction; they are not regulatory filing services or a claim of guaranteed compliance.

AMIN includes governed API keys, a versioned OpenAPI contract, generated SDKs, public API services and webhook delivery controls with retries. Integration scope and data boundaries are confirmed during enterprise evaluation; this page does not claim unsupported named partner integrations.

Staff and clients use separate access surfaces and authentication flows, with role and tenant-aware controls. The currently evidenced deployment model is tenant-isolated SaaS; hosting, residency, provider and institutional control requirements are confirmed during enterprise scoping before any availability commitment.

Begin with a focused product walkthrough, followed by a security and governance review and deployment scoping. Each stage produces explicit scope, evidence, ownership and architecture outputs before implementation decisions are made.