Social welfare and benefits
Universal credit, housing benefit, disability entitlements, and emergency relief. Prove income band without exporting full tax files.
yesno · kycPublic sector worldwide
Government eligibility verification
AffixIO gives central, regional, and local government a stateless path to yes or no eligibility decisions. Issue ML-DSA-65 signed proofs from Noir zero-knowledge circuits, verify through REST API or Node.js SDK, and retain zero PII at the boundary. Auditors get Merkle-anchored evidence suitable for FOI, dispute, and programme review.
ML-DSA-65NOIR ZKMERKLE AUDITZERO PIION-PREM SDKFOI READY
At a glance
- Product
- Stateless yes or no eligibility verification with signed cryptographic proof
- Scope
- Central, regional, local, and cross-border government programmes
- Signatures
- ML-DSA-65 post-quantum (NIST FIPS 204)
- Proofs
- Noir zero-knowledge circuits via open-source Barretenberg stack
- Data retention
- None at the verifier by default
- Integration
- REST API, Node.js SDK, secure QR, MCP connector
- Company
- AffixIO, Wales, UK. GB patent application pending.
Government eligibility verification is the process of deciding whether a citizen, resident, or organisation qualifies for a public programme, permit, or service, then recording that decision in a form auditors can trust. AffixIO returns a signed allow or deny outcome instead of copying underlying records into every vendor system.
The challenge
The problem public bodies face
Programme delivery still depends on eligibility checks that copy citizen data into vendor silos, expand GDPR scope, and weaken FOI defensibility when caseworkers cannot prove what was decided at the boundary.
Data duplication
Each integrator builds a local copy of records to answer the same policy question. Breach surface grows with every new supplier.
Audit fragility
Disputes and transparency requests require reconstructing decisions from logs that may not bind to the original policy inputs.
Cross-agency friction
Central departments, devolved administrations, municipalities, and treaty partners need a common proof format without a shared citizen database.
Post-quantum exposure
Long-lived eligibility artefacts signed with classical cryptography may not survive a harvest-now-decrypt-later threat model.
Use cases
Programme domains across government
Any policy that resolves to allow or deny is a fit. The same proof pipeline applies whether the authority is national, regional, municipal, or multilateral.
Healthcare and public health
Treatment eligibility, prescription schemes, and vaccination status gates. Binary outcome at clinic boundary.
health_ageEducation and student finance
Scholarships, fee waivers, and research grants. Verify entitlement without standing student profiles at every vendor.
grant proofsImmigration and border permits
Visa classes, work permits, and trusted traveller programmes. Present signed eligibility at checkpoint.
permit · QRLicensing and registers
Professional licences, vehicle permits, and business registrations. Registers stay authoritative.
register lookupHousing and local programmes
Council tax support, social housing queues, and homelessness prevention.
local authorityTax credits and revenue
Child benefit, R&D credits, and customs reliefs. Revenue bodies issue predicates.
revenue ZKDefence and facility access
Base entry, contractor clearance, and supply-chain qualification.
access · offlineElections and civic eligibility
Voter roll checks and postal vote qualification.
elector · event-boundPublic procurement
Supplier qualification and framework admission.
supplier gateDigital identity programmes
Wallet issuers and eID schemes. Verification layer above wallets.
eIDASInternational aid and treaties
Disbursement eligibility and cross-border programme admission.
treaty ZKProof pipeline
How verification works
- 01
Issue
Policy authority defines a Noir circuit for the rule set. Witness inputs come from systems that already own the records.
- 02
Bind
Proof is bound to event context: programme ID, expiry, geography, and anti-replay nonce. ML-DSA-65 signature applied at issue.
- 03
Present
User, agent, or device presents the credential via API call or secure QR at the service boundary.
- 04
Verify
Verifier receives allow or deny plus Merkle reference. No personal data retained at the verifier by default.
Policy alignment
Jurisdiction and policy alignment
AffixIO is built in Wales and written for buyers in any government tier. Architectural alignment is not a certification. Your data protection officer remains responsible for deployment-specific compliance.
United Kingdom
Designed for FOI defensibility, UK GDPR data minimisation, and GDS-style API-first delivery.
- FOI and transparency audit trails
- UK GDPR / Data Protection Act 2018
- WP-038 UK government walkthrough
European Union
Selective disclosure patterns for member-state programmes.
- GDPR Article 25 data protection by design
- eIDAS 2.0 selective disclosure
- EU AI Act audit evidence
United States
State programme delivery and federal post-quantum migration planning.
- WP-041 federal PQC executive order
- Agency API integration via REST and SDK
Commonwealth and multilateral
Treaty bodies, development banks, and federal states.
- Cross-sovereign disbursement checks
- Merkle audit for donor reporting
Buyer guide
Approach comparison
| Dimension | AffixIO | Central eligibility database | Document upload vendor |
|---|---|---|---|
| Outcome | Signed allow or deny with Merkle ref | Query returns record snapshot | Manual review queue |
| PII at verifier | Zero by default | Full or partial record copy | Document images stored |
| Audit | Cryptographic proof + Merkle tree | Database access logs | Vendor retention policy |
| Post-quantum | ML-DSA-65 (FIPS 204) | Depends on incumbent stack | Depends on incumbent stack |
Full comparison: vs KYC database · stateless vs traditional
Procurement
Evaluation and procurement path
Sandbox validation
Reproduce WP-038 in the live sandbox.
Architecture review
Map programme policy to circuit inputs. Review trust centre and security.
Procurement pack
Download the procurement pack for DPIA template and diagrams.
Pilot scope
Run a bounded pilot via the evaluation path.
Stack
Technical foundation
ML-DSA-65Post-quantum signatures
NoirZero-knowledge circuits
MerkleAudit anchoring
RESTOpenAPI 1.4.2
SDK@affix-io/sdk
QROffline spent-proof
Proof generation can run on infrastructure you control. See technical architecture and circuit catalogue.
FAQ
Frequently asked questions
What government programmes can AffixIO support?
Any policy that resolves to yes or no: welfare, healthcare, education grants, immigration permits, licensing, housing, tax credits, elections, procurement, digital identity wallets, and cross-border aid.
How does AffixIO support FOI and audit requests?
Each decision produces a signed outcome with a Merkle-anchored reference. Auditors can verify that a specific allow or deny was issued without re-running the check.
Can proofs run on government-owned infrastructure?
Yes. The Node.js SDK generates and verifies proofs on infrastructure you control.
What post-quantum signature scheme is used?
ML-DSA-65 aligned with NIST FIPS 204.
How is personal data handled at the verifier?
By default the verifier receives a binary outcome and proof metadata, not a standing profile.
How does this compare to a central citizen database?
A shared database copies records for every query. AffixIO evaluates policy per request and returns a signed outcome.
Get started
Validate government eligibility verification on the live sandbox, then scope a pilot with the procurement pack and engineering team.