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
How user consent is captured for AI agent transactions
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.
From a user's approval to a checkable mandate
The application should show the proposed authority before asking for approval. Capture what the user approved, bind it to the authenticated user and agent, and retain a versioned record in the system responsible for consent. A conversation transcript alone may not establish the final scope.
Example approval
Buy office supplies once from Merchant A, spending no more than GBP 100 including delivery and tax, before 18:00 on the approved date. Do not start a subscription or substitute another merchant. This is an illustrative mandate, not an AffixIO API payload or a legal consent template.
- Who can act?
- Identify the approving account and the agent or session receiving authority.
- What is permitted?
- Record the action, merchant, purchase category, total limit and currency. State whether recurring purchases are excluded.
- How long does it last?
- Record the approval time, expiry with its time zone, and any single-use limit.
- How can it be withdrawn?
- Provide a revocation route and check the current status before the controlled action.
- What was evaluated?
- Associate the attempted transaction, mandate version, policy version and decision evidence without copying unnecessary personal records.
When must the agent ask again?
A change outside the approved scope needs a new approval. Examples include a higher total, another merchant, an expired mandate or a recurring charge where only a one-off purchase was allowed. A mandate reference is a lookup key, not proof that permission remains active.
If consent cannot be checked, keep the action pending or deny it according to your policy. Do not infer approval from a timeout. The application must enforce the result; recording a decision after the purchase cannot prevent an unauthorised purchase.
Delegated purchase authority is distinct from payment-provider authentication and from any separate privacy consent requirements. Your implementation must handle each applicable requirement. Follow the verification example, then the checkout enforcement sequence and issuer consent context.
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
Answers about approval scope, record ownership and revocation.
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.
BoundProof Agent
Give every AI agent its own proof area before it acts.
Provision a persistent BoundProof Agent, check its proof allowance and give a reviewer a scoped AffixIO Hub code. Trial and paid access follow the current billing status of that agent area.
- bpa_ agent key first. SDK key access depends on an active trial or subscription licence.
- Authorised payment. An authorised agent can use the documented API payment flow. Human payers use hosted Stripe Checkout. Payment-provider authentication may still be required.
- Scoped Hub view. The BP code opens only that agent's own area, usage and proof status.
Starter paid access
From £19/month
Provision the agent, check its licence and allowance, then request an SDK key through the documented flow.
Personal Agent Protocol context
PAP-style sessions still need proof before action.
When a personal agent reaches a website, MCP tool, OpenAPI route or checkout flow, AffixIO can check the exact action and return yes, no or review evidence before the business lets it run.
PACT consent context
Scopes still need proof before execution.
PACT can identify the personal agent and carry user-granted scopes. AffixIO can check the exact action and return yes, no or review evidence before the brand lets it run.