Prototypux SaaS Engine
| 开发者 | tiagoferreiradesign |
|---|---|
| 更新时间 | 2026年7月31日 23:35 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Plans as a custom post type: type (free/paid), monthly and/or yearly price, managed role, publishing quotas, fallback plan, and a manual features list for the pricing table.
- Quotas on as many content types as you need — pick them once in Settings, then give every plan its own limit for each (posts, listings, a custom post type, or all of them).
- Freemium without trials: a permanent free plan is assigned automatically on registration (by any form or builder). Upgrades go through Stripe.
- Hosted Stripe Checkout & Customer Portal — cards never touch your site (PCI SAQ-A). No embedded SDK: a thin HTTP client with a pinned API version and signed webhooks.
- Activation by webhook only — access is never granted on the checkout redirect, so a closed browser tab never leaves a customer half-subscribed.
- Server-side quota enforcement — publishing limits are enforced in the REST API and on post insert, not just hidden in the UI. Quota = items published (or scheduled) at once; deleting one frees a slot.
- A static checkout URL you can paste into any button, menu or email, plus a Customer Portal link.
- Account components as shortcodes: pricing table, plan status, usage bars, portal & checkout buttons, plan/quota conditionals, and CSS visibility classes for page builders.
- Manual reconciliation with Stripe (Tools) — the one-click repair for a missed webhook.
- Automatic past-due banner for the affected user, linking to the Customer Portal.
[wpse_pricing]— pricing table with a monthly/yearly toggle and manual feature lists.[wpse_account]— a pre-assembled account page.[wpse_plan_status],[wpse_usage type="post"],[wpse_portal_button],[wpse_checkout_button plan="basic" interval="month"][wpse_if_plan plan="pro,basic"]…[/wpse_if_plan](addnot="1"to invert)[wpse_can_create type="post"]…[/wpse_can_create]and its opposite[wpse_quota_reached type="post"]…[/wpse_quota_reached][wpse_quota_remaining type="post"]and[wpse_quota_message type="post"]
wpse-hide-if-quota-full-{type}— hides the element once the quota is full.wpse-show-if-quota-full-{type}— shows the element only when the quota is full.
wpse-plan-{slug}, wpse-status-{status}, wpse-can-create-{type} / wpse-quota-full-{type} on the body for custom CSS.
Developer API
Public functions (wpse_subscription(), wpse_has_plan(), wpse_quota(), wpse_can_create(), wpse_checkout_url()), actions (wpse_activated, wpse_status_changed, wpse_payment_completed, wpse_downgraded, wpse_quota_reached, wpse_quota_demoted) and filters let you extend everything from your own theme or plugin.
安装:
- Upload the plugin to
/wp-content/plugins/and activate it. - Go to SaaS Engine → Settings and paste your Stripe test keys (secret, publishable).
- Create a webhook endpoint in your Stripe dashboard pointing to the URL shown on the Settings screen, subscribe it to the five listed events, and paste the signing secret.
- Create your plans under SaaS Engine → Plans (mark one free plan as the registration default).
- Add
[wpse_pricing]to a page. Switch Settings to live mode when you are ready to charge real cards.
屏幕截图:
常见问题:
Does it work with my form / page builder?
Yes. Registration is the site's responsibility — any form that creates a user triggers the default free plan. Quota enforcement is server-side, so it protects you no matter how content is created. For builders, the plugin outputs plan and quota CSS classes on the body element, so you can show or hide any element without writing code.
Do I need the Stripe PHP SDK?
No. The plugin talks to the Stripe API directly over the WordPress HTTP API, with a pinned API version and HMAC-verified webhooks. This avoids the fatal conflicts that embedded SDKs cause with other Stripe-using plugins.
A customer paid but their access did not change. What now?
Almost always a missed webhook — check that your Stripe webhook endpoint is subscribed to the five events listed on the Settings screen. To repair it immediately, go to SaaS Engine → Tools → Reconcile now: it checks every subscription against Stripe and fixes the drift with one click.
What happens on a failed payment?
The subscription enters a grace period (configurable) during which access is kept while Stripe retries. If it is not recovered, a cron job downgrades the user to the plan's fallback.
Will deleting a plan break existing subscribers?
No — the plugin blocks deleting a plan that still has active subscribers and points you to archiving it instead (unsellable, but current subscribers keep their conditions).
Does the plugin collect or track any data?
No. The plugin has no analytics, no telemetry and no "phone home" behaviour. It only contacts Stripe, as described in the "External services" section.
更新日志:
- Fixed: the welcome notice shown after activation used an outdated plugin name.
- Initial public release: plans, Stripe billing engine (Checkout, Customer Portal, webhooks, reconciliation), server-side publishing quotas, account components, pricing table, and the static checkout URL.