內容簡介
eew Subscriptions Lite 讓您能夠直接在 WordPress 上銷售定期訂閱，支援 Stripe 和/或 PayPal，無需 WooCommerce，簡化了流程並減少了不必要的負擔。
【主要功能】
• 支援無限產品的訂閱表單
• 客戶管理訂閱的控制面板
• Gutenberg 區塊：訂閱表單和管理訂閱
• 來賓結帳，自動創建 WP 帳號
• 支援保存的付款方式的回頭客
• Webhook 處理訂閱生命周期和發票事件
外掛標籤
開發者團隊
原文外掛簡介
eew Subscriptions Lite (the eew stands for East End Web) lets you sell recurring subscriptions directly from WordPress using Stripe and/or PayPal – no WooCommerce, no bloat.
Try the live demo – see the subscription form and gated content in action before you install anything. The demo page also shows the content restriction and one-time payment blocks, which need the full version (see below) – each block is labelled with which edition provides it.
Features:
Subscription form with unlimited products via [eew_sub_lite_subscription_form]
Customer manage subscriptions dashboard via [eew_sub_lite_manage_subscriptions]
Gutenberg blocks: Subscription Form (Lite) and Manage Subscriptions (Lite)
Guest checkout – WP accounts created automatically on first payment
Supports returning customers with saved payment methods
Webhook handling for subscription lifecycle and invoice events
Compatible with any WordPress theme
Requirements:
A Stripe account and/or a PayPal REST app – at least one payment vendor must be configured
Stripe: publishable key, secret key and webhook secret. PayPal: Client ID, Client Secret and Webhook ID. (Both configured in Dashboard nav > EEW Subs Lite)
Upgrade to full version:
The full version of eew Subscriptions adds:
One-off payment forms (Set price / pay what you want)
One-time access passes (a single payment grants time-limited access)
Full-page/by block and file/media content restriction by subscription (via active sub or one time payment pass)
Learn more and purchase at eastendweb.dev
External Services
This plugin connects to the following external services to provide its core functionality. No data is ever sent to the plugin author – all communication is directly between your server/visitors and the payment vendor(s) you configure.
Stripe API (api.stripe.com)
Your server communicates with the Stripe API (via the bundled official Stripe PHP SDK) to create and manage customers, subscriptions, setup intents and payment methods. When a visitor uses the subscription form or the manage-subscriptions dashboard, the following data is sent to Stripe: the customer’s email address and name (where provided), and the identifiers of the products, prices, subscriptions and payment methods involved. Stripe also sends webhook events back to your site to keep subscription statuses in sync.
Additionally, if you click Create Webhook Automatically on the settings page, your server sends your site’s webhook URL to Stripe in order to list, create and delete webhook endpoints in your own Stripe account. Note that this action deletes any existing endpoint registered at that same URL before creating the replacement – Stripe only reveals a webhook signing secret at the moment an endpoint is created, so an existing endpoint cannot be reused. Endpoints at any other URL are never touched. This only happens when you click the button; nothing is sent automatically.
Additionally, when you open the plugin’s settings page, your server asks Stripe to confirm the API key you have saved is valid and to name the connected account (Stripe’s “retrieve account” call). No customer data is involved – only your own saved credentials. The result is cached and re-checked when you save new keys, when you click Re-check, or after the cache expires.
Stripe.js (js.stripe.com)
On pages containing the subscription form or manage-subscriptions shortcode/block, the Stripe.js library is loaded in the visitor’s browser directly from js.stripe.com, as required by Stripe for PCI compliance. Card details are entered into Stripe’s secure Payment Element and are sent directly from the visitor’s browser to Stripe – they never pass through your server.
Stripe services are provided by Stripe, Inc. – Terms of Service, Privacy Policy.
PayPal API (api-m.paypal.com, or api-m.sandbox.paypal.com in Sandbox mode)
If you enable PayPal as a payment vendor (Settings > Enabled Payment Vendors), your server communicates with the PayPal REST API to obtain an access token, create, look up and cancel subscriptions, look up billing plans, and verify the signature of incoming PayPal webhooks. When a visitor uses the subscription form with PayPal selected, the following data is sent to PayPal: the customer’s email address and name (where provided), and the identifiers of the plans and subscriptions involved. PayPal also sends webhook events back to your site to keep subscription statuses in sync. This only happens if you configure PayPal credentials in the plugin settings – a Stripe-only site never contacts PayPal. The Sandbox/Live environment setting determines which of the two hosts is used.
Additionally, if you click Create Webhook Automatically on the settings page, your server sends your site’s webhook URL to PayPal in order to list and create webhooks in your own PayPal app. Unlike Stripe, an existing matching webhook is reused rather than replaced, so nothing is deleted. This only happens when you click the button; nothing is sent automatically.
Additionally, when you open the plugin’s settings page, your server requests a PayPal access token to confirm the Client ID and Client Secret you have saved are valid. No customer data is involved – only your own saved credentials. The result is cached and re-checked when you save new credentials, when you click Re-check, or after the cache expires.
PayPal JS SDK (paypal.com)
On pages containing the subscription form, if PayPal is configured and selected as the payment method, the PayPal JS SDK is loaded in the visitor’s browser directly from paypal.com to render the PayPal payment button and complete checkout.
PayPal services are provided by PayPal, Inc. – Terms of Service, Privacy Policy.
