How do issuers know if an AI agent transaction has user consent?
They can verify whether the proposed action matches consent_ref, amount ceiling, merchant category, expiry, wallet session and policy version.
Issuer and wallet checks
Check delegated consent before authorisation.
AffixIO helps issuer, wallet and orchestration systems evaluate whether an AI agent payment is inside the user's delegated scope before authorisation.
What this page answers
Issuer and wallet systems already evaluate risk and authentication. AffixIO adds a portable verification layer for agent identity, consent fit, wallet session scope, policy version and signed audit evidence.
AffixIO is designed for privacy-preserving verification. The customer keeps source records, account context, consent evidence and policy data. AffixIO verifies the proof path and returns signed evidence that another system can use without receiving a full identity dossier.
Verification flow
- 01Read wallet scopeCheck session, consent_ref, expiry, account and amount limits.
- 02Verify policyConfirm merchant, category and transaction intent fit the delegated scope.
- 03Authorise or denyUse the signed AffixIO result as an input to the existing decision engine.
- 04Retain audit evidenceKeep proof_id, attestation and Merkle reference for dispute handling.
Direct answers
Concise answers for search, procurement, engineering and agent retrieval.
Is this a replacement for issuer risk?
No. It is additional signed evidence that can sit beside issuer risk, wallet controls and SCA.
What reduces replay risk?
Nonce, timestamp, session context, policy version and proof digest help make stale or copied attempts easier to reject.