Tenant isolation
Each subscribed organisation operates within its own tenant context. Tenant data is intended to remain separated from other customer organisations.
Security & compliance
Controlled access and traceable operations by design
SaftaOS is designed to help remittance businesses manage sensitive operational and financial records through tenant boundaries, role-based access, structured workflows and retained activity history.
Tenant isolation
Role-based permissions
Office-aware access
Audit history
Evidence retention
Controlled financial workflows
Core safeguards
Security controls aligned with operational responsibility
SaftaOS applies access and workflow controls according to the organisation, office, user role and operational responsibility.
Role-based access
Permissions are assigned according to user responsibilities so that authorised users can access only the functions relevant to their roles.
Office-aware control
Operational access can be restricted by office and business context, supporting local responsibility within multi-office organisations.
Activity history
Important actions and status changes can be retained with user, time and operational context for later review.
Evidence retention
Payment, collection, settlement and compliance records can retain supporting evidence linked to the relevant activity.
Separation of duties
Transaction, settlement, treasury, finance and administrative responsibilities remain separated through dedicated workspaces and permissions.
Access governance
Access follows the user's responsibility
SaftaOS is designed to avoid a one-access-level model. Different user categories can be given different capabilities and information boundaries.
Platform administration
Platform-level responsibilities remain separate from tenant operational administration.
Tenant administration
Authorised tenant administrators can manage approved users, offices and organisation-level configuration.
Operational users
Cashiers, transaction officers, managers and finance users can be restricted to their authorised functions.
Correspondent users
Correspondent access can be limited to assigned transactions and responsibilities without exposing the tenant's broader environment.
Data handling
Structured records with controlled context
SaftaOS organises customer, transaction, correspondent, settlement, treasury and compliance information into structured records rather than unconnected messages and files.
- Tenant-scoped records
- Office and operational context
- Controlled customer information
- Linked transaction evidence
- Structured financial records
- Restricted correspondent visibility
Customer responsibility
Each customer organisation remains responsible for its own data-governance, retention, legal and regulatory obligations.
Authentication & access
Access is tied to authorised users
SaftaOS uses authenticated user access and role-based permissions to restrict operational functions according to assigned responsibility.
- Named user access
- Role-based permissions
- Tenant access boundaries
- Office-aware restrictions
- Administrative-role separation
- Restricted correspondent access
Least-access principle
Organisations should assign only the access required for each user's current operational responsibilities.
Audit & traceability
Important actions remain connected to their operational record
Transaction and financial workflows can retain status changes, responsible users, timestamps and supporting evidence to help explain how a record reached its current state.
- User and timestamp context
- Status-change history
- Transaction timeline
- Payment and collection evidence
- Settlement-action history
- Administrative activity records
Traceability, not automatic compliance
Audit records support review and accountability but do not replace an organisation's legal, regulatory or independent assurance obligations.
Financial controls
Sensitive financial actions remain within controlled workflows
SaftaOS separates transaction processing, correspondent settlement, treasury activity and profitability review into dedicated workspaces.
- Controlled status lifecycles
- Settlement approval stages
- Treasury obligation records
- Payment and receipt evidence
- Allocation status controls
- Finance-review separation
Clear financial responsibility
Operational modules record their own responsibilities while Finance and Profitability remains the controlled location for financial analysis.
Compliance support
Compliance information connected to the underlying activity
SaftaOS supports structured customer, KYC, risk, AML-decision, evidence and transaction-status records for authorised compliance review.
- Customer KYC records
- Risk-profile information
- AML-required decisions
- Transaction compliance status
- Supporting document references
- Compliance and risk reporting
Important limitation
SaftaOS supports compliance workflows. It does not provide legal advice, guarantee regulatory compliance or replace required professional review.
Shared responsibility
Secure technology and responsible operations work together
Platform safeguards are only one part of a secure operating environment. Customer organisations must also maintain appropriate user administration, internal policies, device security, staff training and regulatory oversight.
- Access-control framework
- Tenant and role boundaries
- Structured operational workflows
- Activity and evidence records
- Appropriate user assignments
- Password and device practices
- Internal approvals and supervision
- Legal and regulatory compliance
Public security information
Need further technical information?
Detailed security, hosting, deployment and data-handling information can be discussed during the commercial and implementation process, subject to appropriate confidentiality controls.