> ## 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.

# Get started with Clink Agent Pay

> Understand Clink Agent Pay, payment protocol routing, Vault Services, and Agent Portal options.

Clink Agent Pay lets an Agent securely complete payments at supported merchants within the user's authorization. It selects a suitable payment path based on the user's card, authorization, and merchant checkout conditions, and the Agent or platform reports the actual result.

## Payment protocol options

Clink supports multiple payment routes so an Agent can choose the protocol that matches the card and checkout scenario.

### Visa Intelligent Commerce (VIC)

Visa VIC provides tokenized payment credentials, ties user authorization to purchase conditions, and supports Agent identity and transaction recognition in AI shopping.

### Mastercard Agent Pay

Mastercard Agent Pay supports Agent registration and verification, Agentic Tokens that reduce exposure of the original card details, user-controlled purchase authorization, and Agent transaction risk signals.

### UnionPay Agent Pay

UnionPay Agent Pay supports Agent purchases on behalf of users with Passkey authorization and secure payment credentials. It serves a similar role to Visa VIC and Mastercard Agent Pay.

### Stripe Shared Payment Token (SPT)

Stripe SPT lets an Agent use a user's payment capability with a designated merchant without giving the original card details to the merchant or the model. An SPT can constrain the merchant, amount, currency, validity period, and usage scope.

### Clink VCC

When a user's payment method does not support the major protocols currently available, Clink can issue a one-time virtual card through its issuing capability. The merchant does not need any special integration; Clink completes the routing automatically.

## Clink Agent Pay capabilities

Choose the capability that matches the task you need to complete:

| Capability | What it does | When to use it | First integration step |
| :- | :- | :- | :- |
| [Wallet Services](https://docs.clinkbill.com/guides/agent/wallet_service.md) | 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](https://docs.clinkbill.com/guides/agent/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](https://docs.clinkbill.com/guides/agent/ucp_pay.md) | 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](https://docs.clinkbill.com/guides/agent/quick_pay.md) | 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](https://docs.clinkbill.com/guides/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](https://docs.clinkbill.com/api-reference/agent-portal/overview.md) | 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). |

## Next steps

* Using your own Agent Host: start with [Local Agent quickstart](https://docs.clinkbill.com/guides/agent/quickstart.md).
* Building for multiple users: depending on your integration, read [How to integrate MCP](https://docs.clinkbill.com/guides/agent/platform_integration/mcp_integration.md), [How to integrate RESTful API](https://docs.clinkbill.com/guides/agent/platform_integration/restful_api.md), or [How to integrate Vault SDK](https://docs.clinkbill.com/guides/agent/platform_integration/vault_sdk.md).
* Need a wallet connection: read [MCP and OAuth connection](https://docs.clinkbill.com/guides/agent/platform_integration/mcp_integration.md).
* Need browser card substitution: read [Agent Vault SDK](https://docs.clinkbill.com/guides/agent/vault_sdk).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.