Aller au contenu
TakoAPI
Retour aux skills

stripe-best-practices

par ifoster01

Transportation
1.5kTéléchargements rapportés par clawskills.sh
1Étoiles
0Vues
0 mention J'aimeConnecte-toi pour aimer ce skill
—Pas encore noté
Ta note

Résumé

Best practices for building Stripe payment integrations.

Description

Ce que fait ce skill

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.

Quand l'utiliser

  • 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

Exemple de workflow

ENTRÉE

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

SORTIE

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

Prérequis

  • Stripe account
  • Stripe API keys

Installation

clawhub install ifoster01/stripe-best-practices

Exécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.

Liens