AIPayHQ – AIPayHQ
AIPayHQ.com — Intent Bound Authorization for AI Agent Payments
AI PAY HQ · Intent Bound Authorization · Agentic Commerce

AI
PAY
HQ

The Authorization Layer Beneath Every Agentic Payment Protocol

Mastercard Agent Pay · x402 · MCP · Google AP2 · Stripe MPP
provide the payment rails.

IBA Intent Bound Authorization declares what your agent
is authorized to pay for — before it touches any of them.

“How do they know the consumer authorized the agent to make the purchase?
How can they know if the agent has carried out the consumer’s instructions correctly?”

— Pablo Fourez, Chief Digital Officer · Mastercard · March 2026
▼   THREE LIVE DEMOS BELOW   ▼
LAYER 0 · PRE-EXECUTION
IBA CERT
Signs before agent acts
LAYER 1 · TOOL ACCESS
MCP
Agent gets payment tool
LAYER 2 · MECHANICS
x402
HTTP payment executes
LAYER 3 · RAILS
AGENT PAY
Card/stablecoin settles
LIVE INTERACTIVE DEMONSTRATIONS
Three Demos. One Architecture.
Every demo shows what happens without IBA — and what happens with it.
THE AUTHORIZATION GAP · EVERY MAJOR PROTOCOL · 2026
Protocol Solves Leaves Open
MCP (Anthropic) Tool access — gives agents payment tools Which tools the agent is authorized to invoke
x402 (Coinbase) HTTP-native stablecoin payment mechanics What the agent may pay for, to whom, how much
AP2 (Google) Agent payment sessions · 60+ partners Pre-execution authorization boundary
MPP (Stripe/Tempo) Machine-native payment rails Who declared the agent’s spending authority
Agent Pay (Mastercard) Card-based agentic payment infrastructure Cryptographic pre-execution authorization
IBA (IntentBound.com) Signed cert before any protocol is invoked Closes all of the above — Patent GB2603013.0
x402 gives your agent a wallet.
IBA decides what it is authorized to spend it on.

The certificate is declared before the agent connects.
Before MCP. Before x402. Before the first payment fires.
3
Live Demos
1.4ms
Gate Latency Target
14
Grok Validations
10
NCCoE Filings
150+
PCT Countries