Integrate Google Pay payment tokens into an agent-driven merchant-initiated transaction (MIT) flow using the Google Pay API and Universal Commerce Protocol
Integrate the Google Pay API (Web or Android) to obtain a payment token during a buyer-present session; the token is a JSON object encrypted with your processor's public key — pass it to your processor rather than attempting to decrypt it yourself
Subscribe to token lifecycle notifications: as of recent Google Pay API updates, processors and merchants can receive lifecycle events when underlying credentials change (e.g., card renewal, suspension); use these to proactively contact customers before the next billing cycle rather than discovering stale credentials at auth time
Mark subsequent agent-initiated charges as MIT in your authorization request; Google Pay tokens acquired in an initial customer-present session can fund MIT charges for subscriptions or agent-triggered purchases, but the correct MIT indicator must be set or the network may treat the transaction as fraudulent card-not-present
If your existing Google Pay backend and merchant ID are enrolled in UCP, you can accept UCP-routed agent payments without re-provisioning; Google confirmed existing Merchant IDs are fully compatible with UCP as of the 2026 ecosystem update
Integrate the Google Pay and Wallet Developer MCP server (Public Preview as of 2026): it lets AI agents connected to your development environment manage integrations, troubleshoot auth errors, and generate payment code via plain-language tool calls
Test the full MIT lifecycle: initial customer-present token acquisition, agent-triggered repeat charge with MIT indicator, token lifecycle update event, and a charge attempt after a token suspension event to confirm your revocation handling
Known gotchas
Google Pay tokens are processor-specific encrypted blobs; switching processors invalidates existing tokens and requires customers to re-authenticate — plan processor transitions carefully if you hold Google Pay tokens at rest
The Developer MCP server is in Public Preview and not recommended for production payment operations; use it for development tooling only until Google announces general availability
MIT flagging rules differ between Visa and Mastercard on the Google Pay rails; verify the exact field and value with your acquirer for each network, since an incorrect MIT indicator can cause the issuer to decline the charge or trigger a rules violation
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