| Wallet Services | Manages payment cards, wallet state, and purchase authorization through MCP. | An Agent needs to read or manage a user’s wallet, or prepare purchase authorization for a payment. | Connect the user’s MCP with OAuth, then read the current wallet state and tool rules. |
| Browser Pay | Issues a checkout credential for a merchant website and records the observed result. | Use when the Agent can operate the merchant’s browser checkout page. | Read the merchant’s final total, then request get_credential. |
| UCP Pay | Runs a structured product checkout through Catalog and UCP. | Use when the merchant supports UCP and the flow needs product, fulfillment, order, or digital-delivery state. | Search for the exact product and confirm its options, then call create_checkout. |
| Quick Pay | Creates and tracks a direct Agent Payment Session. | Use when the integration only needs a simple direct payment-session API. | Create one payment session with the original amount and checkout context. |
| Agent Vault SDK | The browser fills a placeholder card while Clink keeps the real card inside its PCI boundary. | Use when a platform controls a Playwright or CDP browser and the Agent must not handle real card details. | Configure server credentials and attach the SDK to the merchant page. |
| Agent Portal | Provides account, wallet, purchase authorization, payment credential, result, order, refund, and settings capabilities. | Use when a platform needs to provide Clink’s standard Portal experience, or build its own wallet, authorization, and order UI. | First review Agent Portal’s capabilities, then choose Hosted Agent Portal (MCP) or Customized Agent Portal (API). |
