Build a Stripe payments & events dashboard with Claude

This is an end-to-end example: connect a data source through the Stripe CLI, generate a dashboard from live numbers, and close the review loop on one link. Total time, start to shared link, is under fifteen minutes. The same shape works for any of the other examples — only the connection step changes.

Here's the finished dashboard, published to a canvas — click any tile or number to leave a comment, exactly as your team would:

The three moving parts

1. The Stripe CLI gives Claude read access to your Stripe account — balance, charges, payment intents, events, disputes — through commands it runs in your terminal. It authenticates with a restricted key, so you control what it can touch.
2. Claude runs the CLI, pulls the numbers, and writes a single self-contained HTML dashboard. You iterate on it in the artifact panel until it's right.
3. Drafty turns that HTML into a stable link your team reviews. Comments pin to the exact element; Claude ships the fix to the same URL.

The generation step is fast now. The part this example is really about is the third one — getting the dashboard in front of people without losing their feedback to a screenshot circled in Preview.

Step 1 — Connect the Stripe CLI

Install the official Stripe CLI, then authenticate. You run this part yourself once.

Install (macOS, Homebrew):

On other platforms, install via npm with npm i -g @stripe/cli, Scoop on Windows, or the stripe/stripe-cli Docker image.

Authenticate:

stripe login opens a browser to authorize the CLI and generates a restricted API key for your account — valid for 90 days, stored locally in ~/.config/stripe/config.toml. Once it's logged in, Claude can run stripe get, stripe charges list, stripe events list, and the other read commands in your terminal.

Step 2 — Pull the numbers

Ask Claude in plain language. It runs the CLI's read commands (stripe get, stripe charges list, stripe events list) to fetch real data:

Claude runs the commands, returns the figures, and you sanity-check them against the Stripe Dashboard before going further. This is the moment to catch a wrong assumption — a test-mode key, a currency mix, a status filter you didn't expect — while it's cheap.

Step 3 — Build the dashboard

Once the numbers look right, ask for the artifact:

Claude renders it live in the artifact panel. Iterate in place — you're not regenerating from scratch:

• "Make the success rate a ring gauge and put it next to gross volume."
• "Add a 14-day daily-volume bar chart."
• "Color failed charges red in the recent-charges table."

Step 4 — Publish to Drafty for review

A Claude artifact link is a preview, not a stable URL — iterate the artifact and the link you already sent now shows the old version. Ask Claude to publish it to a Drafty canvas instead, so the link you share always stays current:

Claude pushes the dashboard and hands back a drafty.im/canvas/… link that renders on any device. Send it — your team opens it in a browser, no login and no Claude account needed.

Step 5 — The review loop

This is the part that's not obvious until you've done it once.

A reviewer clicks the specific tile, chart, or number they want changed and leaves a pinned comment — "this success rate looks low, are we counting test-mode charges?" The comment is anchored to that element, not floating in a Slack thread. Claude reads the comments through the CLI, reruns the relevant Stripe command if needed, and pushes a revised dashboard to the same URL. The reviewer refreshes and sees the change; the thread stays attached to the element.

The mechanic matters because of what it removes. A Slack message about a chart produces "the number on the left looks wrong." A pinned comment on the actual tile produces "this — exclude test-mode charges from the success rate." One of those produces a correct revision; the other produces a guess.

Keeping it fresh

A CLI-generated dashboard is a snapshot — it holds the numbers Claude pulled when it built it; it doesn't re-run the Stripe commands when someone opens the link. For a weekly review or a board-ready snapshot, that's fine.

To make it a live canvas that always shows today's figures, copy this prompt — Claude sets up the refresh for you and schedules it to run on its own:

The link stays stable while the content updates underneath it — see keeping a canvas updated automatically.

What to watch for

• Read-only, always. A payments dashboard needs read access and nothing more. Scope the restricted key accordingly, or rely on stripe login's default read access.
• Check the figures before you share. The CLI returns exactly what you ask for — if your success-rate query includes test-mode charges or your volume query mixes currencies, the dashboard will confidently show the wrong number. Reconcile against the Stripe Dashboard once.
• The link is the deliverable, not the artifact. Share the Drafty URL, not the Claude artifact preview — that's the one you can update in place.