Invizo Subscriptions Lite

Invizo Subscriptions Lite helps you sell recurring access, services, memberships, or subscription products from your WordPress site using Stripe.

You can use it in two ways:

• Standalone subscriptions: create plans in WordPress, show them with shortcodes, and send customers through a focused Stripe checkout flow.

• WooCommerce subscriptions: add an Invizo Subscription product type and let WooCommerce handle the shopping flow while Invizo stores subscription details.

The plugin is built for site owners who want subscription billing without turning every page into a full store. It gives you plan management, Stripe checkout, subscription records, webhook sync, and customer-facing account pages in one lightweight workflow.

Highlights

• Stripe Payment Element checkout for modern card payments and SCA-ready flows.

• Plan management inside WordPress, including price, billing interval, media, features, and trial days.

• Shortcodes for plan lists, checkout, account pages, login/register pages, and subscriber self-service.

• Customer portal pages where subscribers can review status, billing details, next payment dates, and saved payment methods.

• React-powered admin screens for plans, subscriptions, setup, and settings.

• Stripe webhooks and background sync to keep local subscription records aligned.

• Privacy-policy consent support on checkout when you configure a policy page.

• Optional WooCommerce product type for subscription products.

Shortcodes

Use these shortcodes on normal WordPress pages:

• [invizo_store] or [invizo_plans] – show available plans.

• [invizo_checkout] – show the standalone checkout.

• [invizo_checkout plan_id="123"] – lock checkout to one plan.

• [invizo_account] – show the customer account area.

• [invizo_subscriptions] – show subscriber subscription details.

• [invizo_auth] – show login/register links and account actions.

plan=123.

Who is this for?

Invizo Subscriptions Lite is useful for:

• Creators selling paid access on a monthly or yearly schedule.

• Agencies and service businesses billing clients on a recurring plan.

• Coaches, educators, and membership sites that need simple subscription checkout.

• WooCommerce stores that want a dedicated subscription product type connected to Stripe.

External services

This plugin connects to Stripe services outside your site.

• Stripe.js ( js.stripe.com ) is loaded on checkout pages so Stripe can render secure payment fields.

• Stripe API is used to create and update customers, create subscriptions, manage payment methods, create webhook endpoints when requested by an admin, and sync subscription/payment status.

• Stripe-hosted pages may be opened for billing portal actions where configured.

What data is sent to Stripe?

When a customer checks out or manages billing, the plugin may send the customer’s name, email address, selected plan, billing country/city/postal code, Stripe customer IDs, Stripe subscription IDs, payment method IDs, payment intent IDs, and related billing metadata needed to complete and maintain the subscription.

Payment card details are entered into Stripe-hosted payment fields and are handled by Stripe.

• Stripe Services Agreement: https://stripe.com/ssa

• Stripe Privacy Policy: https://stripe.com/privacy

Build and source files

The plugin includes generated browser assets for performance and the human-readable source files needed to review and rebuild them.

Admin app assets

• Generated files: assets/js/app.js and assets/css/app.css.

• Source directory: react-ui/src/.

• Important source files: react-ui/src/main.jsx, react-ui/src/App.jsx, react-ui/src/components/, react-ui/src/hooks/, react-ui/src/App.css, and react-ui/src/index.css.

• Build files included for review: react-ui/package.json, react-ui/package-lock.json, react-ui/vite.config.js, and react-ui/index.html.

• Rebuild command: cd react-ui && npm install && npm run build.

Other frontend assets

These files are shipped as human-readable source:

• assets/js/checkout.js

• assets/css/checkout.css

• css/account-portal.css

• css/store.css

PHP dependencies

Stripe’s PHP SDK is installed with Composer and prefixed with Strauss into InvizoSubscriptionsLiteVendor\Stripe\ under invizo-vendor/.

Stripe’s own SDK contains a cURL-based HTTP client. Those cURL calls are part of the third-party Stripe library, not plugin-specific HTTP code. Plugin-specific HTTP requests should use WordPress APIs.

The root vendor/ and node_modules/ folders are not included in the release package. The reviewable React source is included, but react-ui/node_modules/ is not.