ZIMRA FDMS Sandbox documentation

Mutero-hosted ZIMRA FDMS-compatible Online gateway for third-party Virtual Fiscal Device (VFD) developers and Mutero itself. Real device certificates, strict RCPT/DEV/FISC validation, async closeDay — practice fiscalisation before ZIMRA Live.

Not official ZIMRA
This is a Mutero-hosted FDMS-compatible sandbox. Homologation and production fiscalisation still require ZIMRA Live (or ZIMRA sandbox credentials). Offline submitFile is out of scope for v1.

Quickstart

  1. Sign in to the sandbox console (Mutero account · no subscription required) and generate credentials, or POST /api/devices/generate.
  2. Create a CSR (CN preferably ZIMRA-{serial}-{paddedDeviceId}) and call POST /registerDevice with certificateRequest (or csr).
  3. On protected endpoints, present the issued device certificate via mTLS or header X-FDMS-Device-Certificate (PEM). Always send DeviceModelName / DeviceModelVersionNo (e.g. Mutero / 1.0).
  4. Flow: getConfig → openDay → submitReceipt → closeDay → poll getStatus until FiscalDayClosed (or FiscalDayCloseFailed).

Device auth (mTLS)

Sandbox issues real X.509 certificates from the Mutero Sandbox CA. Deployments behind a TLS proxy can forward the client cert; Next.js/serverless clients (including Mutero VFD) may send X-FDMS-Device-Certificate. Thumbprint must match the cert stored at registration.

Differences vs ZIMRA

  • Branding and CA are Mutero, not ZIMRA.
  • Online-only v1 — no offline file protocol.
  • Credential generate helper for DX (deviceID + activationKey).
  • Same class of RCPT/DEV/FISC rejects Mutero's mapper aims for.
Error catalogOpenAPI JSONOpen console