Description
Summary I already have a fully completed Chrome Extension called YouTube Shield (Manifest V3). The project is fully functional. All features, logic, UI, and UX have already been completed. Your task is only to integrate Stripe payments into the existing extension. Nothing else needs to be rebuilt. Please do not redesign the interface, change the UI/UX, or create custom payment pages or payment forms. The extension should use Stripe's default UI (Stripe Checkout, Stripe Billing, Customer Portal, and any other built-in Stripe solutions whenever appropriate). The goal is to rely on Stripe's native payment interface as much as possible. The extension must become fully subscription-based. If a user does not have an active subscription, they must not be able to use the extension. When the extension is opened without an active subscription, Stripe Checkout should immediately appear. The available subscription plans should be: 7-Day Free Trial Monthly — $3.99 3 Months — $11.29 Yearly — $41.99 Users should also be able to purchase any paid plan directly without starting the free trial. The free trial should use Stripe's standard Trial functionality. After the trial ends, Stripe should automatically continue with the paid subscription unless the user cancels it before the trial expires. If a subscription expires, is cancelled, or otherwise becomes inactive, the extension must automatically become locked until the user purchases another subscription. The extension already contains a Donate button located in: Settings → Support Development At the moment, this button is only a placeholder. Please connect it to Stripe so that clicking it opens Stripe's default payment interface, allowing users to donate any amount they choose. Donations are completely optional and must not affect subscription status or access to the extension. The project is already completed. Please keep changes to the existing codebase as minimal as possible. Only implement the Stripe integration and everything required for subscriptions and donations. The technical implementation (subscription verification, user identification, Stripe configuration, etc.) is entirely up to you. Please use the simplest, cleanest, and most reliable solution while relying on Stripe's built-in functionality whenever possible. One important note: the existing project was originally built using AI-assisted "vibe coding", not traditional software engineering. Please keep this in mind when working with the codebase and avoid unnecessary refactoring unless it is required for stability or the Stripe integration. If anything is unclear, please ask me before making assumptions.