01
Describe the decision
Who or what is asking, what they want to do, limits, and which policy version applies.
Stateless verification infrastructure
Yes or no. With proof. Nothing stored at the verifier.
AffixIO is the layer you plug in when a product needs a clear decision: allow or deny, with cryptographic proof your teams and partners can audit. Payments, AI agents, and government programmes use the same API and SDK.
Request in
Allow or Deny
Signed proof out
Stateless No hidden user profile cache at the verifier.
Offline or online Same core at the lane or in the cloud.
ML-DSA ready Room for stronger cryptography as standards land.
Three steps. Then AffixIO forgets the request.
The same flow for a live API call or an offline packet.
02
AffixIO checks the facts
Your rules and authorised sources. Sensitive data stays in systems you already control where possible.
03
Yes or no with proof
An explicit answer you can file, replay, or hand to partners. AffixIO does not keep the request afterward.
One verification core. Different industries.
Integrate once; use the same stateless pattern across channels.
Payments
Cards, wallets, and terminals that need yes or no before money moves, including when the network drops.
Payment verification →AI agents
Checkout and authorization where software acts for a user. Identity, consent, and policy before payment.
AI verification hub →UK government
Eligibility after GOV.UK One Login: benefits, tax, right to work, licensing, with no citizen replica at AffixIO.
Government programmes →Access and compliance
Gates, accounts, and controls your risk team can trace. Evidence, not a silent black box.
Access control →A thin layer between your channels and your core systems
AffixIO does not replace payments, identity, case management, or registries. It answers one question in the middle: allowed or denied, with proof, then forgets the request.
AffixIO does
- Evaluate policy per request
- Return yes/no + signed proof
- Run offline, online, or both
- Stay stateless (no PII vault)
AffixIO does not
- Store citizen or customer profiles
- Replace your core systems
- Hold sessions between calls
- Become a new data silo
Channels (examples)
Core systems (examples)
Technical architecture · What AffixIO is · Government integration
Stack position
Your channels
Apps, terminals, agents, and services that initiate verification.
AffixIO
Thin stateless layer. API/SDK in and out. Queries your core, returns proof.
Your core systems
Processors, identity, registries, HR, and case tools you accredit.
- Request in
- Identifier, action, limits, circuit / policy id
- Response out
- Allow or deny, proof bundle, audit metadata
Built for buyers who want stateless
Short procurement reviews. Audits that read what you keep. Engineering that ships once.
Integrate once, run for years
No large user database for AffixIO to migrate or breach. Your team ships verification and moves on.
Test like any API
Mock in staging, pin versions, replay calls. Every test run starts clean with no leftover session.
Audit-ready answers
Yes and no arrive with proof you file on your systems, in formats reviewers already understand.
Plug it in with API or SDK
Both talk to the same stateless core. No phone-home and no user record cache at AffixIO.
SDK for apps and devices
The software kit helps your engineers wire flows, carry policy references, and handle proof bundles in code. It does not phone home and it does not cache user records.
SDKStateless core
AffixIO checks the request against your rules and trusted signals, returns yes or no with proof, and then drops the request. Your risk and audit colleagues get material they can read and follow.
Core serviceAPI
Stable URLs and versions so operations teams know what changed and when. Every call stands on its own, which is what stateless means in practise.
APIOffline, online, or both
Stateless by design: no session to lose between calls.
When the line drops
Devices can carry signed proofs forward and reconcile later when the connection comes back. Your privacy rules stay intact because nothing about the customer is held by AffixIO between calls.
When everything is up
Central teams push tight policy updates and get fast responses. Downstream systems stay in step because each verification call carries everything it needs to make the answer make sense.
Same building block. Payments, gates, eligibility checks, and automated actors call the same stateless verification.
Where teams start
Each link opens a deeper page that uses the same stateless foundation.
Payments
Payment verification
Works when networks fail and catches up cleanly when they come back.
Payment verification overviewprogrammes
Eligibility verification
One verified decision for benefits, pricing, and similar programmes.
Eligibility verification APIAccess
Access control
Gates for buildings and accounts with evidence security teams can cite.
Access control examplesAgents
Agent permissions
Limits for software actors, checked while transactions run.
Agent permissionsRisk
Compliance verification
Controls written as outcomes that internal review can inspect.
Compliance frameworksCommon questions
What is stateless verification?
Each request is evaluated and answered with a signed yes or no and proof. AffixIO does not keep a long-term store of who asked or the personal data inside the request.
How do merchants verify AI agents at checkout?
Verify the consent receipt signature, allowed merchant and amount, and that the nonce has not been reused before authorization. Merchant verification guide
How does AffixIO fit UK government digital ID?
GOV.UK One Login handles sign-in; AffixIO answers eligibility after authentication with stateless yes/no outcomes. UK government programmes · Digital ID rollout guide
Does it work offline?
Yes. The same design runs at a store lane with no signal or in a data centre. Offline payment verification
Contact
Tell us your setup
Write to us about your setting. Tell us whether you need offline support, full online mode, or both, and which job comes first. We answer with a practical wiring diagram for your team, with the stateless verification core in the middle.