Clone the Visa TAP reference implementation from github.com/visa/trusted-agent-protocol; review the Agent Registry, Merchant Backend, and CDN Proxy components to understand the trust architecture.
Submit your agent's public key and metadata to the TAP registry via POST /api/v1/agents/register; all verified registrants receive a Visa Trusted Agent credential, which is a signed JSON object.
In your agent's checkout request, include the Trusted Agent credential in the request header as specified in the TAP spec; the merchant's CDN Proxy or backend validates the credential signature before forwarding to payment processing.
Integrate TAP signals into your Stripe or Adyen payment session; both processors accept TAP credentials as part of their agent-aware checkout flows as of early 2026.
Monitor your agent's Agentic Directory listing in the Visa Developer Center; you can update metadata, rotate keys, or revoke credentials through the same portal.
Known gotchas
TAP is in the 'forward-leaning merchants adopt it as an option' phase as of April 2026; broad merchant baseline adoption is not expected until 2027 or later, so fallback flows for non-TAP merchants are required.
The Visa Acceptance Agent Toolkit (built on the TAP MCP server) is in pilot; access requires separate approval from Visa Developer Center — it is not open to all developers yet.
Visa TAP credentials reference the same Web Bot Auth Ed25519 key infrastructure; agents already registered with Cloudflare Web Bot Auth can reuse the same keypair rather than maintaining separate credentials.
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