Security posture before sales claims
Mozaca separates implemented product controls, public posture, and private diligence so buyers can evaluate evidence without mistaking architecture or roadmap material for formal certification.
Fedha, Hazina and Zent are live — new products on the way. Build with us →
Mozaca Labs builds financial software. The trust that makes that possible is itself an engineering discipline. Here's how we practice it.
How we protect our products and the money that moves through them: the engineering controls, how to report a vulnerability, how we handle data, and where each formal certification stands. Deeper evidence is shared with qualified buyers under NDA.
An illustrative view of verification, ownership, risk review, and the evidence an operator needs to make a decision. Sample data only.
Trust work is attached to the operating model: public posture, controlled access, clear assurance boundaries, and private evidence for qualified diligence.
Mozaca separates implemented product controls, public posture, and private diligence so buyers can evaluate evidence without mistaking architecture or roadmap material for formal certification.
Internal and client work is scoped to named owners, MFA-backed identities, private repositories, role-based access, and written handoff or removal at close.
Financial workflows should produce audit-ready evidence: ledger events, approval state, webhook delivery, reconciliation records, incident notes, and exportable reports.
Fedha and Zent digital-asset flows operate through licensing, partner controls, transaction monitoring, and jurisdiction review so control posture is explicit.
Where each control and certification stands today: what is published here, what we share privately under NDA, and what is still in progress.
Public disclosure, data-handling, incident, access-control, and vulnerability-reporting expectations are documented here for product and diligence review.
We can prepare a control mapping for your diligence review. The formal report will be shared under NDA once it is issued.
Security management practices are being structured around access, data handling, incident response, change control, and vendor review.
Card workflows are scoped through approved providers and PCI boundaries; the public website does not process cardholder data.
The public status page covers website, contact, documentation, product posture, and the controlled-access environment model.
Responsible disclosure contact details are available at /.well-known/security.txt.
Not adjectives — the specific engineering controls that wrap money movement. For formal certification (SOC 2 Type II, ISO 27001), see assurance status above.
TLS 1.2+ in transit and AES-256 at rest across services and data stores.
Data, policy, keys, and rail configuration scoped per client deployment — no shared boundary.
MFA, passkeys, role-based access, and maker-checker approval on every sensitive action.
Append-only, event-sourced journals with hash-chained, correlation-ID'd audit evidence.
Managed secrets, rotated keys, and HMAC-signed webhooks with replay protection.
Audit events, transaction monitoring, and a defined incident-response path with named owners.
Regulated money movement is licensed market by market. For each deployment, the operating entity, licenses, partners, and corridors are confirmed in signed scoping or diligence.
Regulatory references are reviewed per client market and partner path during diligence. This page is not legal advice.
The practical surface of how we run engagements — disclosure, response, and data handling.
Need an SBOM, subprocessor list, or insurance certificate for vendor onboarding? Request via the engagement contact.
Use your evaluation to examine the controls that matter to your organization, with evidence appropriate to the product and deployment under review.
Review role boundaries, privileged actions, approval separation, credential handling, and revocation paths.
Who can do what—and whyReview how state changes connect to users, timestamps, policy decisions, financial journals, and exports.
A traceable chain of actionsAsk how exceptions, provider issues, recovery, and support escalation are handled for the proposed environment.
Clear responsibilities under pressureNo. Public illustrations explain the intended experience. Technical diligence should examine the implementation, scope, operating process, and evidence relevant to your deployment.
Include the stakeholders who will approve the environment. Their requirements help determine the architecture material, control walkthroughs, and supporting evidence needed.