Workspace isolation
Scope access to the authenticated workspace and environment. A request should not expose another workspace’s records.
Operating controls
Clear permissions.
Traceable settlement decisions.
The security model covers both access and financial integrity: who can act, which instruction they authorize and what evidence supports the result.
The product security model
Separate permissions
Creating an instruction, authorizing settlement and administering a workspace are separate capabilities. Separation of duties follows the workspace policy.
Financial integrity
Authorized terms stay attached to the instruction. Status changes, execution observations and reconciliation need a traceable record.
Integration trust
Keep credentials on server boundaries, verify incoming events and use idempotency for retryable operations.
These are product design principles. Deployment controls and assurance evidence should be reviewed for the specific engagement with our team.
What the public preview provides
The website workspace runs on demonstration data. It has no connected payment provider or financial authorization and does not move money.
Private walkthroughs can use a shared access code enforced before workspace files are served. That preview gate is not customer account authentication or proof of production readiness.
Discuss security requirements
Contact our team to review your access model, data handling, operating responsibilities and integration acceptance criteria. This page does not claim a certification, regulatory approval or independently audited production deployment.
For an initial inquiry, share business context only. Do not submit account credentials, identity documents, bank details or sensitive customer records.
Read about inquiry privacy →