preloader

WP Simple Pay plugin review and common issues

WP Simple Pay is used for selling products, handling checkout, and managing orders inside WordPress. In most cases, it fits business sites better than a custom build done too early. A common issue is that checkout, tax, shipping, or gateway conflicts. This usually happens when cart and checkout break when caching or scripts are misconfigured. It can save time, but it still needs testing on a staging site before major changes go live. From experience, WP Simple Pay works best when you keep the setup focused and avoid overlapping plugins.

WP Simple Pay plugin review and common issues

What is WP Simple Pay plugin?

WP Simple Pay is a WordPress plugin built specifically for accepting Stripe payments without setting up a full ecommerce system. You do not need WooCommerce or a shopping cart — you create a payment form, embed it on any page, and start collecting payments directly through Stripe. It is the most direct path from “I want to take a Stripe payment on my WordPress site” to a working form.

The free version (Lite) handles one-time payments via Stripe Checkout and includes a basic form builder. The 3% per-transaction fee on Lite is waived entirely when you upgrade to Pro, which is the most important pricing detail. Pro unlocks recurring subscriptions, custom amounts, coupon codes, tax rate collection, ACH direct debit, Buy Now Pay Later via Klarna and Afterpay, installment plans, free trials, setup fees, and processing fee recovery — the ability to pass Stripe’s transaction fee back to the customer.

The plugin recently added a full Form Style editor in version 4.17.0, so you can customize payment form appearance — colors, typography, border radius — without writing CSS. It also includes 70+ pre-built form templates, dedicated payment landing pages you can create inside the plugin without building a WordPress page, and integrations with tools like Zapier and other automation platforms.

WP Simple Pay is a Stripe partner, which means it stays current with Stripe’s API changes and supports the full Stripe payment method ecosystem — Apple Pay, Google Pay, iDEAL, SEPA, Sofort, and more. Its main limitation is the Stripe exclusivity: if you need PayPal, you need a different solution. For anyone committed to Stripe who wants simple, reliable payment forms without an ecommerce platform, it is one of the best-maintained options in WordPress.

Need Help With WP Simple Pay Setup, Troubleshooting, or Customization?

Need help with WP Simple Pay? Whether you are dealing with errors, broken functionality, styling problems, plugin conflicts, or advanced customization, we can help you fix the issue and get the plugin working properly on your WordPress site.

Get WP Simple Pay Expert Help

Key Features

  • Drag-and-drop Stripe payment form builder
  • One-time and recurring subscription payments
  • Custom amount and user-entered amounts (Pro)
  • ACH direct debit and SEPA (Pro)
  • Buy Now Pay Later via Klarna and Afterpay (Pro)

Pros & Cons

Pros

  • Cleanest Stripe integration available for WordPress without WooCommerce
  • Stripe partner with full payment method ecosystem support
  • Form Style editor means no CSS needed for branding

Cons

  • Stripe-only — no PayPal or other gateway support
  • Free Lite version charges a 3% platform fee per transaction

Free vs Premium

The free Lite version accepts one-time Stripe payments but adds a 3% platform fee on top of Stripe’s gateway fees. Pro removes that fee entirely and adds subscriptions, custom amounts, coupons, tax rates, ACH, Buy Now Pay Later, installment plans, fee recovery, and more. Pro starts at $49.50/year for a single site. For businesses processing meaningful volume, the fee savings on Pro typically justify the cost within months.

Common Problems & Fixes

Why is my WP Simple Pay payment form showing a nonce or REST API error?

The “rest_cookie_invalid_nonce” error almost always comes from page caching. WP Simple Pay uses WordPress REST API nonces that expire after 12 hours. If your cache is serving a page with an expired nonce, the payment form fails to load correctly. Either set your cache TTL to under 12 hours or exclude your payment pages from caching entirely. WP Simple Pay automatically sets DONOTCACHEPAGE on success and failure confirmation pages, so most caching plugins handle those pages correctly — the issue is usually with the form page itself.

Why is my WP Simple Pay form getting a 403 or 406 error?

A 403 or 406 error on payment form submissions is almost always a server firewall or ModSecurity rule blocking the request. WP Simple Pay’s payment requests can trip ModSecurity rules that flag payment-related POST requests as suspicious. Contact your hosting provider and ask them to review ModSecurity logs for blocked requests from your site and whitelist WP Simple Pay’s form endpoint.

Why are WP Simple Pay subscriptions not renewing?

WP Simple Pay subscriptions are managed entirely by Stripe — renewals are charged by Stripe directly, not through WP-Cron. If renewals are failing, check Stripe dashboard events for the specific failure reason. Common causes are expired cards, payment method issues, or failed webhook delivery. Verify that your Stripe webhook endpoint in WP Simple Pay Settings → Stripe Setup is correct and that Stripe can reach it successfully.

Customization & Developer Notes

How do I change the look of my WP Simple Pay payment form?

Since version 4.17.0, WP Simple Pay includes a Form Style editor in the form builder (the Style tab). You can set form colors, button colors, typography, and border radius using a visual interface without writing CSS. For changes beyond what the style editor covers, you can add custom CSS targeting the form’s container classes in your theme or child theme.

Can I add custom fields to a WP Simple Pay payment form?

Yes. The form builder includes a Custom Fields section where you can add text inputs, dropdowns, checkboxes, radio buttons, and number fields. These fields collect additional data from the payer and attach it to the payment record in Stripe metadata and in WP Simple Pay’s payment log. Pro users can also use Smart Tags to reference custom field values in confirmation messages and notification emails.

Frequently Asked Questions

Does WP Simple Pay work without WooCommerce?

Yes. WP Simple Pay is completely independent of WooCommerce. It is designed for sites that want payment forms without a full ecommerce setup. If you need product catalogs, inventory management, or shipping, WooCommerce is more appropriate.

Does WP Simple Pay support PayPal?

No. WP Simple Pay processes payments exclusively through Stripe. If you need PayPal support, you need a different plugin — WPForms with its PayPal addon, or a WooCommerce setup with the PayPal gateway.

Can I use WP Simple Pay for donations?

Yes. The custom amount field lets donors enter any amount they choose, and the optional recurring toggle lets donors set up automatic monthly donations. This makes WP Simple Pay a clean solution for nonprofits and fundraising sites that do not need a full donation management platform.

What is the WP Simple Pay processing fee recovery feature?

Pro users can enable a setting that adds Stripe’s transaction fee (typically 2.9% + $0.30) to the payment total, presenting it to the customer as an optional or mandatory surcharge. This means you receive the full amount you intend to collect without absorbing Stripe’s fee. The feature is commonly used by nonprofits and service businesses that want full control over their net receipts.

Need a WP Simple Pay Developer?

Find a vetted WordPress developer specializing in WP Simple Pay. From setup and configuration to custom WP Simple Pay development — get expert help on WPWizzy.
Get a Free Estimate

Ready to hire your WordPress developer?

WPWizzy connects you with vetted freelance WordPress developers from the Codeable network — the top 2% of WordPress experts worldwide, , you can get a free no-obligation project estimate before hiring. Every developer is carefully screened, backed by Codeable’s satisfaction guarantee, and rated by real clients based on completed WordPress projects.

Pick one option and we’ll take you to the right next step.

After submitting your request, up to three WordPress developers may review your project and ask a few questions to better understand the issue.
This step helps us define the scope of work and provide an accurate estimate. Most projects receive a response within 24 hours.
Providing a few key details about your website or the problem will help us respond faster. There is no obligation to proceed with the project.