---
title: Stripe
summary: Connect a Stripe account so your AI agents can look up payments and manage customers, invoices, refunds, and subscriptions under permissions you control.
category: integrations
slug: stripe
---

## What Stripe in Kronos lets your agents do

Once a Stripe account is connected to Kronos, your agents can — within
the permissions you grant — look up your billing data and act on it the
way you would in the Stripe dashboard:

**Read actions** (available when an agent has "Read only" or higher):

- Look up the details of a specific charge.
- Look up the details of a specific payment.
- Look up a specific refund.
- List the refunds you've issued.
- List a customer's saved payment methods.
- List your payment links.
- List your shipping rates.
- List your tax rates.
- Search your customers by name, email, or other details.

**Write actions** (available only when an agent has "Read and write"):

- Create a new customer.
- Delete a customer.
- Create a payment.
- Update a payment.
- Issue a refund.
- Create an invoice.
- Create a product.
- Create a price for a product.
- Create a subscription.
- Update a subscription.
- Cancel a subscription.

You decide which agent gets which level, and you can switch any
permission off in one click without disconnecting the Stripe account.

## Connecting Stripe

1. Open Kronos → **Connect** in the sidebar → **Applications** tab.
2. Click the **Stripe** card to open the detail dialog, then click the
   green **Connect** button.
3. You land on Stripe's own sign-in screen. Sign in to the Stripe
   account you want to connect and approve the access.
4. You're sent back to Kronos at the **Already connected** tab with the
   new Stripe entry selected, ready to assign to an agent.

You can connect more than one Stripe account if you run separate
businesses or environments — each appears as its own entry.

## Naming the connection

You can add a short personal note next to a Stripe connection (the
"Your note for this connection" field). Labels like "Main store",
"Subscriptions", or "Test account" make a long list easier to scan. The
note is yours only — it doesn't change anything on the Stripe side.

## Giving an agent access

On the Stripe management page click **+ Add AI Agent**, pick the agent
from the dropdown, then choose:

- **Off** — the agent cannot touch this Stripe account.
- **Read only** — the agent can look up charges, payments, refunds, and
  customers, but cannot create, change, refund, or cancel anything.
- **Read and write** — the agent can do all of the above plus create
  customers, payments, invoices, products, and subscriptions, issue
  refunds, and cancel subscriptions.

The same controls are available inside the AI Agent editor — scroll to
the **Connected Apps** section.

## Fine-grained overrides

Inside the permissions modal (the gear icon next to a Stripe account in
the agent editor or on the Stripe management page) you'll see the full
list of Stripe actions grouped by **Read tools** and **Write tools**.
Toggle individual actions on or off to override the preset.

Common combinations:

- **Billing-support agent**: preset Read only, no overrides. The agent
  can answer "was this charge successful?" or "did the refund go
  through?" but cannot move any money.
- **Refund-desk agent**: preset Read only, override "Issue a refund" ON.
  The agent can look things up and process refunds, but cannot create
  customers or change subscriptions.
- **Onboarding agent**: preset Read and write, override "Delete a
  customer" OFF and "Cancel a subscription" OFF. The agent can set up
  customers, products, and subscriptions but cannot remove customers or
  end subscriptions.
- **Full billing assistant**: preset Read and write, no overrides.

Click Save to apply. Changes take effect on the next message the agent
processes.

## Multiple Stripe accounts on the same agent

If an agent has access to two or more Stripe accounts (for example a
main store and a separate subscriptions business), the agent picks which
account to use on each action based on context. When the request is
ambiguous ("refund the last order"), the agent will ask which Stripe
account to use.

You can cut ambiguity by turning the agent's access to one of the
accounts off, or by giving the connections obviously distinct notes.

## When something goes wrong

- **"Needs reconnect"** badge — Stripe revoked or expired the
  connection. Open `/app/connect`, click Stripe, and walk through
  Connect again. Your per-agent permissions are preserved.
- **Agent says "I can't issue a refund"** — that agent's permission
  preset is Off or Read only without the "Issue a refund" override. Open
  the permissions modal and adjust.
- **Agent says the connected app is temporarily unavailable** — Stripe
  or the connection had a transient hiccup. Ask to retry in a moment. If
  it persists, check the Stripe management page for a "Needs reconnect"
  badge.

## Privacy

Kronos does NOT store your Stripe data. Each time an agent uses a Stripe
action, it fetches just-in-time from Stripe through the connection, uses
what it needs to complete the task, and discards the result. The audit
log records that the action happened (which agent, which action, when,
and whether it succeeded), but not the underlying payment or customer
data.

When you disconnect Stripe or cancel your Kronos subscription, the
connection and all per-agent permissions are deleted immediately.