add-payment

Stripe subscription billing requires installing Stripe dependencies and configuring checkout flows starting with sk_test_ keys. Implement webhook signature verification and event idempotency to safely process customer payments and subscription updates.

Handling Stripe webhooks requires verifying webhook signatures to confirm event authenticity and applying idempotency checks for retried events. This prevents duplicate processing when Stripe resends events, ensuring your subscription billing data remains accurate and secure.

Yes, you can extend existing Stripe Checkout, webhook, and Customer Portal patterns already wired in your codebase. The implementation mirrors your current Stripe setup to add new subscription tiers, update billing flows, and register new webhook event handlers consistently.

When a different payment processor is detected in your application, the Skill adapts the implementation approach accordingly. It ensures correct Stripe Customer Portal integration and billing flow setup while respecting existing payment infrastructure rather than blindly overwriting current processor logic.

Yes, you must use strict test-mode keys, specifically sk_test_ prefixed keys, when setting up Stripe subscription billing. This ensures safe development and testing of checkout flows, webhook handlers, and Customer Portal integration before processing live payments.

The best way to add a new subscription tier with Customer Portal support is to configure the pricing tier in Stripe, integrate the Customer Portal for self-service management, and implement the related webhook event handlers with proper signature verification and testing.