Agency OneTrust
Built like a banking system, because it is one.
Where the data lives, how the controls work and what each leaves behind, and the pack your risk team can ask for.
Revised 4 October 2026. Everything on this page describes the platform as it is, and is revised when it changes.
Where the data lives, and who holds the money.
Shared platform
One deployment serves several operators, each isolated at the database itself, so brands, services, partners and books never mix. It runs in a cloud region in southern Africa.
Dedicated instance
Your own environment, in-country where regulation asks for it, on your release cadence. The same codebase and the same controls as the shared platform.
Your settlement bank holds the money
The platform records every movement; a regulated settlement bank you appoint holds and moves the money on the national rails. Its statements are the third leg of the daily match.
The controls, and the evidence each one leaves.
Each control is in the code, so it holds at every counter and can be exercised in a pilot. The right-hand column is what an auditor can ask to see.
| Control | How it works | Evidence it leaves |
|---|---|---|
| Deny by default | Nothing is allowed unless a role permits it, checked on the server for every request. | Each decision, in the audit trail. |
| Standard identity | Staff sign in through a dedicated identity provider on OpenID Connect; sessions and token lifetimes are managed centrally. | Sign-on events and token lifetimes, in the identity provider's log. |
| Two people on risky moves | Publishing a service, taking a provider live, reversals, rebalances and admin grants need a second, different person, from their own login. | The request and the approval, each with its own identity. |
| Every change recorded | Who, when, what changed and why, for every change to money, catalog and access. | The audit trail, kept with the data. |
| One posting per payment | Every write carries a key, so a retried or repeated request finds the first attempt and money moves once. | A reference on every payment. |
| Books in balance | Every movement is recorded twice, in whole thebe, and the books are checked through the day. | A trial balance at P 0.00, any hour. |
| Operators kept apart | Each operator's data is isolated in the database itself, on the shared platform or a dedicated one. | Isolation tests in every release. |
| The bank as the third leg | The settlement bank's statement is matched daily against counters and providers. | The daily match and its exceptions. |
Ask for the trust pack
Assembled for your engagement and sent within two business days. It holds:
- The architecture note: the parts, how they fit, where data lives
- The control list above, with the evidence each control leaves and how to test it in a pilot
- Our data processing terms
- The identity model: roles, what each may do, how two-person control is enforced
No mail app on this machine? Copy the address and write from anywhere.
Ask us the hard questions.
Bring your security, compliance and audit teams; the controls hold up under scrutiny because scrutiny is what they were built for.