stripe-best-practices
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
90
86%
Does it follow best practices?
Impact
96%
1.29xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Evaluation results
100%
10%Membership Platform Subscription Integration
SaaS subscription billing setup
Billing API usage
100%
100%
Checkout Sessions for frontend
100%
100%
No payment_method_types on session
100%
100%
Prices not Plans
100%
100%
No manual renewal loop
100%
100%
Customer Portal for self-service
100%
100%
Restricted API key
0%
100%
Latest API version
100%
100%
Webhook signature verification
100%
100%
No Charges API
100%
100%
98%
20%Freelance Marketplace Payment Platform
Connect marketplace account onboarding
Accounts v2 API
0%
100%
No legacy type parameter
100%
100%
Controller properties used
100%
100%
No legacy account type terms
100%
100%
Stripe-hosted onboarding
100%
100%
Single charge type
100%
100%
PaymentIntents or Checkout for fund flows
100%
100%
No payment_method_types
100%
100%
Restricted API key
0%
100%
Latest API version
100%
60%
92%
38%Stripe Integration Security Audit and Hardening
API key security hardening
No hardcoded key
100%
100%
Restricted API key recommended
0%
100%
Webhook signature verification
100%
100%
No key logging
100%
100%
Debug env-dump endpoint removed
100%
100%
Pre-commit hook created
100%
100%
payment_method_types removed
0%
100%
IP allowlist recommended
0%
100%
Separate env keys
0%
100%
Stripe IP allowlist for webhooks
0%
0%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.