AFCAS Gateway
System
A cryptographically secured secondary gateway platform for the Automated Fire Safety Compliance System โ receiving enrolled metadata, generating immutable compliance certificates, and issuing verifiable licence cards with encrypted barcodes.
Architecture & Data Flow
The AFCAS Gateway sits as a secure secondary system that receives enrolled applicant metadata from the GNFS Core System. All data is cryptographically sealed into an append-only ledger โ records can only be added, never modified or deleted โ ensuring a tamper-proof chain of compliance for every property in Ghana.
Users & Beneficiaries
The platform serves a wide range of stakeholders across Ghana's property and fire safety ecosystem.
Core Platform Features
System Components
The gateway is composed of five interconnected modules, each handling a distinct layer of the compliance pipeline from data ingestion to physical card output.
Cryptographic Security & Immutability
The entire platform is designed around a zero-trust, append-only architecture. Every record is sealed with cryptographic hashes forming an unbreakable chain โ any tampering attempt is immediately detectable.
SHA-256 Hashing
Every metadata record hashed on ingestion. Hash chain links each record to its predecessor.
Append-Only Ledger
Database enforces write-only policy. No UPDATE or DELETE operations permitted on sealed data.
Asymmetric Encryption
RSA/ECDSA key pairs for barcode encryption. Private key held solely by AFCAS system.
Temporal Tokens
24-hour expiry on all access tokens. HMAC-signed with server-side validation.
TLS 1.3 Everywhere
All API communications encrypted in transit. Certificate pinning on mobile app.
Audit Logging
Immutable audit trail for every system action. Tamper-evident log storage.
Vendor & Third-Party Verification
Vendors, lawyers, land purchasers, and individuals can request property fire safety certification through a registered vendor ID and a temporal token system with monthly metered billing.
Technology Stack
Project Timeline
A phased delivery approach across approximately 26 weeks, with each milestone producing working, testable components.
| Phase | Deliverable | Duration | Status |
|---|---|---|---|
| Phase 1 | Core Gateway API, Metadata Ingestion, Immutable Ledger | 6 weeks | Planning |
| Phase 2 | Token Management, Vendor Portal, Billing Engine | 4 weeks | Pending |
| Phase 3 | Certificate Generation, Public URL, QR Codes | 4 weeks | Pending |
| Phase 4 | Licence Card System, Crypto Barcode, Print Queue | 4 weeks | Pending |
| Phase 5 | Mobile Verification App (Android + iOS) | 5 weeks | Pending |
| Phase 6 | UAT, Security Audit, Deployment & Handover | 3 weeks | Pending |