Start with 100 free AffixIO proofs

New eligible Hub account holders can claim one allocation of 100 free SDK proofs. No card required. Use them to test SDK proofs, agent verification, agentic payment checks and transaction intent proof workflows.

See the free proof offer

Live tool · test mode

Agentic Pay: a real checkout, proven.

An AI buying agent asks to charge a Stripe test card. AffixIO authorises the agent (Know Your Agent), checks the card, then stamps a signed proof: simple_yesno plus audit_proof, ML-DSA-65, for every intent. No real charge, ever.

Real proofs, live API
Stripe test numbers only
KYA-gated agent
Signed ML-DSA-65

Run a test payment How the proof works

Checking live licence…

Live proof tunnel

The 3D tunnel behind this panel reacts to every payment: idle drift, payment surge, green approval pulse or red decline flash. Drag to orbit, scroll to zoom.

Settlement proof…
Licencechecking…
Server ledger…

Three.js · drag to orbit · scroll to zoom

Fullscreen demo stage

The working checkout. Every control below hits the live proof backend. There are no mocks in this box.

How the proof works

Test checkout console

Pick a Stripe test card, set an amount, and let the agent run: KYA authorisation → card checks → signed proof → receipt. Full PANs never leave your browser log redaction. Only the last 4 reach the server.

1 · Agent authorisation

Know Your Agent checks pay.charge on stripe://test/*.

Waiting…

2 · Card checks

Luhn, brand, expiry, CVC + Stripe test scenario.

Waiting…

3 · AffixIO proof

simple_yesno settlement proof + audit_proof, ML-DSA-65.

Waiting…

4 · Receipt

Licence heartbeat + ledger append (last4 only).

Waiting…

Session ledger

No intents yet this session.

Server ledger…

SDK wiring

import { AffixSDK } from "affixio";
// server-side (key never ships to the browser)
const sdk = new AffixSDK({ apiKey: process.env.AFFIX_API_KEY });
const kya = await trust.authorise({ credential, action: "pay.charge",
  resource: "stripe://test/" + intentId });
const proof = await proveCircuit("simple_yesno",
  { credential, context, requestAttestation: true });
// GET /v1/auth/check -> licence heartbeat

This page uses the vendored SDK path /var/www/vhosts/SDK via a same-origin PHP proxy. The browser never sees the API key.

Try the edges

still mints a signed no proof
exercises the decline branch
fails closed before any proof

Agentic payments search layer

Where AffixIO sits when agents start spending.

Agentic payments are splitting into rails, mandates, wallets, tokens and proof. AP2 can describe authorisation, MPP can move machine payments, x402 can charge at the HTTP request, Visa TAP and network tokens can make card rails safer, and ACP or UCP can shape commerce journeys. AffixIO sits before the payment action and proves whether the agent should be allowed to spend at all.

Discover

AI shopping agents and browser agents

Grok Bot style cloud agents, Muse AI style personal agents, OpenAI agents, Claude agents, Gemini agents, Perplexity Comet, LangGraph, CrewAI and MCP runners can all move from search to action. They need a verifiable checkout decision before the cart becomes money.

Authorise

AP2 mandates and consent proofs

Agent Payments Protocol, delegated credentials, spending caps, merchant scope, cart scope and human-not-present approval all need a proof envelope that can be checked after the agent has moved on.

Settle

MPP, x402 and payment rails

Machine Payments Protocol, HTTP 402 payments, stablecoin settlement, Stripe Link, Shared Payment Tokens, Visa TAP, Mastercard Agent Pay and agentic network tokens solve different parts of money movement. AffixIO verifies the permission layer that sits above them.

Audit

Signed proof for every yes or no

Every approved, declined, retried or expired payment intent should create evidence: who the agent was, what it requested, what policy allowed, which amount applied, and whether the result can be replayed, disputed or reconciled.

High-intent terms, natural language

Agentic payments are not one keyword. They are the new checkout surface.

People are searching for agentic payments, AI payments, AI checkout, AI shopping agents, autonomous purchasing, MCP payments, x402 payments, AP2 mandates, machine-to-machine payments and agent commerce because every team is asking the same commercial question: can an AI agent buy safely without exposing the business?

Commercial intent

agentic payments, AI payment rails, AI checkout, agentic commerce, autonomous purchasing, machine initiated payments, agent payment verification, AI agent checkout security

Protocol intent

Google AP2, Stripe MPP, x402, ACP, UCP, MCP tool payments, Visa Trusted Agent Protocol, Mastercard Agent Pay, Shared Payment Tokens

Risk intent

Know Your Agent, delegated consent, payment mandates, spending caps, replay protection, idempotency, verifiable audit trail, agent identity, policy proof

Named naturally, claimed carefully

Muse AI, Grok Bot and the wider agent wave make payment proof urgent.

Muse AI style personal agents can plan, browse, fill forms and reach checkout. Grok Bot style cloud agents, coding agents, browser agents and MCP tool runners can call APIs, compare offers and trigger paid actions. AffixIO does not claim direct integration with Muse AI, Grok Bot, OpenAI, Anthropic, Google, Perplexity, Visa, Mastercard, Stripe or any named provider unless a specific integration page says so. These names describe the market category that now needs verifiable authority before spend.

Personal agent

Before the agent buys

Check merchant scope, basket value, category limits, card token scope and user consent freshness before a Muse AI style assistant reaches payment.

Cloud agent

Before the tool spends

Bind Grok Bot style tool calls to action, resource, amount and time so an autonomous workflow cannot silently convert a search task into a charge.

Protocol bridge

Before the rail settles

Add a proof decision above AP2, MPP, x402, ACP, UCP, Visa TAP, Mastercard Agent Pay or any processor metadata path.

Proof operating model

The agentic payment checklist buyers, merchants and platforms will ask for.

AffixIO turns agent checkout into an inspectable control system. The agent can still be fast, but the business gets a result that compliance, support, finance and security can understand after the transaction.

Agent identity: identify the agent, app, session, owner and capability before a paid action runs.
Delegated consent: bind user permission to merchant, amount, resource, category and expiry.
Policy decision: prove whether the action is allowed, denied, expired, out of scope or over budget.
Payment context: record token scope, rail, idempotency key, retry window and processor reference.
Audit proof: give every yes and no a signed receipt that can be verified without exposing full payment data.

AEO answers for buyers

Straight answers for agentic payment searches.

These are the questions search engines, LLMs and buyers are already compressing into one answer box.

What is agentic payment verification?

Agentic payment verification checks whether an AI agent is authorised to spend before it reaches the payment rail. It proves agent identity, delegated consent, spend limits, merchant scope and the exact intent being charged.

Does AffixIO replace AP2, MPP or x402?

No. AP2, MPP and x402 address mandates, machine payments and web-native settlement. AffixIO complements them by producing a signed decision layer before checkout, API charging or MCP tool payment.

Can AI shopping agents use AffixIO?

Yes. Any product that receives requests from AI shopping agents, browser agents, cloud agents or MCP runners can use AffixIO to verify permission, create audit proof and reduce payment abuse.

Why does this help sales?

Agent-ready checkout needs trust. A merchant that can show proof-ready agentic payments, safe AI checkout and verifiable mandates is easier for platforms, partners and security teams to approve.

Agentic Pay FAQ

Straight answers before you wire this into your agent.

Is this a real payment?

No. Test mode only. The page accepts generic Stripe test numbers and never contacts a payment network. The real artefact is the AffixIO proof.

Where does AffixIO fit in agentic payments?

AffixIO sits before the payment rail. It verifies agent identity, delegated consent, spending policy and exact intent, then creates a signed proof that the payment decision can be checked later.

Can this work with AP2, MPP, x402, Visa TAP or Mastercard Agent Pay?

Yes. Those standards and rail programmes handle different layers of agentic commerce. AffixIO can provide the proof and policy decision that tells a product whether an agent should be allowed to use them.

Does AffixIO integrate directly with Grok Bot or Muse AI?

AffixIO does not claim direct integration with Grok Bot, Muse AI or any named third-party agent unless a specific integration page says so. They are examples of the broader agent category where consent, policy and audit matter.

Do you store my card?

No. Only the last 4 digits, brand, amount and proof id reach the ledger. Full PANs stay in your browser and are never logged.

Can a declined card still get a proof?

Yes. The agent still receives a signed no decision, so your reconciliation trail stays complete. The verdict card turns red and the digest still verifies.

How do I move this beyond test mode?

Point the same proof path at your own rails. Issue a key from the AffixIO hub, attach the proof envelope as the idempotency key or metadata on your payment, then verify on the recipient side.

Contact AffixIO AffixIO for agents affixio on npm

AI agent verification resources

The proof-before-action pathway

Start with the explanation of what it means for an AI agent to be verified before a transaction, then follow the implementation path for consent, spending limits, checkout and signed evidence.

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.

Read the PAP fit

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.

Read the PACT fit

Start with 100 free AffixIO proofs

Agentic Pay: a real checkout, proven.

Live proof tunnel

Give every AI agent its own proof area before it acts.

Fullscreen demo stage

Test checkout console

1 · Agent authorisation

2 · Card checks

3 · AffixIO proof

4 · Receipt

Where AffixIO sits when agents start spending.

AI shopping agents and browser agents

AP2 mandates and consent proofs

MPP, x402 and payment rails

Signed proof for every yes or no

Agentic payments are not one keyword. They are the new checkout surface.

Commercial intent

Protocol intent

Risk intent

Muse AI, Grok Bot and the wider agent wave make payment proof urgent.

Before the agent buys

Before the tool spends

Before the rail settles

The agentic payment checklist buyers, merchants and platforms will ask for.

Straight answers for agentic payment searches.

What is agentic payment verification?

Does AffixIO replace AP2, MPP or x402?

Can AI shopping agents use AffixIO?

Why does this help sales?

Agentic Pay FAQ

Is this a real payment?

Where does AffixIO fit in agentic payments?

Can this work with AP2, MPP, x402, Visa TAP or Mastercard Agent Pay?

Does AffixIO integrate directly with Grok Bot or Muse AI?

Do you store my card?

Can a declined card still get a proof?

How do I move this beyond test mode?

The proof-before-action pathway

PAP-style sessions still need proof before action.

Scopes still need proof before execution.

Agents get 150 free proofs. Humans get 100. No card required.