Skip to main content
Clink gives an agent access to a user’s payment cards and spending authorizations through MCP. Wallet Service manages that payment relationship. Browser Pay supplies a payment credential for a specific checkout so the agent can complete the purchase on the merchant’s website.

​
Card network partnerships and availability

Visa
Clink is a Visa Intelligent Commerce (VIC) partner. The current Visa Agent payment flow combines passkey verification, purchase authorizations, and tokenized payment credentials so an Agent can purchase within the user’s approved limits. See Visa’s documentation for an introduction to VIC. Whether a particular card can be used for Agent Pay depends on the current wallet and tool responses. See Passkeys and purchase authorization for how user approval and spending limits work together.

​
Choose your integration

Independent agent

Install the Clink Skill in your agent Host, connect MCP, and authorize your wallet. Start with a copyable installation prompt.

Agent platform

Connect each user through OAuth and call MCP from your platform. Register a public key with Clink when receiving encrypted Browser Pay credentials.
Both integrations use the same Wallet Service and Browser Pay tools. The difference is who manages the MCP connection, user tokens, and any credential decryption.

​
How the components fit together

The user connects their wallet and completes any requested card setup or purchase approval. The agent handles the merchant checkout. Clink returns the credential and records the result reported by the agent.

​
Wallet Service

Use Wallet Service to:
  • Read the user’s current payment cards and their Agent Pay readiness.
  • Let the user add or manage a card, or change the default card.
  • Create, inspect, and manage a purchase instruction: the user’s authorization to spend within defined limits.
  • Follow user actions and resume the corresponding operation.
OAuth grants access to tools; a purchase instruction authorizes spending. Completing OAuth does not by itself authorize a purchase. See Wallet Service for the relationship between cards, instructions, and payment.

​
Browser Pay

When the merchant checkout displays its card form and final total, call get_credential. If the user needs to add a payment card or approve spending, Clink returns a next action. Once a credential is available, the agent fills the merchant’s card form, submits payment, and calls confirm_result with the observed outcome. Issuing a credential does not mean the merchant has been paid. The Browser Pay guide covers the full flow, including a changed total, expired credential, and an unknown payment result.

​
What you need

Card eligibility and any additional setup are determined by the current wallet and tool responses. Read the connected server’s current tool schemas and rules when choosing a payment flow; the installation Skill is not a fixed copy of those rules.

​
Other commerce capabilities

Clink MCP also offers Catalog discovery and UCP Checkout. They have separate tools for searching products, preparing a checkout, completing it, and reading an order or digital delivery. See the Catalog and UCP reference when your integration uses those capabilities.

​
Continue