Register a Visa token requestor and handle cryptogram-based authorization for network tokenization
domain: developer.visa.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enroll your Token Requestor ID (TRID) with Visa Token Service via the provisioning API, providing BIN sponsor and domain/device context
Receive a token PAN and token expiry in the provisioning response; store the token reference ID alongside the raw PAN reference
At checkout, request a Transaction Cryptogram (TAVV) from Visa Token Service by supplying the token PAN, token expiry, and transaction-specific data
Submit the authorization to the card network including the token PAN, cryptogram, ECI indicator, and token-specific field markers in the authorization message
Handle token lifecycle notifications (token status updates, PAN-to-token updates) via the Token Notification Service webhook endpoint
On token suspension or expiry, trigger re-provisioning or fall back to raw PAN flow using the token status check endpoint
Known gotchas
Cryptograms are single-use and bound to the transaction amount; reusing a TAVV across retries will cause a hard decline
Token PAN BIN ranges differ from the underlying PAN BIN, so BIN-based routing logic must be updated to recognize token BINs
Token status change notifications can arrive out of order; implement idempotent status reconciliation rather than applying updates sequentially
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?