Skip to content
Jason LovellFrontier AI research, solution design and engineering
Contact
All work

What does a merchant need before an agent can buy?

Alpha reference gateway that lets shops accept consented orders from AI agents.

Agent-Ready Checkout GatewayUse-case designPython

Code on GitHubDiscuss this build

Design choice

Consent goes into an append-only, hash-chained ledger before a policy hook can allow, deny or flag the order for review.

In practice

Settle what an agent may buy on its own, and what needs a person, while designing the checkout, not after an order ships.

What I built

  • FastAPI gateway for intent, confirmation, authorisation and fulfilment
  • Append-only consent ledger with hash chaining
  • Policy hook for allow, deny, and review decisions
  • Receipt pipeline with detached provenance manifests

System sketch, not a live run.

Policy decision
  1. Intent
  2. Confirmationconsent ledger, hash‑chained
  3. Authorisationpolicy hook
  4. Fulfilment
  5. Receiptprovenance manifest
Allow: Order fulfilled. It leaves with a receipt and a detached provenance manifest.

Where it stops

An alpha reference implementation (v0.1.0): a pattern demo, not a drop-in payment or PCI replacement. Payments go through a Stripe test-mode adapter, which does not simulate 3DS. The inventory and pricing MCP servers are mocks without full authentication, and receipts carry detached provenance manifests but no embedded C2PA signature. The default policy is a stub that allows everything and sends orders over $1,000 to review. A review decision is reported with its reasons in the authorisation response; the gateway does not pause the payment for it.