Merchant checkout
Let AI shopping agents reach checkout without losing control
AffixIO helps ecommerce merchants verify AI agent checkout intent, spending scope and merchant rules before delegated purchases are accepted.
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.
Provision the agent, check its licence and allowance, then request an SDK key through the documented flow.
Before accepting an agent basket
Ask whether this agent has authority for this buyer, this merchant, this value and this moment.
For stores preparing for agentic commerce
AI shopping agents are moving from search and recommendation into action. That means checkout needs a new gate. The question is no longer only whether a card works. The question is whether the agent was allowed to make this request at all.
AffixIO gives a merchant or ecommerce app a simple verification result before the store creates irreversible state. It can be used by custom apps, commerce middleware, agencies and platforms that need agentic checkout controls without rebuilding payments.
Questions buyers ask
Where does this sit in a store?
It sits before order creation, payment capture or fulfilment. Your backend asks whether the agent action is allowed.
Does it need a new checkout?
No. It can sit beside existing checkout and app middleware as a verification step.
Why would a merchant care?
The merchant gets proof of permission, spending scope and policy match before accepting an agent-driven order.