Step 1
Define the decision
Your service sends who is asking, what they need, which policy version applies, and channel context. The format is the same for live API calls and offline packets.
How does MOD verify clearance and estate access without duplicating vetting data?
Binary eligibility for clearance, estate access, and the defence workforce.
Short answer: AffixIO returns a signed yes or no for clearance, facility access, and supplier assurance - evaluated against sources you authorise, without exporting full vetting or HR files to line systems.
Stateless verification · No standing PII store · ML-DSA ready
Programme context
The Ministry of Defence runs one of the UK's most demanding identity and access environments: permanent staff, reserves, contractors, multinational partners, and classified systems. Programmes need to verify facts without duplicating sensitive records across every consuming application.
What teams are solving
Traditional approaches copy vetting outcomes, HR attributes, or registry fields into secondary databases for each new system. That increases breach surface, complicates accreditation, and makes audit trails harder to reconcile across estates.
AffixIO approach: AffixIO sits behind your API gateway and returns a signed yes or no for a defined policy. Clearance gating, estate access, and supplier checks consume the same decision model whether the caller is a web service, a gate reader, or an offline field device.
Where verification applies
- Security clearance gating
Confirm clearable or not clearable for role assignment without exporting full vetting files to line managers or contractors.
- Estate and facility access
Prove current employment or visit authorisation at the gate, including offline validation for remote sites.
- Defence supplier onboarding
Verify professional registration, export control signals, and personnel vetting outcomes through a single API contract.
- Veterans and service leaver handoffs
Confirm service-linked facts for councils and charities without transmitting full service records.
- Cross-domain collaboration
Machine-to-machine decisions between systems at different classification boundaries using minimal attributes.
From request to verified outcome
The same three-step model used across AffixIO applies here: describe the decision, evaluate against sources you control, return yes or no with proof.
Step 2
Evaluate against authority
Checks run against registries and rules you authorise. Sensitive fields stay in systems you already operate wherever the design allows.
Step 3
Return yes or no with proof
The response is explicit, signed where required, and suitable for audit or partner handoff. AffixIO does not retain the request after the decision.
Where AffixIO sits in your stack
A thin stateless layer between citizen channels and core departmental systems. It answers eligibility questions; it does not replace case management, payments, or identity providers.
Your channelsGOV.UK services, contact centres, field applications, partner APIs, and automated agents.
AffixIOStateless verification via API and SDK. Binary outcomes with cryptographic proof.
Your core systemsDepartmental registries, identity, payments, HR, and case tools you already accredit.
Further reading: technical architecture, what AffixIO is, government data integration.
What you can implement
Clearance and vetting signals
Binary outcomes for role assignment workflows, with pseudonymised audit metadata.
Offline estate access
Signed proofs validated locally when networks are degraded.
Supplier assurance
Repeatable checks for contractor competencies and registration status.
Example response (illustrative)
{
"eligible": true,
"proof": "<signed verification artefact>",
"decision_id": "dec_…",
"evaluated_at": "2026-05-15T12:00:00Z"
}
OpenAPI documentation: api.affix-io.com. Integrate via REST, webhooks, or SDKs.
How teams deploy
Managed API
Connect through your API gateway with TLS, mutual authentication where required, and departmental logging.
Self-hosted
Run inside your accredited boundary when policy requires on-premise or private cloud.
Offline and edge
Validate signed proofs locally where connectivity is limited. See offline verification.
Agentic channels
Machine clients receive the same binary signals as citizen channels. See M2M verification.
Deployments align with MOD cloud and on-premise patterns, including private connectivity to registries you operate or sponsor.
Cryptography and data handling
Built for long-lived programmes that must plan beyond legacy signatures and minimise data held at the verification boundary.
Stateless by design
No long-term store of who asked or the attributes inside a request. Supports proportionate DPIA narratives.
ML-DSA ready
Artefacts can use Module-Lattice-Based Digital Signature Algorithm (ML-DSA), aligned with NIST post-quantum direction, with optional HSM-backed key ceremonies.
Zero-knowledge outcomes
Where policy allows, demonstrate that a rule evaluated to yes without exporting underlying registry content.
Patent pending: AffixIO verification pipeline protected under GB2510622.0 (pending).
UK regulatory alignment
- UK GDPR and Data Protection Act 2018
- Government Security Classifications (OFFICIAL patterns; higher via your deployment model)
- NCSC cloud security principles
- Service Standard compatible citizen journeys
- Pseudonymised audit metadata for review
See GDPR compliance and privacy policy.
Common questions
Does AffixIO store citizen personal data?
No. AffixIO is stateless verification infrastructure. It evaluates a request against sources you authorise and returns a decision with proof. It does not maintain a standing database of citizens or request payloads.
Can this run offline for field teams?
Yes. Signed proofs can be validated where connectivity is limited, with reconciliation when the device or site is back online. This pattern is used across offline payment and access programmes on affix-io.com.
How does ML-DSA fit in?
Long-lived verification artefacts can be bound with ML-DSA (Module-Lattice-Based Digital Signature Algorithm), supporting post-quantum planning. HSM-backed ceremonies are available where your security policy requires them.
Can verification work across classified boundaries?
AffixIO is designed as a thin decision layer. Higher classifications are addressed through your deployment topology, accreditor requirements, and what data never leaves your boundary.
Speak with our team
Share your channel mix, assurance constraints, and first use case. We will respond with a practical integration outline.
AffixIO is an independent technology provider. References to UK departments and agencies describe integration patterns for eligible programmes; they do not imply endorsement. Operational deployment is subject to your organisation's assurance, procurement, and data-sharing agreements.