stripe integration

Engineering Community

Skill notes

When to Use This Skill

Implementing payment processing in web/mobile applications Setting up subscription billing systems Handling one-time payments and recurring charges Processing refunds and disputes Managing customer payment methods

1. Payment Flows

Checkout Sessions Recommended for most integrations Supports all UI paths: Stripe-hosted checkout page Embedded checkout form

2. Webhooks

Critical Events: payment_intent.succeeded: Payment completed payment_intent.payment_failed: Payment failed customer.subscription.updated: Subscription changed customer.subscription.deleted: Subscription canceled

3. Subscriptions

Components: Product: What you're selling Price: How much and how often Subscription: Customer's recurring payment Invoice: Generated for each billing cycle

4. Customer Management

Create and manage customer records Store multiple payment methods Track customer metadata Manage billing details

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@wshobson · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview stripe-integration.preview
# Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.