Skip to content

Mobile-ID Digital TrustISO/IEC 27001:2022 · SIS351224I008Published certification scope

View evidence

DEVELOPER

Event Catalog

Consume business state-change events as versioned, replay-tolerant facts rather than assuming exactly-once ordered delivery.

01 / CONCEPT

Integration contract

01

Semantics

Event name describes a meaningful state transition, not an internal database operation.

02

Envelope

Event ID, version, occurred time, subject/context references and correlation are explicit.

03

Consumer

Idempotent consumer tolerates duplicate and out-of-order delivery.

04

Evolution

Additive changes are preferred; breaking changes require a new contract/version.

02 / WORKFLOW

From sandbox to evidence

01Select event and version
02Authorize subscription
03Validate envelope
04Deduplicate by event ID
05Apply state transition defensively
06Record consumer outcome/correlation

03 / SECURITY & PRODUCTION

Production is an evidence decision

Event consumers must be replay-tolerant and idempotent; event delivery should not be treated as exactly-once or perfectly ordered unless the specific contract guarantees it.