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.
What happens after GOV.UK One Login - how is eligibility verified?
ML-DSA ready eligibility signals for relying services.
Short answer: Sign-in proves who someone is; AffixIO proves whether they are allowed for this service, scope, and channel - with signed proof for relying parties.
Stateless verification · No standing PII store · ML-DSA ready
Programme context
UK digital identity programmes need more than authentication. Relying services must know that a user still meets policy at the moment of transaction: age, status, entitlement, or role.
What teams are solving
Attribute bundles are often over-shared. Wallet and VC pilots risk new silos unless decisions remain minimal and auditable.
AffixIO approach: AffixIO sits after identity proofing. Subject identifiers enter; service-specific yes or no leaves, optionally signed with ML-DSA for long-lived programmes.
Where verification applies
- GOV.UK One Login
Consume authenticated subjects; return service-specific decisions.
- Verifiable credentials
Interoperate with VC ecosystems without mandating one wallet vendor.
- Agentic government
Automated services receive the same binary signals as citizen channels.
- Cross-department reuse
One verification event, scoped proofs for multiple relying parties.
- Post-quantum planning
ML-DSA migration path for government signing keys.
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
Post-authentication eligibility
Decisions after One Login or departmental ID.
M2M parity
Agents and citizens use the same truth layer.
Scoped proofs
Limit what each relying party learns.
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.
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.
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.