Stripe Integration Expert
Guide Stripe payment, billing, Connect, Terminal, tax, fraud, and webhook work with current-source checks and production-safe defaults.
Fast Workflow
- Identify the exact Stripe surface: Checkout, Payment Intents, subscriptions, Connect, Terminal, Radar, Tax, Issuing, Treasury, Identity, or webhooks.
- Inspect the existing app framework, Stripe SDK version, environment variables, database model, and webhook routing before changing code.
- Prefer simple hosted surfaces first (Checkout or Billing Portal) unless the product requires custom payment UI or marketplace flows.
- Verify security boundaries: secret keys stay server-side, webhook signatures are checked against the raw body, amounts are server-derived, and retries are idempotent.
- For current API details, read local docs if present or official Stripe docs before touching live-money behavior.
Detailed Reference
Read references/full-guide.md when you need implementation patterns, webhook templates, Connect flows, subscription examples, error handling, testing commands, and operational checklists. Keep this entrypoint loaded first, then load only the reference sections relevant to the task.
Documentation
Run npx agent-starter docs pull stripe in a Claude install, or pull/browse official Stripe docs for the target environment.
Safety Checks
- Do not invent product limits, API behavior, prices, compliance requirements, or security guarantees.
- Keep secrets server-side and use environment variables for credentials.
- Prefer the simplest supported integration path that satisfies the product requirement.
1---2name: stripe3description: Deep Stripe integration expert — Checkout, Payment Intents, Elements, subscriptions (including metered and tiered), Connect (Express/Standard/Custom + marketplace flows), Terminal, Radar, Identity, Tax, Issuing, Treasury, Climate, webhooks (signature verification, idempotency keys, retries). Invoke when user mentions Stripe, payments, subscriptions, checkout, webhooks, Connect/marketplace, refunds, invoices, or 3DS. Example queries — "accept a card payment with Payment Intents", "set up a metered subscription for usage-based billing", "build a marketplace where sellers onboard via Express", "verify a webhook signature and handle payment_intent.succeeded".4---56# Stripe Integration Expert78Guide Stripe payment, billing, Connect, Terminal, tax, fraud, and webhook work with current-source checks and production-safe defaults.910## Fast Workflow11121. Identify the exact Stripe surface: Checkout, Payment Intents, subscriptions, Connect, Terminal, Radar, Tax, Issuing, Treasury, Identity, or webhooks.132. Inspect the existing app framework, Stripe SDK version, environment variables, database model, and webhook routing before changing code.143. Prefer simple hosted surfaces first (Checkout or Billing Portal) unless the product requires custom payment UI or marketplace flows.154. Verify security boundaries: secret keys stay server-side, webhook signatures are checked against the raw body, amounts are server-derived, and retries are idempotent.165. For current API details, read local docs if present or official Stripe docs before touching live-money behavior.1718## Detailed Reference1920Read `references/full-guide.md` when you need implementation patterns, webhook templates, Connect flows, subscription examples, error handling, testing commands, and operational checklists. Keep this entrypoint loaded first, then load only the reference sections relevant to the task.2122## Documentation2324Run `npx agent-starter docs pull stripe` in a Claude install, or pull/browse official Stripe docs for the target environment.2526## Safety Checks2728- Do not invent product limits, API behavior, prices, compliance requirements, or security guarantees.29- Keep secrets server-side and use environment variables for credentials.30- Prefer the simplest supported integration path that satisfies the product requirement.
tuyv