AP2 payment authorization for autonomous agents.

AP2 payment
authorization.

The AP2 payment authorization sidecar for autonomous agents. Send users an approval link. Get back signed AP2 Mandates.

Agent Payments Protocol · MCP · HTTP API

AP2 payment authorization topology The merchant returns a signed checkout to the agent. The agent requests AP2 payment authorization from AP2.bot. AP2.bot sends the user an approval link, then returns the resulting signed AP2 Mandates to the agent. MERCHANT SIGNS THE CHECKOUT ›_ AGENT REQUESTS AUTHORIZATION AP2.BOT AP2 PAYMENT AUTHORIZATION SIDECAR USER REVIEWS AND APPROVES MERCHANT-SIGNED CHECKOUT REQUEST AUTHORIZATION APPROVAL LINK SIGNED AP2 MANDATES AP2 payment authorization topology The merchant returns a signed checkout to the agent. The agent requests AP2 payment authorization from AP2.bot. AP2.bot sends the user an approval link, then returns the resulting signed AP2 Mandates to the agent. MERCHANT SIGNS THE CHECKOUT MERCHANT-SIGNED CHECKOUT ›_ AGENT REQUESTS AUTHORIZATION REQUEST AP2 AUTHORIZATION SIGNED AP2 MANDATES AP2.BOT AP2 PAYMENT AUTHORIZATION SIDECAR APPROVAL LINK USER REVIEWS AND APPROVES
Works wherever your agent runs: terminal · chat · voice · scheduled jobs · backend services

Two MCP tool calls.

Delegate the AP2 payment authorization flow to AP2.bot instead of building it yourself.

MCP TOOL

request_authorization

MCP INVOCATION
request_authorization({
  mandate_contents:
    flightMandates,
  handoff: {
    method: "return_url"
  }
})
FlightDXB → LHR
PriceUSD 2,480
Passengers1
AP2.bot MANDATE DELEGATION
MCP TOOL

get_authorization

MCP INVOCATION
get_authorization({
  authorization_id:
    flightAuthorizationId
})
Checkout MandateSIGNED
Payment MandateSIGNED

MANDATE DELEGATION

Inside
AP2.bot.

One integration handles the approval handoff, wallet flow, and signed result.

Keep approval tied to the checkout.

Send the Checkout and Payment Mandate Content once. AP2.bot holds the exact merchant-signed checkout for the life of the authorization session, so the user reviews—and the wallet signs—the same purchase your agent requested. Your agent can move on while that human decision is pending.

Reach the user without owning a frontend.

Have your agent display the returned approval URL, or let AP2.bot send it by SMS or email. A terminal agent, voice assistant, scheduled job, or backend service gets a direct route to human approval—without building a checkout UI, a messaging workflow, or a tool call that waits for the user.

Skip the wallet plumbing.

AP2.bot builds the OpenID4VP presentation request and handles the Digital Credentials API integration. The user’s wallet presents the merchant, checkout, amount, and selected payment instrument, then collects authentication and approval. The wallet—not AP2.bot—signs both AP2 Mandates.

Get one predictable result.

AP2.bot checks the wallet response against the original checkout and session challenge, then normalizes the signed Checkout and Payment Mandates for retrieval. Your agent gets a consistent authorization state and result instead of carrying wallet-specific response handling in its own code.

AP2 payment authorization sidecar

Add AP2 payment authorization to your agent.

Send users an approval link. Get back signed AP2 Mandates.