Engage a Mastercard-certified processor or your existing acquirer to enable Agent Pay on your merchant account; Agent Pay reached broad processor availability in 2026 following a phased rollout starting with Microsoft, IBM, and Braintree in April 2025
Understand the Agentic Token structure: it is an extension of the Mastercard Digital Enablement Service (MDES) token that binds a tokenized card credential to a specific agent identity, merchant scope, and consent policy with configurable spend caps, merchant restrictions, and expiration windows
On the authorization message, populate program_id field with the value for an Agent Pay transaction (Mastercard added dedicated values to the digital_commerce_data object effective April 17, 2026) so that issuers and processors can identify and correctly route the agent-initiated transaction
Implement real-time token revocation handling: if a consumer revokes an agent's authorization through their issuer app, the Agentic Token is invalidated at the network level and the next auth attempt will fail — surface this failure to the agent as a specific error code distinct from a generic decline
For cross-protocol use, understand that Mastercard Agent Pay participates in the Universal Commerce Protocol (UCP) coalition alongside Visa, Google, Stripe, and others; Agentic Tokens slot into the AP2 Payment Mandate flow when that protocol layer is used
Test token lifecycle scenarios in the Mastercard sandbox: successful authorization, revocation mid-session, spend cap exhaustion, and merchant restriction violation
Known gotchas
Agentic Tokens assume a pre-authorized agent, not a present human; standard MDES token dispute rules may not map cleanly to agent-initiated chargebacks — review the updated Agent Pay dispute rules with your acquirer before launch
The program_id field addition (effective April 17, 2026) requires a message format update on your authorization integration; processors that have not updated their message schemas will not correctly label agent transactions, losing the network-level audit trail
Consumer revocation is real-time at the Mastercard network layer but your processor may have a propagation delay before the revocation reaches your authorization response; do not cache a previously valid Agentic Token as permanently valid
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp