The Digital Post Platform enables secure, structured digital communication between organisations and receivers.
It provides a governed environment for submitting, processing, delivering, and storing official digital messages at scale.
The platform separates governance, communication identities, integration access, message processing, and recipient access into clearly defined architectural components.
This page describes the core components and how they interact at a high level.
The platform consists of the following primary layers:
- Governance Layer
- Organisation and Sender Layer
- Integration Layer
- Delivery and Processing Engine
- Mailbox and Access Layer
- Reporting and Audit Layer
Each layer has a distinct responsibility and security boundary.
Each platform deployment operates under a platform holder.
The platform holder defines:
- Market configuration
- Identity types
- Security policies
- Subscription rules
- Retention policies
- Operational governance
All organisations, sender identities, and integrations operate within this governed context.
Detailed governance and hierarchy behavior are described in the Organisational Model section.
Organisations represent participating entities such as public authorities, financial institutions, or private enterprises.
Within each organisation, one or more sender identities define how communication appears to receivers.
Sender identities control:
- Branding and presentation
- Subscription requirements
- Available message features
- Delivery capabilities
- Permission scope
All envelopes reference a specific sender identity.
Sender configuration directly influences recipient resolution and delivery behavior.
System integrations are authenticated technical clients that interact with platform APIs.
Integrations are responsible for:
- Preparing message body and attachment files
- Generating envelope documents
- Uploading content to object storage
- Creating delivery requests
- Retrieving delivery reports
All API access requires authentication and is evaluated against organisational permissions.
Authentication and authorization behavior are described in the Security Concepts section.
The delivery engine performs asynchronous message processing.
When a delivery is created, the platform:
- Retrieves uploaded envelope and content files
- Validates envelope structure and required fields
- Verifies sender authorization
- Resolves recipients to mailboxes
- Verifies subscriptions
- Scans files for malware
- Performs integrity validation
- Applies encryption for recipient access
- Assigns messages to mailboxes
The platform guarantees atomic delivery per envelope.
Either all recipients of an envelope receive the message, or none do.
Detailed processing behavior is described in:
After successful processing, messages are assigned to recipient mailboxes.
Recipients may:
- View message metadata
- Open message body
- Download attachments
- Trigger receipts
- Use enabled message features
Each recipient receives access to an isolated encrypted instance of the message.
Access permissions are enforced at mailbox level.
The platform provides structured reporting and audit data.
Integrators can retrieve:
- Delivery level status
- Envelope outcomes
- Failure categories
- Processing diagnostics
Audit data supports:
- Operational monitoring
- Incident investigation
- Compliance requirements
- Usage reporting
Delivery reporting is described in the Reporting and Status section.
The typical delivery flow is:
- Integrator prepares message content and envelope files
- Files are uploaded to object storage
- Delivery is created via API
- Platform validates and ingests content
- Recipients are resolved
- Messages are encrypted and assigned to mailboxes
- Delivery report becomes available
Processing is asynchronous. Completion must be verified using the Delivery API.
The platform is built around the following principles:
- Separation of governance and operational execution
- Strong identity based recipient resolution
- Atomic envelope delivery
- Asynchronous processing
- Per message encryption
- Organisational data isolation
- Explicit authorization boundaries
- Full auditability
These principles ensure consistency, traceability, and security across markets and integrations.
This page provides architectural context.
For detailed behavior and models, refer to:
- Organisational Model
- Message Delivery Model
- Message Lifecycle
- Recipient Identification
- Security Concepts
- Status Reporting
Together, these sections describe how the platform operates end to end.