Stripe

Stripe takes money through a few high-level objects (Checkout Sessions, the Billing APIs, Connect's Accounts v2) and reports what happened afterwards through events. Most outcomes are decided by two choices: picking the highest-level object that fits (Checkout Sessions over hand-built PaymentIntents, Billing over a renewal loop, Accounts v2 fields over legacy account types), and treating webhooks as the source of truth, verified on the raw body and handled idempotently, so that fulfillment and access never depend on the client or the success page. Stripe changes often: pin the API version, use the latest SDK, and read the current docs (stripe docs) rather than memory. Some files carry facts from a third-party skill set (appeeky/stripe-skills), tagged [appeeky]; where they disagree with Stripe's own material, the files say so and follow Stripe. For in-app subscriptions sold through the App Store and Google Play, see revenuecat SKILL.md.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]