> ## Documentation Index > Fetch the complete documentation index at: https://docs.clinkbill.com/llms.txt > Use this file to discover all available pages before exploring further. # Agent Solutions > Connect an agent to Clink Wallet and let it pay on merchant websites with Browser Pay. 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](https://developer.visa.com/capabilities/visa-intelligent-commerce/overview) 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](/guides/agent/wallet_service#passkeys-and-purchase-authorization) for how user approval and spending limits work together. ## Choose your integration Install the Clink Skill in your agent Host, connect MCP, and authorize your wallet. Start with a copyable installation prompt. 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. * **Independent agent:** follow the [quickstart](/guides/agent/quickstart) to connect and make your first purchase, then use [Browser Pay](/guides/agent/browser_pay) for payment steps and recovery. * **Agent platform:** start with [platform integration](/guides/agent/platform_integration), implement the connection with [MCP and OAuth](/guides/agent/mcp_integration), then follow [Browser Pay](/guides/agent/browser_pay) for checkout. ## How the components fit together ```mermaid theme={null} %%{init: {"theme":"base","themeVariables":{"fontFamily":"inherit","fontSize":"14px","primaryColor":"#F7F7F7","primaryTextColor":"#161616","primaryBorderColor":"#E7E7E7","lineColor":"#71717A","edgeLabelBackground":"#FFFFFF"},"flowchart":{"nodeSpacing":40,"rankSpacing":38,"padding":14,"diagramPadding":12}}}%% flowchart TD I["Independent agent
Host"] --> M[Clink MCP] P[Agent platform] --> M U[User] -->|Connect and
authorize| W[Clink Wallet] M --> W W --> C[Payment cards] W --> A["Spending
authorizations"] M -->|Browser Pay
credential| B[Agent browser] B -->|Submit payment| S[Merchant checkout] B -->|Observed
result| M classDef emphasis fill:#F8E1CC,stroke:#F8E1CC,color:#161616 class M emphasis ``` 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](/guides/agent/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. | Credential returned | Integration behavior | | :- | :- | | `credential.card` | Use the returned card fields for the checkout. No additional decryption is needed. | | `credential.key` and `credential.payload` | Decrypt the envelope using the key paired with the public key registered for the platform, then use the decoded card fields. | Issuing a credential does not mean the merchant has been paid. The [Browser Pay guide](/guides/agent/browser_pay) covers the full flow, including a changed total, expired credential, and an unknown payment result. ## What you need | Requirement | Independent agent | Agent platform | | :- | :- | :- | | MCP connection | Host supports Streamable HTTP and OAuth | Platform implements the MCP connection and user OAuth flow | | Merchant checkout | Agent has browser interaction capability | Platform supplies browser interaction capability | | User actions | User completes login, card setup, and any approval on their device | Platform presents the returned links to the appropriate user | | Encrypted credentials | Only needed if this connection receives `key` / `payload` | Contact Clink offline to configure the platform public key; use the [decryption example](/guides/agent/browser_pay/decryption) | 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](/api-reference/mcp/commerce) when your integration uses those capabilities. ## Continue * [Independent agent quickstart](/guides/agent/quickstart) * [Agent platform integration](/guides/agent/platform_integration) * [Wallet Service tools](/api-reference/mcp/wallet) * [Browser Pay tools](/api-reference/mcp/browser_pay) * [Operations, rules, and errors](/api-reference/mcp/operations) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.