Stripe

Stripe · Live

Ask Stripe what's actually flowing through the account.

Read Stripe payments, customers, subscriptions, refunds, and dispute data so the agent can reconcile revenue and surface payment friction.

Connect StripeHow it worksLive
Auth
Restricted API key
Access
Read-only
Plan
Every plan
Freshness
Live — every call hits Stripe's API
Available on
Every plan

Examples

Questions teams actually ask.

The tools it pulls from are shown inline — every answer in Lumen cites the underlying records it read.

Finance

Total successful charges, refunds, and net revenue last 30 days, broken down by product.

pullslistChargeslistRefunds
Subscriptions

MRR, churn, and net new MRR for the last 6 months.

pullslistSubscriptionslistInvoices
Disputes

Open disputes by reason and dollar amount — flag anything we should respond to today.

pullslistDisputes

Scope

What Lumen sees. What it can change.

Read is on by default. Every write is a separate toggle, capped per user, and logged.

Read

What Lumen reads

Lumen calls the Stripe REST API using a restricted API key you paste at install. Use a key with read-only permissions everywhere — Lumen never needs write scope by default.

  • Customers

    Lookup, default payment method, balance, lifetime value, subscription state

  • Charges & refunds

    Search by date / status / customer; outcome / risk score; refund history

  • Subscriptions & invoices

    Status, plan, MRR contribution, next billing date, paid / open invoices

  • Disputes

    Reason, status, amount, due-by date, evidence-submission state

  • Payouts & balance

    Recent payouts, available / pending balance, fee breakdown

Write · opt-in

What Lumen can write

Lumen is read-only on Stripe. Refunds, subscription edits, and customer updates are out of scope today — manage those in the Stripe dashboard.

    Every call is logged with user, operation, resource type, ID, and date range. Read-only by definition; nothing is ever mutated. Exportable as CSV.

    Install

    Connect in under a minute.

    No keys, no call, no app marketplace fine print.

    1. Generate a restricted key
      01

      Create a read-only restricted API key

      In Stripe → Developers → API keys → Restricted keys, create a key with read access on Customers, Charges, Subscriptions, Invoices, Disputes, and Balance. Leave write permissions off.

    2. Connect
      02

      Paste the key into Lumen

      In Settings → Integrations → Stripe, paste the restricted key. It's stored encrypted at rest.

    3. Ask
      03

      Try a warm-up question

      Start with "Net revenue and refund rate last 30 days" — the agent will pull charges and refunds and compute the ratio.

    Connect Stripe. Reconcile revenue at the source.

    Restricted API key. Read-only. No write scope ever.

    Connect StripeBack to all integrations