1
Create the authorisation
Choose what is being collected or authorised, who is collecting it, the receiving organisation and the validity window.
HOW GATECODE WORKS
Create. Share. Verify.
GateCode is a temporary-authorisation layer for collections, handovers and access. The authoriser creates the permission, the collector presents the friendly code, and the receiving organisation checks its current status.
Example authorisationACTIVE
GC-7K4M-92
AuthorisationVehicle / key collection
CollectorSarah Mensah
Valid until16:30
One workflow across different kinds of handover.
Schools can use the specialised School Pickup module, while parcel, vehicle, property, care, visitor, item and custom authorisations use the same underlying GateCode engine.
2
Share it your way
Copy the secure collector link or use WhatsApp, SMS or email. The friendly GateCode can also be spoken or written down.
3
Verify against the live server
The organisation types the GateCode or scans its QR. Manual and QR checks use the same live validation route.
The permission stays understandable.
◷
Upcoming and active windows
A GateCode can exist before its valid-from time, become active during the approved window and expire automatically after the valid-until time.
×
Revocation remains available
The authoriser can revoke a GateCode early. A later verification check sees the revoked state from the server.
↗
Optional collector pass
The secure pass is convenient, but it is not mandatory. A collector can present the friendly GateCode without having a GateCode account.
✓
Verification is an event, not consumption
A successful check is recorded for audit history while the GateCode can remain active until its validity window ends or it is revoked.
NO COLLECTOR ACCOUNT REQUIRED
Get started →Keep temporary authorisation temporary.
The collector does not need to register just to complete a handover.