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.
Stateless eligibility infrastructure for departments, agencies, and regulated bodies.
Short answer: After sign-in (for example GOV.UK One Login), programmes still need allow or deny answers with proof - not another citizen data silo. AffixIO returns signed yes/no outcomes via API and SDK and does not retain request payloads.
Stateless verification · No standing PII store · ML-DSA ready
AffixIO provides stateless eligibility infrastructure for departments, agencies, and arm's-length bodies. Your services receive a clear yes or no with cryptographic proof, without building another citizen data store at the verification layer.
Personnel, estate access, and supplier assurance.
View sector pageArmed forces, veterans, and the defence supply chain.
View sector pageTax status, filing eligibility, and intermediary authorisation.
View sector pageBenefits, pensions, and channel authentication.
View sector pageLicence validity and enforcement without full record disclosure.
View sector pageHousehold coverage and respectful field verification.
View sector pageTreatment entitlement and workforce credentials.
View sector pageImmigration status, right to work, and rent checks.
View sector pageCouncil services, licensing, and discretionary support.
View sector pageEligibility after GOV.UK One Login and departmental ID.
View sector pageIn-depth guide to One Login, eVisa, and the trust framework.
View sector pageThe same three-step model used across AffixIO applies here: describe the decision, evaluate against sources you control, return yes or no with proof.
Step 1
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.
Step 2
Checks run against registries and rules you authorise. Sensitive fields stay in systems you already operate wherever the design allows.
Step 3
The response is explicit, signed where required, and suitable for audit or partner handoff. AffixIO does not retain the request after the decision.
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.
Further reading: technical architecture, what AffixIO is, government data integration.
One verified decision for benefits, access, pricing, and similar rules. Documented on the eligibility API page.
Confirm facts via API without storing PII at AffixIO. See identity product and government database integration.
Gates, accounts, and field checkpoints with evidence security teams can cite. Access control use cases.
Machine clients receive the same signals as human channels. Machine-to-machine verification.
Built for long-lived programmes that must plan beyond legacy signatures and minimise data held at the verification boundary.
No long-term store of who asked or the attributes inside a request. Supports proportionate DPIA narratives.
Artefacts can use Module-Lattice-Based Digital Signature Algorithm (ML-DSA), aligned with NIST post-quantum direction, with optional HSM-backed key ceremonies.
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).
See GDPR compliance and privacy policy.
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.