Encryption in transit and at rest
Exchanges with the platform run over TLS; sensitive data is encrypted in storage. No authentication data is kept in clear text.
Security
What protects the funds and the data
A platform holding balances and personal data has to answer for two things: that nobody sees what isn't theirs to see, and that every movement leaves a verifiable trace.
The technical guarantees
Role-based access control
Rights are carried by roles, not by people: who can issue, who can approve a batch, who can only view. A change of duties becomes a change of role.
Per-company isolation
Each organisation sees only its beneficiaries, its wallets and its movements. Isolation is enforced at the query, not left to interface filtering.
Complete audit trails
Issuance, top-up, spend, cancellation, configuration change: every action is timestamped, attributed to its author, and remains available.
Revocable API keys
One key per integration, shown in clear text once, revocable at any time. A revoked key is refused immediately.
Signed webhooks
Events pushed to your systems carry a signature to verify, so a forged call cannot pass itself off as the platform.
The rule applies at the transaction
Daily cap, permitted merchant category, expiry date, available balance: these checks run at the moment of payment. Spending outside the rules is declined at the till — it isn't discovered the next day on a report.
Reporting a vulnerability
If you believe you have found a flaw, write to us describing the behaviour observed and how to reproduce it. We acknowledge receipt and keep you informed of how it is handled.
A security question before going further?
Do your technical team or your CISO want detail on the architecture, the isolation model or data retention? Write to us — we answer in detail.