Implement Mastercard Agent Pay to issue Agentic Tokens for agent-initiated purchases and signal them correctly in authorization messages

Steps

1. 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
2. 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
3. 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
4. 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
5. 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
6. Test token lifecycle scenarios in the Mastercard sandbox: successful authorization, revocation mid-session, spend cap exhaustion, and merchant restriction violation