Rankzaar Subscriptions Manager for Stripe

Rankzaar Subscriptions Manager for Stripe brings your Stripe subscriptions into the WordPress admin and gives you a simple way to sell one-time or recurring services on any page.

js, no card fields on your site: customers pay on the secure, Stripe-hosted Checkout page.

Rankzaar Subscriptions Manager for Stripe is not affiliated with or endorsed by Stripe, Inc.

Manage subscriptions

• Subscription list with search, status tabs, filters (service, next billing date, start date, failed payments) and key numbers: active subscriptions, failed payments, past due, billing this month, canceling, and monthly recurring revenue per currency.

• Subscription page with customer details (name, email, business name, phone), invoices, the reason a payment failed (in plain language, straight from the bank’s decline code) and a full activity history.

• Actions: change plan (with proration choice), pause and resume payments, cancel at the end of the period (and undo), cancel immediately, retry a failed payment, and keep private internal notes. Each action can be turned off.

• Test and live mode with separate keys. Each mode keeps its own data.

• Webhook keeps everything up to date in real time. One click creates the endpoint in Stripe for you. A scheduled background sync catches anything a webhook missed.

Sell services with a shortcode

• Create a service with several price options (for example Basic / Pro / Premium, monthly or yearly). Prices are created in Stripe automatically when you save, or you can paste existing Stripe price IDs.

• Import existing Stripe Payment Links as services in one click.

• Put [smfs_checkout service="your-service"] on any page. Customers pick an option, optionally a quantity, see a live price breakdown, and are sent to Stripe Checkout.

• Optional transaction fee (percentage and/or fixed amount), as a default for all services or per service, charged on every renewal or only on the first payment.

• Coupon codes: create, edit, activate, deactivate and delete Stripe promotion codes from WordPress. Limit them to first-time customers, set a usage limit and an expiry date, and choose whether the fee is discounted.

• Ask for full name, business name and phone number on the checkout page; the details are saved to the Stripe customer.

Email notifications

• Get an email for new subscriptions, payments received, failed payments (with the reason and a link the customer can pay), scheduled cancellations and canceled subscriptions.

• Every email has a ready-made default template. Change the subject and message in Settings → Notifications using placeholders such as {customer_name}, {plan}, {amount} or {failure_reason}, send yourself a test, and reset to the default at any time.

• Optional SMTP settings (with presets for common providers) if your server’s built-in email is unreliable.

Shortcode options

• variant="premium" – show only one option, or variant="basic,premium" for several.

• layout="dropdown" – show the options in a dropdown instead of cards.

• label="Buy now" – button text for this placement.

• breakdown="no" – hide the price line.

• class="my-class" – add CSS classes to the button.

Any element with data-smfs-variant="option-id" (for example a button in a pricing table) selects that option when clicked.

For developers

• Keys can be defined in wp-config.php instead of the database: SMFS_STRIPE_SECRET_KEY, SMFS_STRIPE_WEBHOOK_SECRET and SMFS_SMTP_PASSWORD.

• Filter smfs_checkout_button_classes to add your theme’s button classes to the checkout button.

External services

com ), a payment service provided by Stripe, Inc. It cannot work without it. Requests are made from your server with the secret key you enter; nothing is loaded from Stripe in visitors’ browsers.

Data is sent to Stripe in these situations:

• When a visitor clicks the checkout button: the selected price, quantity, transaction fee, the return URLs of your site and the service/option identifiers are sent to create a Stripe Checkout Session. The visitor is then redirected to Stripe’s hosted checkout page ( checkout.stripe.com ), where they enter their email address, payment details and, if you enabled them, their name, business name and phone number directly with Stripe.

• After a checkout is completed (via the webhook): the customer’s name, business name and phone number collected on the checkout page are saved to the Stripe customer record.

• When an administrator uses the plugin: testing a key, syncing subscriptions, viewing a subscription, creating or editing services (product names, prices, billing intervals), creating coupon codes, creating the webhook endpoint, and subscription actions (change plan, pause, resume, cancel, retry a payment). These requests send the related IDs and values to Stripe and read back subscriptions, customers (email, name, phone, business name), invoices, prices, products, coupons and payment links.

• Background sync (WP-Cron, if enabled): subscription, customer and product data is read from Stripe on the schedule you choose.

Stripe also sends events to your site’s webhook URL ( /wp-json/smfs/v1/webhook ); every request is verified with the Stripe signing secret.

• Stripe Services Agreement and legal terms: https://stripe.com/legal

• Stripe Privacy Policy: https://stripe.com/privacy

If you turn on the optional SMTP feature, all email from your site is sent through the SMTP server you configure (for example your email provider). That provider receives the content and recipients of those emails; its own terms and privacy policy apply.