Security
Security is a property of the design, not a feature added to it.
A system that decides when money may move has to be able to prove who did what, and has to make the wrong thing difficult by construction. This page states what is in place today and what is not. Dhira Pay holds no certifications yet and claims none.
In place
Tenant isolation
An organization sees only transactions it is a party to. Enforced in the query layer and again by row level security in the database, so a mistake in one layer is caught by the other.
In place
Two layer authorization
Every action needs a role that permits it and a position in the transaction that entitles the organization to take it. A non-party is told the transaction does not exist.
In place
Separation of duties
Accepting work and approving the release of funds are different permissions held by different default roles. Administration carries no authority over money.
In place
Tamper evident audit
Every state change is appended to a hash linked chain per transaction. Editing, removing or reordering a record breaks the chain, and the chain is recomputed on demand.
In place
Financial facts from the provider only
A financial position changes only when a verified provider event is posted to a double entry ledger. The database refuses a user request that tries to insert one.
In place
Idempotency and replay protection
Duplicate webhooks, retried requests and repeated dispatches are applied once. Webhooks are signed, time bound and rejected if altered.
In place
Evidence handling
Evidence carries a SHA-256 fingerprint, an author, a time and a sensitivity level. Restricted items are withheld from members without the permission.
In place
Input validation and defensive defaults
Every input crosses one schema. Responses never include internals. A strict content security policy allows no third party origin.
Designed, built in a later phase
Production authentication
Credentials, two step verification, passkeys, device sessions, revocation and re-authentication before sensitive actions.
Designed, built in a later phase
Encryption and key management
Encryption in transit and at rest, field level encryption for identity and bank details, managed keys with rotation.
Designed, built in a later phase
Independent assurance
Penetration testing, a security review of the financial paths and external anchoring of audit chain heads before commercial operation.
Personal information
Collect less. Show less. Keep it only as long as the law requires.
Dhira Pay is designed against the Protection of Personal Information Act. It processes the personal information of people who act for businesses: names, work contact details, their role and the actions they take.
One organization never sees the member list of another. Counterparties see a business profile and the names of the representatives named on a shared transaction, and nothing else.
Identity documents and bank details are not collected in this phase at all. They will be collected only when a regulated provider is connected to verify and protect them.