AI workers for Stripe

What is an AI worker for Stripe?

An AI worker for Stripe is an AI agent scoped to one payments job, such as writing up yesterday's revenue or listing the subscriptions whose payment failed overnight. It reads your Stripe account through a restricted key you create and scope yourself, so Stripe's own permissions decide what it can reach before you narrow it again per worker.

What these workers do

Write up yesterday's revenue

Reads charges, refunds and balance and sends the short version each morning: what came in, what went back out, and which number is different enough to be worth a look.

Catch failed payments while they can still be saved

Lists the invoices and subscriptions whose payment failed overnight, with the customer and the reason, so someone can act inside the retry window rather than after it.

Watch the dispute queue

Checks open disputes and their evidence deadlines, so a response window never closes because the notification was buried in an inbox.

Track subscription churn

Compares cancellations and renewals against previous periods and flags the movement worth explaining, rather than waiting for the monthly number to look wrong.

Answer questions about the account

Looks up a customer, an invoice or a payout on request, and comes back with the answer written out instead of a dashboard someone still has to read.

How an AI worker runs in Stripe

The key you paste is the real boundary

Two tools are general purpose, and that matters

Sandbox and live look identical

What payments reporting is actually for

Stripe questions, answered.

Can a worker refund a customer or cancel a subscription?

Only if you allow it twice over. The restricted key you paste has to permit writes at all, and the worker has to be given the write tool. Neither happens by default. For reporting jobs, create a read-only key and the question does not arise.

Which Stripe data can a worker see?

Whatever your restricted key permits, narrowed again by the tools you allow that worker. Stripe's key scopes are the outer boundary and they are set by you inside Stripe, so a reporting worker can be given revenue data without also being able to reach anything else.

Will it read live payments or test data?

That depends entirely on the key you paste. Stripe manages MCP access separately for live mode and for each sandbox, and nothing in a response says which one answered, so start with a sandbox key and move to live deliberately.

Do you store our payment data?

No. Reads are made against Stripe on request and returned to the worker. What is retained is the audit trail of which token called which tool and when, not the payment records themselves.

Are card numbers ever exposed?

Stripe's API does not return full card numbers to this kind of connection. What a worker can see is the sort of detail shown on a receipt, such as card brand and last four digits, and only if the key you created permits reading that resource.

What AI workers can do in Stripe

The tools a worker can be granted in Stripe once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.

Refund a payment

Refund a charge or payment intent. Money leaves the account and a refund cannot be reversed. Called without an amount it refunds the full charge, so kits that use it should pin one.

Explain an analytics metric

Explain one metric: its definition, how Stripe computes it and which dimensions it can be sliced by.

Get the account balance

Read the Stripe balance: available, pending and reserved funds, by currency.

Get Stripe account info

Read the connected Stripe account: business profile, country, default currency, capabilities and whether charges and payouts are enabled.

List analytics metrics

List the analytics metrics available for this account and what each one measures.

Break down an analytics metric

Break one metric down by a dimension such as country, payment method or product, over a window.

Open a metric in Stripe

Return a link to the metric's view in the Stripe Dashboard for a human to open.

Run a Stripe analytics query

Run an analytics query over the account's payments data and return the computed series. Counts as a write because it creates a query run on the account.

Read from the Stripe API

Read any documented Stripe resource by GET: customers, charges, payment intents, invoices, subscriptions, disputes, payouts and balance. The widest read in the app, and the one redaction and DLP earn their keep on. The connected restricted key bounds what it can reach.

Search the Stripe API

Find Stripe objects with Stripe's search query language across customers, charges, invoices, subscriptions and prices, for when you know a field value but not the ID.

Write to the Stripe API

Create or update any documented Stripe resource by POST: customers, prices, invoices, subscriptions, refunds and more. Real money and real customer records change. The connected restricted key bounds what it can reach.

Run a Stripe report

Generate a Stripe report over a window: payments, payouts, balance change or revenue recognition. Counts as a write because it creates a report run on the account.