The intended architecture prioritizes isolation, access control, integrity and auditability.
Every organization-owned record carries an organization_id. There is no cross-organization access path in the application.
Access is governed by roles: ADMIN, PAYMENT_OPS, COMPLIANCE, RISK, FINANCE, AUDITOR and VIEWER.
The control center sits behind email/password authentication with server-issued, http-only session cookies.
Finalized evidence packages are hashed (SHA-256) so their integrity can be independently verified.
Audit logs are designed to be append-only from normal users, preserving a record of actions.
The demonstration environment uses only synthetic data. No production payment data is present.
For Stellar proof, only a hash is attested. Sensitive payment and customer data remains off-chain.
What we do not claim
TUGMA does not claim to be SOC 2 certified, ISO certified, penetration tested or bank-grade certified, and does not claim to be approved or certified by any government authority. Any such assurances would be stated only if and when they are actually performed and verifiable.