Technical reference

Agentic commerce protocols: ACP, UCP, AP2, MCP, A2A, x402 and more

AI agents start purchases through different protocols: commerce checkout, card networks, Pix, machine-to-machine payments, mandates and agent-to-agent communication. This reference summarizes, at a conceptual level, the role of each protocol and points to the matching illustrative scenario in the transaction flow explorer.

The ten protocols

  • Agentic Commerce Protocol (ACP)

    Commerce · Card

    Standardized agent checkout with delegated payment using a token bounded to the merchant and the amount.

    View scenario in the flow explorer (U1)

  • Universal Commerce Protocol (UCP)

    Commerce · Retail and services

    Catalog discovery, quotation and standardized agentic order closing (Google and retail partners).

    View scenario in the flow explorer (U6)

  • Visa Trusted Agent Protocol (TAP)

    Card network · Visa

    Recognition of autonomous agents on the Visa network. The issuer can ask AuthPros for a trust recommendation before deciding authorization.

    View scenario in the flow explorer (U2)

  • Mastercard Agent Pay

    Card network · Mastercard

    Agent-initiated payments on the Mastercard network with evidence of the cardholder's intent; the issuer remains responsible for authorization.

    View scenario in the flow explorer (U2)

  • Pix with dynamic QR and Open Finance

    Central Bank of Brazil · SPI

    Agent-initiated Pix with DICT key resolution, payee checks and night-time limits before the payment order is sent.

    View scenario in the flow explorer (U3)

  • Stablecoin via x402 (HTTP 402)

    Machine to machine · Blockchain

    Machine-to-machine micropayments over the HTTP 402 status code, with on-chain settlement and proof of payment.

    View scenario in the flow explorer (U4)

  • Agent Payments Protocol (AP2)

    Mandates · Card, Pix or crypto

    Chained user intent, cart and payment mandates, checked against the delegated authority.

    View scenario in the flow explorer (U5)

  • Model Context Protocol (MCP)

    Tools and agents

    Discovering a payment tool on an MCP server never grants implicit authority to pay; payment requires an explicit mandate and consent.

    View scenario in the flow explorer (U7)

  • Agent-to-Agent (A2A)

    Between agents · B2B

    Direct negotiation between buyer and seller agents; a delegated agent's authority never exceeds that of its delegator.

    View scenario in the flow explorer (U8)

  • Direct EMVCo card (Network Token + 3DS, MIT)

    Acquiring and issuing

    Illustrative Merchant Initiated Transaction with a Network Token and EMV 3DS: AuthPros gives a trust recommendation and the issuer authorizes.

    View scenario in the flow explorer (U9)

Trust recommendation and authorization are different decisions

Across every protocol, AuthPros evaluates agent identity, delegated authority, intent and context and returns a trust recommendation with evidence. The responsible institution, such as the issuer, acquirer or payment institution, decides authorization and executes the payment on its own rail. Discovering a tool, receiving a token or completing a checkout is not financial authorization.

About the scenarios

Explorer scenarios are illustrative and educational: they show the conceptual message sequence between participants and do not imply a production integration or certification with networks or providers. Visa TAP and Mastercard Agent Pay share the card network scenario.

Does an agentic payment protocol authorize the purchase on its own?

No. The protocol carries the proposal and credentials; delegated authority must be verified and the responsible institution still decides final authorization.

Continue exploring

POENES