INVIZO SUBSCRIPTIONS LITE
Invizo Subscriptions Lite compatibility with REEID Translate
Invizo Subscriptions Lite compatibility with REEID Translate is being reviewed using official plugin documentation. Creates Stripe-powered recurring subscriptions using either a Standalone flow or a WooCommerce subscriptions mode. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Invizo Subscriptions Lite does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Invizo Subscriptions Lite is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Invizo Subscriptions Lite compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Creates Stripe-powered recurring subscriptions using either a Standalone flow or a WooCommerce subscriptions mode.
- Provides WordPress shortcodes for plan/store display, standalone checkout, customer account pages, and subscriber subscription details (e.g., `[invizo_store]`, `[invizo_plans]`, `[invizo_checkout]`, `[invizo_account]`, `[invizo_subscriptions]`, `[invizo_auth]`).
- Supports plan-scoped checkout via a shortcode attribute (`[invizo_checkout plan_id="123"]`) and via a checkout URL query string (`/checkout/?plan=123`).
- Implements a Stripe Payment Element checkout flow (Stripe.js loaded on checkout pages) intended to support SCA-ready payment flows.
- Stores subscription-related data in WordPress as custom post types with post meta linked to Stripe IDs (plans and subscriptions linked to Stripe customer/subscription identifiers).
- Uses Stripe webhooks and background sync to keep local subscription records aligned with Stripe.
- Optionally integrates with WooCommerce by adding an Invizo Subscription product type and letting WooCommerce handle the shopping flow while Invizo stores subscription details.
TRANSLATION BOUNDARY
Invizo Subscriptions Lite capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Invizo Subscriptions Lite and REEID Translate FAQ.
What does Invizo Subscriptions Lite do?
Invizo Subscriptions Lite has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Invizo Subscriptions Lite have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Invizo Subscriptions Lite?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Invizo Subscriptions Lite in a multilingual WordPress workflow.
REEID documents Invizo Subscriptions Lite functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.