How to Accept Payments in WordPress Without WooCommerce
The November 3, 2026 WooPayments security update is a reminder that a store is a lot to patch. Simpler ways to accept payments in WordPress, and when WooCommerce still fits.
Do you need WooCommerce to take a payment on a WordPress site? What if all you sell is a consultation, a deposit or a single download? Plenty of sites accept payments in WordPress without WooCommerce, and the WooPayments security update of November 3, 2026 is a good moment to ask whether yours should be one of them.
That update fixed a problem in the subscriptions code bundled with WooPayments, and it shipped patched releases for every WooPayments version line from 9.0 up. WooCommerce asked store owners to check the installed version by hand on every site, staging copies included, even with automatic updates on. That is routine upkeep for a real store. It is a lot of store to look after when the site only sells one service.
Our advice is to match the setup to what you sell. A payment link or a payment form covers services, deposits, registration fees and donations. A digital commerce plugin covers downloads and software licenses. WooCommerce stays the right choice for physical products, stock and shipping.

What the WooPayments Update Fixed
WooCommerce published the security update for WooPayments on its developer blog. These are the facts it gives:
- What it fixes: a security issue in the subscriptions features that ship inside WooPayments.
- Where it comes from: it extends a fix WooCommerce announced in August for WooCommerce Subscriptions. That August release fixed several vulnerabilities, the most serious of which could let an unauthorized user take control of a site. WooCommerce said it had no evidence that any store was compromised.
- Which versions are fixed: a patched release exists for each WooPayments line from 9.0 to 11.2. A store on anything older than 9.0 should move to 11.2.1.
- What store owners should do: check the installed version under Plugins → Installed Plugins, update if the version isn’t a fixed one, and check again afterward. Agencies are asked to check every client site, including public staging and development copies.
The November post names no CVE and no severity, and it says nothing about attacks in progress. If you run WooPayments, the update comes first and the rest of this article can wait.
Why a Smaller Payment Setup Is Easier to Keep Patched
A smaller setup isn’t automatically safer. Any plugin that receives payment webhooks needs updates, and Core Forms ships its own fixes like every other plugin. What changes is how much code sits between your site and the payment, and how many separate products you have to watch.
A WooCommerce store usually runs all of these:
- WooCommerce itself, with its cart, sessions and order tables
- a payment plugin such as WooPayments or the Stripe gateway
- customer accounts with their own login and password reset
- a public REST API for products, orders and customers
- extensions for subscriptions, bookings or memberships, each on its own release schedule
A payment form needs much less: a form, an amount, a call to Stripe or PayPal and a signed webhook that confirms the payment. There is no cart to secure, no customer account to take over and no order API to expose.
The WooPayments update is a good example of where the extra code hides. Plenty of stores using WooPayments never sell a subscription, yet the subscriptions code still ships inside the plugin and still needed the patch. Code you don’t use is still code you have to update.
To be fair to WooCommerce, publishing a fixed release for 23 separate version lines is careful work, and the advisory tells owners exactly what to check. The problem is simply that a store has more to check.
Simpler Ways to Take Payments in WordPress
There are broadly four setups, and the right one depends on what you sell rather than on how big your site is.
| Setup | Fits | What you give up |
|---|---|---|
| Payment links or buttons | One fixed price, tips, a quick deposit | Custom fields and a record inside WordPress |
| Payment form plugin | Services, deposits, registrations, donations, quotes | Cart, stock and shipping |
| Digital commerce plugin | Downloads, software licenses, memberships | Depth for physical shipping |
| WooCommerce | Physical products, large catalogs, shipping and tax | Simplicity and upkeep time |
Payment Links
A payment link is a checkout page the processor hosts for you. Stripe calls them Payment Links, and PayPal offers payment links and buttons. You paste the link on a page and the buyer pays on Stripe’s or PayPal’s site.
No payment code runs on WordPress at all, which makes this the smallest setup there is. The cost is the same as any other payment: Stripe charges its standard 2.9% + 30¢, and PayPal charges 3.49% + 49¢ for PayPal Checkout through a link or 2.99% + 49¢ for a card.
The limit is that the link only knows the price. It can’t collect the project brief, the event date or the shirt size, and the payment lives in the processor’s dashboard instead of next to the rest of your site’s records.
Payment Forms
A payment form collects the details and the money in one step. The buyer fills in the fields, pays through Stripe or PayPal, and the entry is saved in WordPress with its payment status.
Core Forms is our form plugin, and this is the setup it is built for. It takes payments through Stripe, PayPal, Razorpay and Polar. With Stripe the buyer can pay right inside the form or on Stripe’s hosted checkout. A few details matter for keeping the setup tight:
- The server sets the price. The amount comes from the saved form or a calculated field, so a buyer who edits the page can’t change what gets charged.
- The webhook is the proof. A submission stays pending until the processor’s signed webhook confirms the payment, and only then do the emails and other actions run.
- No card data touches WordPress. The card details go straight to Stripe or PayPal.
- No extra fee. Core Forms talks to each processor directly and adds nothing per payment.
Other form plugins take payments too. Gravity Forms has Stripe and PayPal add-ons on its paid plans, and WPForms supports Stripe in its free version but adds a 3% fee per payment until you upgrade. Our Stripe vs PayPal fees comparison shows how much that kind of fee changes the math.
The limit of a payment form is that it sells one thing at a time. There is no cart for buying 5 different products, no stock count and no shipping rates by location.
Digital Commerce Plugins
If you sell downloads, plugins, themes or memberships, a digital commerce plugin gives you a cart, customer accounts and order history without WooCommerce’s physical-goods features. Easy Digital Downloads and FluentCart both run inside WordPress, while SureCart keeps the store on its own hosted platform and connects to WordPress.
Core Forms also sells digital products and issues software licenses from the same plugin as its forms. Our Easy Digital Downloads alternative guide compares that route with a full digital store.
These plugins still need the same upkeep as any store with accounts and orders. They are smaller than WooCommerce because they skip shipping, stock and physical product types.
WooCommerce
WooCommerce is still the right tool when you ship physical products, track stock, charge tax by location or sell a catalog large enough to need categories and filters. None of the setups above replaces that.
If you stay on WooCommerce, the advisory’s own checklist is the one we’d follow: keep a record of the version on every site, check staging copies too, and don’t trust automatic updates until you’ve seen the fixed version installed.
Moving a Simple Store Off WooCommerce
If your store sells 1 to 3 things, a payment form or a payment link will usually do the same job with much less to maintain. This is the order we’d follow for the move:
- A list of what the store actually sells. Anything with no shipping and no stock is a candidate for a form.
- A plan for recurring payments. Saved cards belong to the payment account, not to WordPress, so subscriptions are the hardest part to move. They can keep running on the store until they end or until the payment provider can transfer them.
- An export of the order history. Your tax records still need it after WooCommerce is gone.
- Redirects from the old product URLs to the new form page, so links and search results still land somewhere useful.
- A test payment in test mode, with the webhook connected, before the form goes live.
- Deleting WooCommerce and its payment plugins once the data is exported. A deactivated plugin still sits on the server, and only deleting it removes the code.
Deleting the plugin doesn’t erase your store data by default. WooCommerce only removes its tables and settings on deletion when the WC_REMOVE_ALL_DATA constant is set to true in wp-config.php.
FAQ
Is WooPayments safe to use after the November 3 update?
WooCommerce says a store running a fixed version needs no further action. The safe step is to confirm the installed version on each site against the advisory, because an update that failed or never ran leaves the old code in place.
Can I use Stripe on WordPress without WooCommerce?
Yes. You can paste a Stripe Payment Link on any page, or use a form plugin that connects to Stripe directly. Both charge Stripe’s standard rates, and neither needs a cart.
Do I need to worry about PCI compliance with a payment form?
When the card details are entered on Stripe’s or PayPal’s own fields or hosted checkout, they never reach your server. That keeps most sites in the simplest PCI category, the short self-assessment known as SAQ A.
Does deactivating WooCommerce delete my orders?
No. Deactivating or deleting the plugin keeps the order data in your database unless the WC_REMOVE_ALL_DATA constant is set to true. We’d still export the orders before removing it.
When is a payment form not enough?
When buyers need to put several products in a cart, when you track stock, or when shipping and tax depend on where the buyer lives. Those are store problems, and a store plugin solves them better.
Final Remarks
If you’re unsure whether your site needs a store at all, we’d count the products. One service, one deposit or one download sells perfectly well through a form, and every store plugin you don’t install is one less advisory to check.
When you’re ready to try the form route, Core Forms payments connects Stripe and PayPal to any form with no cart and no fee of its own.