integrationlisted

Use this FIRST for ANY Stripe integration to pick the right approach before writing code. Router that classifies the ask (accept a one-time payment, subscriptions/recurring/invoicing, in-person/POS, marketplace/platform payouts, fraud/identity/bank-linking) and routes to the correct sibling skill and integration surface (Payment Links, Checkout, Elements, mobile/Terminal SDKs). Triggers — "Stripe", "accept a payment", "PaymentIntent", "checkout", "subscription/recurring/plan/trial/metered billing", "invoice", "marketplace/platform/Connect/split funds/payout", "Terminal/card reader/POS/Tap to Pay", "webhook/Stripe-Signature", "test cards/Stripe CLI", "publishable/secret/restricted key", "idempotency key". API version pinned 2026-06-24.dahlia.
Florkin/claude-stripe-skills · ★ 0 · API & Backend · score 70

Install: claude install-skill Florkin/claude-stripe-skills

# Stripe Integration (router) Entry point for every Stripe task. **Classify the need, then route.** Do not implement a full flow from this file — it names the canonical objects and hands off to the specialised sibling skill. The shared foundations (auth, idempotency, money, errors, CLI, testing) apply to every route and live in `reference/`. **Pinned Stripe API version: `2026-06-24.dahlia`** (major release "Dahlia"). Override per request with the `Stripe-Version` header; each webhook endpoint pins its own version at creation. See `reference/foundations.md`. All examples below are SDK-neutral (raw REST + a one-line cross-SDK note). Nothing here is framework-specific. --- ## When to use / decision tree Two questions, in order: **(1) WHAT is being built** → picks the product + sibling skill. **(2) HOW is it surfaced** → picks the UI/integration surface. ### Step 1 �� WHAT (classify the product) | The ask is about… | Product family | Route to | |---|---|---| | Accept a one-time / on-demand payment for **your own** business | Payments (PaymentIntent) | **stripe-suite:payments** | | Recurring charges, subscriptions, plans/tiers, trials, renewals, metered/usage-based, automated invoicing | Billing | **stripe-suite:billing** | | In-person / point-of-sale, physical card reader, Tap to Pay | Terminal | **stripe-suite:terminal** | | Platform/marketplace: pay out to or split funds among **other** parties (multiple sellers/vendors) | Connect | **stripe-suite:connect** | | Receive