Stripe
Stack Pack.

Stripe coverage across the full surface — Payments + Elements, Billing + Invoicing, Connect (platforms + marketplaces), Issuing (card programs), Identity (KYC + onboarding), Tax (automated jurisdictions), Radar (fraud), Sigma (warehouse analytics). Opinionated about subscription vs metered billing and when Connect is overkill.

Why it's in the catalog. Stripe is the default payments primitive — but the API surface is large and the right shape depends on the business model. The pack carries opinions on subscription billing patterns, Connect onboarding flows, and when Tax / Radar are mandatory vs nice-to-have.

Headline products and features the pack carries opinions on. Each lives as its own canonical page under stacks/stripe/<product>.md in the etyb-skills repo — currency-stamped, sourced, opinionated.

• Payments + Elements
• Billing (subscriptions + metered)
• Connect
• Issuing
• Identity (KYC)
• Tax
• Radar
• Sigma
• Webhooks

When /etyb routes a request to one of these roles AND the Stripe pack is in play, the role's reference is composed with the platform-flavored knowledge from this stack. Same role, sharper answer.

• › backend-architect
• › security-engineer
• › fintech-architect
• › e-commerce-architect
• › saas-architect

The three things on Stripe that a 2024-cutoff model is most likely to get wrong — and that this pack reflects.

• Billing usage-based meters: simpler than 2024-era metered subscriptions, MCP-aware
• Connect onboarding: hosted flows with KYC orchestration built in
• Webhook signing: rotate on a schedule, never log secrets

The Stripe pack comes with /etyb — one install, every pack ready to go. The overlay loads automatically when the work calls for it.

$ npx skills add e-t-y-b/etyb-skills

See the full install guide for Claude Code plugin and manual routes.