Provider · Payments

Stripe — Ashlr Stack Provider

Stripe: Billing, subscriptions, tax. Restricted / test-mode secret key stored in Phantom. Wire it into your project with one command via Ashlr Stack.

Payments · API key KEY-ONLY · v0.2 adds provisioning

Stripe — Billing, subscriptions, tax. Restricted / test-mode secret key stored in Phantom.

Dashboard ↗

One command

Add Stripe to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add stripe

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "accept payments from customers"

Auth flow

Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Create a restricted key at https://dashboard.stripe.com/apikeys (use test mode for development).

Secret slots

stack add stripe writes these 1 secret slot into your Phantom vault:

STRIPE_SECRET_KEY

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

MCP wiring

Stripe ships an MCP server. stack add stripe auto-wires it into .mcp.json so your Claude Code / Cursor / Windsurf session can use it immediately.

@stripe/mcp with STRIPE_SECRET_KEY piped from Phantom — create products, prices, and inspect events from the agent.

v1 notes

v1 only stores the key. Full Stripe Connect / account linking lands when we register the Ashlr OAuth app.

FAQ

Do I need a Stripe account to use it with Stack?

Yes — Stack provisions Stripe on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://dashboard.stripe.com and paste it once.

Where does Stack store my Stripe credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (STRIPE_SECRET_KEY) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove stripe` to pull the Stripe service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Stripe credentials in their dashboard — https://dashboard.stripe.com — and Stack's next `doctor --fix` will pick up the new values.