Evoxup Membership — Membership, Licensing, & Universal Integrations

Description

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.
• 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.4 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.

External Services

Evoxup Membership works locally without connecting to Evoxup or any paid service. It does not contact external servers automatically. Network requests occur only after a site administrator explicitly configures an external API/provider or follows a link to Evoxup.com.

Administrator-configured external API

An administrator may optionally enter an HTTPS external API base URL and credentials in Settings. When External or Hybrid API mode is selected, Evoxup Membership can send server-to-server HTTPS requests to that administrator-supplied endpoint. Plain HTTP endpoints are rejected.

Data sent can include the configured client ID, encrypted-at-rest service credential after decryption for transport, request correlation ID, node identifier, license key, product identifier, site URL/domain, client version, and other fields required by the requested licensing operation. These requests occur only after the administrator saves and enables that external configuration.

Because the destination is supplied by the site administrator, its operator, Terms of Use, and Privacy Policy depend on the selected service. The administrator is responsible for reviewing those policies before enabling the connection.

Configured external commerce providers

Administrators may configure authenticated webhook integrations for purchase fulfillment. Inbound events can contain provider order/product identifiers, customer/order information required for fulfillment, event status, timestamps, and authentication metadata. Unsigned webhook delivery is rejected unless a provider-specific verifier explicitly authenticates it.

If a configured provider requires outbound API requests, only the data required by that integration is sent after the administrator enables it. The site owner should review the provider’s Terms of Use and Privacy Policy before configuration.

Evoxup.com links

The plugin administration screens can contain optional links to https://evoxup.com/evo-membership and https://evoxup.com/donate/. Following these links is a normal browser navigation initiated by the administrator; the plugin does not send site/customer/license data to Evoxup.com in the background.

WooCommerce

WooCommerce integration is local to the WordPress installation unless the site owner separately configures WooCommerce or another service to communicate externally. Evoxup Membership does not require an external Evoxup service merely to process a local WooCommerce order.

Support Evoxup

Evoxup Membership is free software. If the plugin is useful to you and you would like to support continued development, you can make an optional one-time contribution.

Donate: https://evoxup.com/donate/

Donations are optional and do not unlock features, licenses, memberships, updates, support tiers, or any functionality included in the WordPress.org plugin.