Skip to content
TakoAPI
Back to skills

stripe-best-practices

by ifoster01

Transportation
1.5kDownloads reported by clawskills.sh
1Stars
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Best practices for building Stripe payment integrations.

Description

What This Skill Does

A knowledge skill that encodes Stripe's recommended integration patterns, deprecated API warnings, and decision rules for payments, subscriptions, and Connect platforms. It guides agents toward current Stripe APIs and away from legacy ones like Charges API, Card Element, and Sources API.

Encoding these rules in a skill prevents agents from defaulting to outdated Stripe APIs that Stripe itself recommends against, which can cause compliance issues and integration debt.

When to Use It

  • Choosing between CheckoutSessions and PaymentIntents for a new checkout flow
  • Setting up recurring billing for a SaaS product
  • Migrating an existing integration off the deprecated Charges API
  • Building a marketplace with Connect and selecting the right charge type
  • Saving a customer payment method without an immediate charge

Example Workflow

INPUT

User asks: I want to add subscription billing to my SaaS app

AGENT
  1. 1

    Identifies recurring revenue use case and applies Billing APIs preference

  2. 2

    Recommends Stripe Billing APIs combined with Checkout frontend

  3. 3

    Advises against raw PaymentIntents for subscription management

  4. 4

    Suggests Stripe-hosted Checkout as the default frontend unless more control is needed

  5. 5

    References stripe:billing/design-integration for integration planning

OUTPUT

A recommended integration approach using Stripe Billing APIs and Checkout, with links to relevant Stripe docs

Requirements

  • Stripe account
  • Stripe API keys

Installation

clawhub install ifoster01/stripe-best-practices

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links