Enroll in the Mastercard Agent Pay for Machines (AP4M) protocol and issue Verifiable Intent credentials for your agent so it can transact across Mastercard's card and stablecoin rails
Register your agent with Mastercard Agent Pay by submitting agent identity and public key through the AP4M enrollment portal; credentials and spending permissions are recorded on public blockchains (Polygon, Solana, or Base) rather than a private Mastercard database.
Obtain Verifiable Intent credentials — programmable spending rules specifying per-transaction caps, merchant restrictions, and expiry windows; these are publicly auditable on the selected chain.
At transaction time, include the agent's AP4M Verifiable Intent credential in the authorization message; Mastercard-certified processors (including Coinbase, Adyen, and Stripe) validate the credential before routing to settlement.
Choose settlement currency: AP4M supports both traditional fiat (via Mastercard card rails) and stablecoins; for micropayments worth fractions of a cent, use the stablecoin path via one of the 31 launch partners.
To revoke an agent's authorization, update or remove its on-chain Verifiable Intent credential; the next authorization attempt will fail at the network level.
Known gotchas
AP4M was officially launched on June 10, 2026; some partner integrations and processor certifications may still be in rollout — verify your processor's AP4M support status before going live.
Mastercard uses public blockchains as an authorization and credentialing ledger while keeping settlement on its own proven network; do not confuse on-chain credential storage with on-chain settlement.
Verifiable Intent is conceptually similar to but distinct from AP2's IntentMandate; the two systems are not interoperable by default — agents operating across both ecosystems must maintain separate credential objects.
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