stripe-best-practices

Configure Stripe payment integrations with security and compliance best practices.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/Faouzi91/HomeFlex --skill stripe-best-practices-faouzi91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/Faouzi91/HomeFlex/tree/main/scripts/.agents/skills/stripe-best-practices
Command: npx skills add https://github.com/Faouzi91/HomeFlex --skill stripe-best-practices-faouzi91

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Stripe payment integrations frequently suffer from security misconfigurations, use of deprecated APIs, incorrect Connect platform setups, and non-compliance with Stripe's latest requirements, leading to payment failures, fraud risks, and regulatory penalties.

Core Features & Use Cases

  • API Selection Guidance: Recommends the correct Stripe API (Checkout Sessions, PaymentIntents, Connect v2, Billing APIs, Treasury) for each use case including one-time payments, subscriptions, and marketplace platforms.
  • Security Best Practices: Covers API key management, restricted keys, webhook validation, OAuth protection, and Connect liability rules to prevent data breaches and fraud.
  • Deprecated API Migration: Provides clear migration paths for outdated Stripe APIs like the Charges API and Sources API to maintain long-term integration stability.
  • Use Case: For a full-stack rental platform like HomeFlex, this skill ensures correct implementation of Stripe Connect for landlord payouts, secure payment processing, and compliance with Stripe's go-live requirements.

Quick Start

Use the stripe-best-practices skill to design a secure Stripe Connect integration for your rental platform's marketplace payouts and payment processing.

Frequently Asked Questions about stripe-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Stripe webhook signatures to prevent payment fraud?

Stripe webhook validation requires verifying webhook signatures using your endpoint secret and Stripe's signature header to confirm event authenticity, preventing fraudulent payment notifications and data breaches before processing any webhook events.

What's the best way to migrate from deprecated Stripe Charges API to PaymentIntents?

Migrating from deprecated Stripe Charges API to PaymentIntents requires following Stripe's migration paths to maintain integration stability, updating payment flow logic, and adhering to Stripe's latest API version standards for long-term compliance.

How do I configure Stripe Connect for marketplace platform payouts?

Stripe Connect configuration for marketplace payouts requires correct Connect account setup using Connect v2 APIs, applying proper liability rules and OAuth protection to ensure compliant multi-party payment processing across your platform.

Do I need restricted API keys for secure Stripe payment integration?

Secure Stripe payment integration requires restricted API keys for proper API key management, limiting access scopes to specific resources and operations, which prevents data breaches and reduces fraud risk across your payment infrastructure.

Which Stripe API should I use for subscription billing versus one-time payments?

Stripe subscription billing uses the Billing APIs for recurring charges, while one-time payments use Checkout Sessions or PaymentIntents, with each API selected based on your specific payment flow requirements and use case.

Why does my Stripe Connect integration fail go-live compliance requirements?

Stripe Connect integrations fail go-live compliance when platform setups are incorrect, API keys are unrestricted, or webhook validation is missing, requiring adherence to Stripe's latest API version standards and proper liability configuration.