Skip to main content

Core concepts

Tenant​

The customer isolation boundary. Users, policies, applications, API keys, webhooks, evidence and billing belong to exactly one tenant. Assayra’s production PostgreSQL contract adds forced row-level security below the API authorization layer.

Application​

One verification subject and one policy execution. An application is either individual or business, holds the durable customer reference, and is pinned to an exact workflow ID and version.

Invitation​

The revocable applicant access credential. Creation returns its absolute URL, expiry and delivery state. Invitations can be retrieved, sent, rotated or revoked without creating a second application.

Verification workflow​

The executable assurance policy: which identity/business information, documents, biometric signals, screening and risk outcomes are required. Published versions are immutable. Create an editable successor to change future intake.

BPMN process​

Optional staff and system coordination around an application: human tasks, SLAs, timers and escalations. BPMN cannot directly approve an applicant or bypass the verification workflow. See workflow versus process orchestration.

Evidence and signal​

Evidence is the encrypted source material or authoritative response. Signals are derived, versioned results such as MRZ validity, field agreement, face similarity, liveness/PAD, screening candidates and transaction rules. Hashes bind evidence, inference and decision.

Case and decision​

A case is human work created by review policy, screening, fraud or ongoing assurance. A decision can approve, reject or retain review. Where four-eyes control is active, a maker proposes and a different authorised checker countersigns.

Decision receipt​

An independently verifiable Ed25519 object binding the workflow version, evidence hashes, signal/model versions, screening, actors, outcome and audit anchor. The receipt proves what produced the decision; it is not a generic promise of regulatory compliance.

Country Assurance Pack​

The activation boundary for real automated decisions in a country/use case. It binds policy, residency, document/template coverage, model routes, data freshness and approval evidence. Missing required coverage fails closed.