Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (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, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
82
86%
Does it follow best practices?
Impact
89%
2.69xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
Stripe Connect marketplace: seller onboarding and payment splitting
v2 account creation endpoint
0%
100%
No legacy account type field
0%
100%
Recipient configuration requested
0%
100%
v2 capability status check
0%
100%
No deprecated v1 capability fields
0%
100%
Express dashboard default
0%
100%
No application_fee_amount on transfer
0%
0%
account_onboarding component
100%
100%
notification_banner component
0%
100%
account_management component
100%
100%
No API onboarding
100%
100%
Stripe one-time payment checkout integration
Uses Checkout Sessions
100%
100%
Omits payment_method_types
0%
100%
Uses payment_method_configurations or excluded_payment_method_types
0%
70%
Includes integration_identifier
0%
100%
Random 8-letter suffix in integration_identifier
0%
70%
Recommends restricted API key
100%
100%
No API key in source code
100%
100%
API key in environment variable
100%
100%
Latest API version
0%
0%
No Charges API
100%
100%
Table of Contents
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.