Customer-owned VAT number, CR, registered address, business ownership and authorized staff.
NOT PUBLICLY AVAILABLEMCHILS SOFTWARE HOUSE / MULTI-TENANT FISCAL PLATFORM
One platform.
Every retailer independent.
Manage the engineering architecture for multiple Saudi retail clients with segregated merchant workspaces, per-device invoice sequences, scoped staff permissions and an auditable onboarding lifecycle.
MCHILS PLATFORMSTAGING ARCHITECTURE
☁MCHILS EBXSoftware and support
↔
▤ ▤Independent retailersOwn VAT · Own EGS · Own chains
Never combine different retailers' invoices, CSID credentials, QR identities or invoice counters.
Architectural preview, not a customer account system. Both example retailers below are fictional. No production tenants, certificates, encrypted signing keys, FATOORA sessions or government submissions exist in this view. The server-side tenant engine is private and not exposed through this page.
PROVIDER OPERATIONS
Tenant isolation studio.
Switch between fictional retailers to see separated branches, electronic generating units (EGS) and uninterrupted device-level sequences.
Real clients onboarded0None authorized
Fictional tenant examples2Visual architecture only
Fiscal security checks30 / 30Private staging suite passed
FATOORA productionDisabledAwaiting approved CSID
INDEPENDENT FISCAL WORKSPACE · EXAMPLE
NOT ONBOARDEDSelect a retailer
No live data.
Demo branches—Isolated by merchant
EGS units—One chain per device
Tax invoices issued0No official documents
Fiscal devices
Each EGS has its own immutable sample sequence.
Sequence explorer
Select a fictional device to inspect the chain.
| Illustrative ICV | Document type | Prior reference | Sample state |
|---|
These are illustrative counters, not ZATCA-approved invoice hashes. A compliant signed document sequence must be maintained by the actual onboarded EGS, including standard, simplified and linked credit/debit documents.
SECURE MERCHANT ENABLEMENT
From software to compliant service.
These steps remain locked until the respective retailer completes the required legal verification and approved ZATCA onboarding.
Separate retailer license, branch allowances, financial roles and fiscal data retention.
STAGING TESTEDAssign physical/logical devices, secure cryptographic key custody and merchant-specific ZATCA CSR/CSID lifecycle.
NO REAL CSID INSTALLEDOfficial XML, cryptographic stamps, Phase 2 QR, SDK checks, both standard and simplified flows, credit and debit notes.
OFFICIAL SDK PENDINGClearance/reporting queue, response validation, rejection and retry handling, deadlines and error monitoring.
NETWORK SUBMISSION DISABLEDCertified integration tests, finance sign-off, secure archive, recovery, monitoring and customer onboarding acceptance.
PRODUCTION DISABLEDREAD-ONLY PLATFORM STATUS
Checking deployed ZATCA preparation…
The actual Retail API currently provides unsigned demonstration XML drafts. Merchant-specific production integration is not yet configured.
LEGAL TAX INVOICES: NOT ENABLED