> ## Documentation Index
> Fetch the complete documentation index at: https://conto.finance/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connected-card walkthrough

> Connect a card, set agent limits, authorize a purchase, and review requests before your integration pays.

Bring your own agent and computer use or browser automation. Conto connects the card and checks your spending rules before your trusted checkout integration receives payment details. Your application handles finding products, navigating stores, and completing a supported checkout.

This walkthrough uses **Demo Buyer**, **Visa ending 4242**, and **Example Software** as illustrative data. The accompanying video shows the actual Conto card components with simulated responses. It does not connect a real card, perform cardholder verification, or make a purchase.

[Watch the captioned walkthrough](https://conto.finance/videos/connected-card-walkthrough.mp4) · 80 seconds · Demo data, no payment

## Before you begin

Use a Builder or Enterprise organization with connected cards enabled, an existing agent, and a member who can manage cards. Have the cardholder available to verify purchase authorizations. Confirm card eligibility and your checkout integration before using a real card. The dashboard flow uses USD and single-use authorizations.

## 1. Choose the card and cardholder

Open your agent's **Connected Cards** tab and choose **Connect a card**. Select **I own it** or **A teammate owns it**. Enter a new card through the secure hosted fields, or choose **Use a saved card** to select a card belonging to that cardholder. The video uses a saved demo card so no card numbers or verification secrets appear.

A saved card is not spending authority. The next steps establish the agent's limits and the permission for a particular purchase.

## 2. Set the agent's limits

For this example, set **$25 per transaction**, **$100 daily**, and **\$250 monthly**. Agent limits must fit within the card's limits.

Leave **Set up a purchase authorization now (optional)** off, choose **Review card connection**, review the cardholder and limits, and choose **Save card**. You can save the card without knowing what the agent will buy.

## 3. Authorize one purchase

Choose **Authorize purchase** on the connected card. Set **Purchase type**, **Merchant name**, **Merchant URL**, **Country**, **Amount (USD)** and **Expires in**. **Merchant category code** is optional. Choose **One purchase** for a single checkout, or **Multiple purchases** to let the agent draw against the amount more than once until the authorization expires.

The illustration uses **Example Software**, **[https://software.example](https://software.example)**, **US**, **\$25** and **1 hour**. That URL is not a store you can pay.

The same form appears during card setup if you tick **Set up a purchase authorization now (optional)**, so a card and its first authorization can be created in one pass.

Save the authorization. A cardholder must then choose **Verify authorization** and complete the provider's secure verification flow. For a teammate's card, share the verification link. They sign in to the same organization to use it. Conto confirms the authorization's status with the provider before it can be used. The video shows the waiting state and skips the private verification ceremony.

## 4. Let your trusted integration request payment

Your agent prepares the purchase with your computer-use tools. Your backend uses the [connected-card SDK](/docs/sdk/connected-cards) to request a credential against the verified authorization, using a stable idempotency key for that purchase. Conto checks the merchant, amount, current limits, and any review requirement.

If the request needs review, it appears in **Needs attention** on the agent's card tab. An eligible reviewer chooses **Approve** or **Reject**. Approval lets the integration retry the original request with the same input and key, and Conto rechecks the current rules. Approval itself does not submit a payment. A denied request must stop without requesting a replacement under a new key.

An approved draw returns a credential once. The trusted executor acknowledges delivery and passes it directly to the authorized checkout, keeping it in memory and out of model prompts, tool responses, screenshots, recordings, and logs. Your agent must not have another payment route that bypasses this boundary.

## 5. Check the outcome or stop access

Keep the Conto request ID and the merchant's non-sensitive order reference. Confirm payment using the merchant receipt and card activity. A credential being issued, received, or reported used is not proof of settlement.

If delivery or checkout is uncertain, stop and investigate the original request. Do not create a new key to retry payment. An issued credential's allowance is not automatically restored by a failed checkout.

To stop future credential requests, choose **Revoke** on the authorization. Conto blocks new requests and asks the provider to cancel the allowance. Already issued credentials may remain usable. Revocation does not freeze the original card or refund a purchase. If cancellation or a purchase outcome stays unresolved, contact support with the request ID and masked evidence, never full card details.