Evoxup Membership — Membership, Licensing, & Universal Integrations

Evoxup Membership is a WordPress platform for managing memberships, licensing, customers, products, entitlements, commerce fulfillment, and integrations from one administration area. Every function included in the WordPress.org plugin is free to use. Evoxup Membership does not require a paid license, paid membership, trial, quota, or activation key to unlock functionality that is already included in the plugin. A license or membership key may be used only to verify eligibility for separately distributed commercial Evoxup packages or external services that are not included in this WordPress.org plugin. What Evoxup Membership manages

• EVO Products as the canonical product identity used by Evoxup.
• Membership Plans and Product-to-Plan relationships.
• Customers and members, while preserving the native WordPress user ID when a WordPress account is linked.
• Integrated Member Administration workspace that lists native WordPress users and EVO members together, then provides profile, membership, license, activation, order-context, entitlement, and activity management after an EVO member record exists.
• Membership lifecycle, status, start and expiration dates.
• EVO licenses, activations, verification rules, domains and entitlement state.
• Product and membership entitlements.
• Normalized order and transaction records.
• Purchase fulfillment from WooCommerce or verified external providers.
• Versioned REST/API integration surfaces for supported integrations.
• Optional bundled Lite modules that run locally and can be enabled or disabled by an administrator.

Products, plans, members, and entitlements An EVO Product is the central commercial object. A Product can be linked to one or more Membership Plans, and a Membership Plan can include one or more Products. A successful verified purchase can resolve the mapped EVO Product, create or update the Evoxup customer/member record, grant the configured Membership Plan, issue an EVO license when EVO licensing is selected, create entitlements, and record the normalized transaction. It does not create WordPress user accounts. A WordPress account and an EVO member record remain separate identities. When a matching WordPress account already exists, Evoxup can link it to the EVO member record without replacing the native WordPress user ID. Licensing Evoxup can issue and manage EVO licenses for Products configured to use EVO licensing. License verification can use the Product, license status, activation/site binding, membership entitlement, and configured tier requirements. If a Product is configured to use another supported licensing provider, Evoxup does not force EVO license issuance and can preserve that provider's ownership of the licensing flow. Built-in Evoxup Membership functionality is never unlocked by these license checks. WooCommerce integration WooCommerce is optional. When WooCommerce is installed, an administrator can map WooCommerce products to EVO Products and define how the purchase should be fulfilled. A successful WooCommerce order can trigger the configured Evoxup membership, entitlement, customer/member, and licensing workflow. When EVO licensing is selected, Evoxup can issue the corresponding EVO license. When another provider is selected, Evoxup respects that provider instead of generating a duplicate EVO license. Evoxup uses supported WooCommerce APIs and declares compatibility with WooCommerce HPOS and Cart/Checkout Blocks for the integration paths used by the plugin. Verified webhooks and universal integrations Evoxup can receive verified commerce events from configured external providers. Webhooks are fulfillment inputs, not a remote administration channel. A verified provider event can:

• Resolve a provider product to an EVO Product.
• Create or update the Evoxup customer/member record.
• Create or update the normalized order record.
• Grant, update, cancel, or revoke the configured membership or entitlement according to the verified event.
• Issue an EVO license when EVO is the selected licensing provider.
• Process supported refund, cancellation, and revocation events.

Webhook payloads cannot choose privileged WordPress roles, install or remove plugins/themes, change arbitrary WordPress settings, execute PHP or SQL, or perform arbitrary filesystem operations. Remote webhook fulfillment does not create WordPress users. If a matching WordPress account already exists, Evoxup may link it to the EVO member record by the supported identity-matching workflow. Free modules and optional add-ons Evoxup Membership 1.8.5 includes optional local Lite modules that can be enabled or disabled by an administrator from Extensions & Add-ons. These modules are bundled in the plugin ZIP and are fully functional without a paid key. PRO and SUPER STAR add-ons shown on the Extensions & Add-ons screen are informational references to separately distributed products. Their executable code is not included in this plugin, is not downloaded by this plugin, and no built-in feature is locked behind an upgrade. Updates Evoxup Membership Core and the infrastructure bundled inside it update with the normal WordPress.org plugin update process. Core updates do not require an Evoxup license or membership key. Separately distributed packages follow their own documented distribution/update channel. Entitlement for a commercial external package does not affect the free built-in functionality of Evoxup Membership.

1. Upload the evoxup-membership folder to /wp-content/plugins/, or install the plugin through the WordPress Plugins screen.
2. Activate Evoxup Membership — Membership, Licensing, & Universal Integrations.
3. Open the Evoxup administration menu.
4. Open Customers to use the integrated Member Administration workspace, then create or review your EVO Products and Membership Plans.
5. Configure licensing rules for Products that use EVO licensing.
6. Optionally map WooCommerce products to EVO Products.
7. Optionally configure verified external providers/webhooks under Integrations.
8. Open Extensions & Add-ons to enable bundled Lite modules or view informational PRO / SUPER STAR add-on cards.

No paid key is required to use the functionality included in this plugin.

1.8.5

• Merged Evoxup Member Administration 1.1.0 into the WordPress.org Core package as an integrated Customers workspace; no separate extension or executable add-on is required.
• Added member profile editing, membership operations, license/activation operations, entitlement view, order context, search/filtering, and private activity notes behind existing Evoxup capabilities and nonces.
• Preserved the public-build account boundary: remote fulfillment does not create WordPress users; the integrated admin workspace links only existing local WordPress accounts.
• Kept WordPress.org-safe distribution: no third-party executable package installer, no premium code bundle, and no license gate for included functionality.

1.8.4

• Added bundled Account Lite, Content Access Lite, Analytics Lite, Social Identity Lite, and System Health Lite modules with local Enable / Disable controls.
• Rebuilt Extensions & Add-ons with a dedicated FREE / PRO / SUPER STAR presentation while keeping premium executable code outside the WordPress.org ZIP.
• Shortened the readme short description to remain within the WordPress.org 150-character limit.
• Standardized current WordPress capability identifiers on the evomembers_ prefix.

1.8.3

• Restored a visible optional Support / Donate link inside Evoxup administration pages and in the WordPress.org readme.
• Donations remain completely optional and do not unlock or restrict any plugin functionality.

1.8.2

• Restored the bundled Marketplace visual interface using WordPress enqueue APIs after the WordPress.org compliance refactor.
• Kept Marketplace as a catalog/entitlement interface for separately distributed packages without restoring runtime executable-package installation.
• Updated the public product identity to Evoxup Membership — Membership, Licensing, & Universal Integrations and refreshed WordPress.org-facing documentation.

1.8.1

• Completed the main WordPress.org compliance pass for remote fulfillment, executable-package handling, script loading, audit sanitization, and external-service disclosure.
• Verified webhooks continue to create/update EVO member, membership, entitlement, order, and license records but no longer create WordPress users remotely.
• Removed Core-managed runtime install/update/rollback/uninstall of executable third-party add-ons and legacy custom executable storage paths.

1.8.0

• Clarified that every built-in Evoxup Membership function is free and that Core updates use the normal WordPress.org updater.
• Defined the boundary between free built-in functionality and separately distributed commercial packages/services.
• Clarified WooCommerce fulfillment, verified webhook integration, and free/external package access policy.

1.7.9

• Fixed managed update filesystem initialization and moved temporary update/rollback staging into WordPress-managed upgrade storage.
• Preserved signed download verification, post-update identity/version checks, restore points, and automatic rollback behavior for the pre-compliance update architecture.

1.7.8

• Resolved the remaining Plugin Check input-sanitization findings in local extensions administration requests.
• No membership, entitlement, Repository, or product-model behavior changed in this maintenance release.

1.7.7

• Completed a broad WordPress.org remediation pass covering escaping, sanitization, nonce handling, translator comments, filesystem helpers, and rollback-storage location.
• Removed obsolete Remote Runtime/generated Cloud Proxy customer execution paths while preserving the membership/licensing model and Repository entitlement behavior.