How is user consent captured with agent transactions?
The customer system, wallet or merchant captures consent. AffixIO verifies whether the proposed agent action fits that stored consent.
Consent and delegated authority
Verify consent without copying the consent record.
Agentic commerce needs consent that is bounded, current and auditable. AffixIO helps prove that an attempted action fits the consent held by the customer, wallet or merchant.
What this page answers
Consent for an agent transaction should define the actor, scope, expiry, transaction type and limits. AffixIO can verify that fit and return signed evidence while the consent record remains in the customer's system.
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
- 01Capture consentRecord the user's bounded approval in the customer system.
- 02Reference consentUse a consent_ref rather than exposing the raw consent record.
- 03Verify fitCheck action, amount, merchant, expiry and policy version.
- 04Return evidenceStore signed result and proof_id for audit or dispute review.
Direct answers
Concise answers for search, procurement, engineering and agent retrieval.
What can consent include?
Consent can include amount ceiling, merchant, merchant category, product class, geography, wallet session, expiry, account and permitted action type.
Can consent be revoked?
Yes. Revocation remains in the customer system or wallet. A later verification can deny actions that no longer fit the active consent state.