Certification
ZIMRA
The applicant is Thuma Books Zimbabwe (Private) Limited, for the device model ThumaBooks, version 1.0, under ZIMRA's Fiscal Device Gateway API specification v7.2.
- All 22 device requirements in the specification's §9 are met, each with the test that proves it.
- The certification run — every scenario ZIMRA asks for — is rehearsed end to end against a simulator of ZIMRA's system, and waits only on ZIMRA's test credentials.
- Checked against ZIMRA's live systems where no credentials are needed: its published API schema, its signing certificates in test and production, and its onboarding answers.
Status: application with ZIMRA ZIMRA's reference will be published here, with the date, when it is issued. We do not call ThumaBooks "ZIMRA-approved" before then.
Key custody
Where the device's private key lives
Each device's private key is generated in our service and never shown to anyone — not the business, not our staff. It is stored encrypted with its own random data key (AES-256-GCM), and that data key is wrapped by an AWS KMS key that never leaves KMS. Every unwrap is logged.
Credentials and activation keys are taken once to register the device and are never stored or logged.
Integrity
Every receipt checked twice
- Before sending: every one of ZIMRA's receipt rules, so a refusal is caught while it can be fixed.
- After sending: ZIMRA's own signature on the receipt and on every closed day is verified against ZIMRA's certificate.
- Continuously: a sample of our receipts is looked up on ZIMRA's public verification portal and compared with what was sent; any difference becomes an alert.
- Receipts are hash-chained per device, in ZIMRA's order; a gap or a change breaks the chain.
Operations
We hear of trouble first
A day ZIMRA will not close, receipts not reaching ZIMRA for four hours, a certificate a week from expiry: each is shown to the business with what to do, and reaches our operations team at once — so support can call before the business has to.
ThumaBooks' public status page, status.thumabooks.com, checks every live country every minute: the tax authority's system as we reach it — ZIMRA's FDMS today — and ThumaBooks fiscalisation, whether receipts are leaving our queue, with how fast they reach the authority. When receipts wait because the authority is down, the page says it is the authority's, not ours. Each country appears there the day it goes live.
Hosted on AWS in Cape Town (af-south-1), the closest region to Zimbabwe. An uptime commitment is offered to Enterprise customers once multi-zone failover is in place, not before.
Records
Yours, for seven years
Every fiscalised document, its receipt as ZIMRA received it, ZIMRA's signature and the day reports are kept for seven years on every plan, and export in full. A lapsed subscription never holds back what was already signed.
API security
Keys, partners, webhooks
- API keys are shown once and stored only as a fingerprint.
- A reseller acts for a business only after that business grants it, and loses access the moment it is removed.
- Webhooks are signed (HMAC-SHA256 with a timestamp) and only go to public https addresses.
Accessibility
Built to WCAG 2.2 AA
Keyboard-operable throughout, with visible focus; text contrast of at least 4.5:1 in both themes; controls at least 24 px; status changes announced to screen readers; nothing that relies on colour alone — a greyed country also says "Coming soon". The QR code always has its verification code beside it as text. Tell us where we fall short: hello@thumabooks.com.
Report a vulnerability
Responsible disclosure
Found a security problem? Email support@thumabooks.com with "Security" in the subject. We acknowledge it, keep you informed, and do not pursue good-faith research.