Best WordPress Payment Plugin in 2026: 7 Options and When You Actually Get Paid

The main WordPress payment plugin options are WP Simple Pay for a Stripe button, WooPayments for a WooCommerce store, Paymattic for free payment forms, and Easy Digital Downloads for selling files. They differ less on features than on whose account holds your money first. This comparison reads each route against its payment processor’s own published payout rules.

You install the plugin, connect Stripe, make your first sale, then sit there refreshing your bank app.

I went looking for how long that wait actually is. The guides ranking on page 1 for this term all compare the same things: gateways supported, setup time, licence price. I searched all 4 of them for the phrase “waiting period” and got zero hits on every one.

The longest one tells you to expect same-day deposits.

That is not what the payment companies’ own documentation says. So this post reads the payout rules for each route instead of the feature lists. Whose account your money sits in first, how many days before it moves, what the fast option costs, and which of these plugins takes a slice of every sale before the money even gets that far.

Key Takeaways

• The wait on your first sales comes from the gateway, not the plugin. Stripe publishes 7 to 14 days for a new account’s first payout, and PayPal holds a new seller’s initial payments for up to 21 days.
• WooPayments writes its own version of that rule. A new account waits 7 days before its first payout, and WooCommerce says that delay cannot be waived under any circumstances.
• Same-day money is a paid feature with a gate on it. WooPayments instant payouts cost an extra 1.5%, and need a US account over 90 days old that has processed more than $1,000.
• Free plugins are rarely free per sale. WP Simple Pay Lite and the free Easy Digital Downloads each add 3% on top of Stripe. SureCart’s free plan adds 2.9%. Paymattic adds nothing.
• A subscription order costs WooPayments users an extra 1%, and that 1% applies to the whole order rather than just the subscription line.

The WordPress payment plugins worth a shortlist

No single WordPress payment plugin wins this category, because these tools answer 3 different questions. Some add a payment method to a cart you already run. Some are a payment button with no cart at all. Some are the whole shop.

If margin is what brought you here, the free 5-day Online Selling Mistakes Challenge covers the 5 leaks that cost solo sellers the most, and fees are only 1 of them.

What separates these plugins once you get past the feature list is simpler, and it is the thing almost nobody publishes: which account your money lands in, and whether the plugin takes a slice before you see it.

4 of the 7 routes below add nothing of their own on top of your payment processor’s rate, and 3 of them add a percentage: WP Simple Pay Lite and the free Easy Digital Downloads each add 3%, and WPForms adds 3% for as long as its licence is inactive.

I built CartMango, which is why it is in the table at all, and it is the odd row there. CartMango is a hosted checkout you link to from a WordPress page, so it never appears in your plugins list and it will not run a shop with stock and shipping. It earns a row because the column this table is really about, where the money lands, is the one thing CartMango handles the same way as the free plugin options.

3 things worth knowing before you read that table as a ranking.

SureCart is missing from it on purpose. Its free Launch plan is a real option, at $0 plus a 2.9% cut, with Pro at $199 a year or $699 once. It sits closer to a full store than to a payment button, and our WordPress ecommerce plugin comparison already works through what its cut does to a growing shop.

The licence prices in that last column are first-year prices. WP Simple Pay, WPForms and Easy Digital Downloads all print the same footnote under their pricing tables: renewals are at full price. So $49.50 becomes $99, $59.40 becomes $99, and $199.50 becomes $399.

And Easy Digital Downloads is the one that catches people, because its 3% survives the cheapest paid plan. The Personal tier at $99.50 is the only one of its 4 whose feature list leaves out the words “no platform fees”, and the fee itself is documented over in the Stripe setup docs rather than on the pricing page. We covered that trap in full in the ecommerce plugin post above.

A payment plugin and a payment gateway are 2 different things

The plugin and the gateway are 2 separate companies doing 2 separate jobs, and most of what follows on this page turns on the difference.

A payment plugin is the WordPress side. It draws the form, validates the card field, records the order and tells your site a payment happened. A payment gateway is the company behind it: Stripe, PayPal, Square, Authorize.Net. The gateway moves the money, holds it, and decides when you get it.

So when a payout is late, the plugin is almost never the reason. Swapping WP Simple Pay for WPForms changes nothing about when Stripe pays you, because both are talking to the same Stripe.

Stripe and PayPal cover most of this category, and 2 other gateways come up often enough to name. For Square, the roundups point at WP EasyPay and MyPayKit, and MyPayKit’s free version runs the same model as the plugins above, a 3% platform fee that a $49.50 licence removes. For crypto, they point at MyCryptoCheckout, listed at 0% of its own across more than 100 coins. SureCart adds Mollie, Paystack and Razorpay for sellers outside the US and Europe.

A wrinkle worth knowing, because it is where new sellers quietly lose a sale. The gateway tells your site the payment went through using a webhook, a small message sent from Stripe back to your site. If that message does not arrive, the payment still succeeded and took the customer’s money, and your site never marks the order paid or sends the file. Test it before launch, because a silently broken webhook looks exactly like a customer who never bought.

Whose account does the money land in first?

Most of these plugins never touch your money. They hand the card details to Stripe or PayPal, and the payment lands in an account you opened, in your name, that you can log into without WordPress.

WP Simple Pay describes itself on its WordPress.org listing as “a standalone Stripe payments plugin that connects Stripe with WordPress”. WPForms, Paymattic, Easy Digital Downloads and the official WooCommerce Stripe gateway all work the same way. You connect your Stripe account, and Stripe pays you.

WooPayments is built differently, and its own listing says so. When you sign up, “your personal and business information is verified with Stripe and stored in an account connected to the WooPayments service”. Its payout documentation is blunter: money you make “must flow through your WooPayments account balance before it’s paid out into your bank account”.

That is not a scandal. Plenty of good products work that way, and it buys you a single dashboard where refunds, disputes and payouts all live in one place. But it does change who decides when you get paid, and it changes what happens on the day something goes wrong.

A seller posted on r/woocommerce about launching a new site and taking a first payment of 800 euros through WooPayments. They were told the account had to be at least 7 days old before payouts could be enabled, so they waited it out.

Then payouts were suspended anyway, while support asked to see a transaction history first. Their reply gets at the real problem: how do you build a transaction history when your first transactions are the thing being held?

It ended badly for that seller. The account was closed, and the support email they posted says the balance goes “in reserve for the next 120 days”, which the email calls “the industry-standard period in which most payments are disputed”. The same email confirms the account structure in passing, closing both “your WooPayments account and the associated Stripe Express account”.

That is the worst case and not the normal one. The seller was told their business carried an elevated dispute risk, which most sellers never trigger. It is worth reading anyway, because it shows what the middle layer is for and who is holding the balance when a decision gets made about you.

With your own Stripe account, that conversation is between you and Stripe. With a managed balance, there is a company in between.

When you actually get your first payment

A brand-new WordPress store waits somewhere between 7 and 21 days for its first payout, and which plugin you installed does not change that. The number belongs to the gateway.

Stripe’s own payout documentation says the first payout on a brand-new account is scheduled “to complete within 7 to 14 days”, and adds that it “can take longer depending on your industry, country of operation, and risk level”. That applies to your own Stripe account. It has nothing to do with which WordPress plugin sent the payment.

PayPal is stricter again, and says so on its own help page for new sellers: “we hold the initial payments you receive for up to 21 days”, which it calls “a common industry practice to cover any potential buyer complaints”. PayPal reviews accounts monthly and releases the brake once you have built a selling history and confirmed your identity.

So the wait applies on all 3 gateways behind every plugin in this post. It is a payment processor rule, and no plugin removes it.

WooPayments then writes its own version of the same rule, in plain language, on a page most people never open.

WooCommerce’s own payout documentation. Read the first line, and then the worked example at the bottom.

The wording is “the first payout for all new accounts is sent after a 7 day waiting period”, and that this delay “cannot be waived under any circumstances”. After the 7 days, a pending period starts on top: 2 business days in the US and Australia, 3 in most other countries, 4 in Japan and New Zealand, 5 in the UAE, and 7 calendar days in Hong Kong and Singapore.

WooCommerce then does the arithmetic for you, which is generous of them and slightly alarming to read. A new US merchant who opens the account on Monday and makes a first sale on Wednesday gets that money in the bank “the following Friday”.

Add the pending period to the 7 days and WooPayments runs 9 days in the US and 14 in Hong Kong and Singapore, which sits inside Stripe’s published 7 to 14 rather than beating it, while PayPal is the longest of the 3 at up to 21 days.

That surprised me. I went into this expecting the plugin to be the villain, and WooPayments lands inside the same window its own processor already uses.

So why does none of this reach a buyer before they choose?

I searched all 4 guides ranking for this term. “Waiting period” returns zero hits on every one of them. So does “7 day”, and so does “business days”.

The longest guide on page 1 goes the other way and tells readers to expect “same-day deposits in supported regions” from WooPayments.

Just 1 of the 4 raises the subject at all. It says Stripe “occasionally holds funds during their review process”, adds that this is “rare but it happens”, and warns separately that PayPal has “a reputation for occasionally freezing accounts”. Both true. Both framed as bad luck that might land on you.

A first-payout hold is a different animal. It is the documented default for a new account on all 3 gateways, each one publishes a number for it, and a new seller meets it by design rather than by bad luck. A reader who hits it after reading that page will assume something has gone wrong with their account, because a rare review is the only version of a payout delay anybody described to them.

Same-day deposits do exist. They are just not what a new seller gets, and the next section is what they cost when you finally qualify.

What same-day money actually costs

WooPayments does offer instant payouts, and the money arrives “within minutes instead of days”. 4 things have to be true first, and they are listed on WooCommerce’s instant payouts page.

Your account has to be based in the US. It has to be more than 90 days old. It has to have processed more than $1,000 in the last 90 days. And fewer than 1% of your transactions can have been disputed in that time.

Then it costs 1.5% of the payout on top of everything else you already paid.

There are limits inside the limits, too. The minimum instant payout is $50, the maximum is $1,000, and you can only request one every 24 hours. So a seller with a $3,000 week cannot pull it out in one go.

WooCommerce also notes that taking part in optional features like this one “is at the sole discretion of the WooCommerce team”. That sentence matters if fast access to cash is the reason you were leaning toward this plugin.

For a brand-new store, none of it applies. You are 90 days and $1,000 away from being allowed to pay 1.5% for something the guide told you was standard.

The extra 1% nobody mentions on subscriptions

WooPayments charges an extra 1.00% on any order that contains a subscription payment, and the WooPayments fee schedule is the only place it is written down.

Start with the rest of that schedule, because the 1% sits on top of it. The US card rate is 2.90% plus $0.30, international cards add 1.50%, and currency conversion adds another 1.00%. A dispute costs $15.

And then: an extra 1.00% on any order containing a subscription payment, whether that is the first payment or a renewal, when the subscription runs on the Stripe Billing engine. WooCommerce’s own wording is blunt: “this fee applies to the entire order, not just the subscription line item”.

So a $60 order with a $9 membership tucked into it is charged the extra 1% on all $60, not on the $9.

If you sell memberships or a recurring product through WooCommerce, that is worth putting in a spreadsheet before you commit. Our breakdown of PayPal’s fees for sellers does the same exercise for the other processor most WordPress sellers end up running alongside Stripe.

How do I add a payment option in WordPress?

WordPress core has no payment feature at all. Everything below is the plugin doing the work.

1. Decide whether you need a cart. Selling a single product, taking a deposit, or invoicing a client? You need a button. Selling 40 things with variations and a basket? You need a cart. This one decision removes most of the plugin list, and our guide to adding a shopping cart to a website walks through the 4 ways to do it if you are torn.

2. Open a Stripe or PayPal account first, in your own name. Do this before you install anything. It takes longer than the plugin does, and it is the account your money will actually live in.

3. Install the plugin that matches step 1. A button goes to WP Simple Pay, WPForms or Paymattic. A shop goes to WooCommerce, Easy Digital Downloads or SureCart. Digital files belong on Easy Digital Downloads, and our WooCommerce digital downloads guide covers what that setup costs on the WooCommerce side.

4. Connect the account, then run a real test purchase. Not the plugin’s test mode. A live payment of $1 on your own card, refunded afterwards. Test mode confirms the plugin works. A real payment confirms your Stripe account is actually activated, which is a different question and the one that bites.

5. Check the payout page before you launch anything. Find the payout schedule inside Stripe or inside the plugin’s dashboard, and write down the date the first payment will land. If that date does not work for your cash flow, you want to know now and not in launch week.

Step 5 is the one that gets skipped. Every other step on this list can be redone in an afternoon. That one costs you nothing to check now and cannot be undone in launch week.

Is there a PayPal payment plugin for WordPress?

Yes, and more than one, though the good options depend on which route you picked above.

WooCommerce has an official PayPal Payments extension, and that is the standard answer for a Woo store. WPForms and Paymattic both take PayPal on their payment forms.

Easy Digital Downloads supports PayPal too, and it carries a detail worth having. EDD’s own documentation confirms its 3% fee “only applies to transactions processed through Stripe when using the free version”, so PayPal escapes it. If you were running EDD’s free version anyway, routing through PayPal quietly saves you that 3%.

WP Simple Pay is the exception. Its own listing says it connects to Stripe and only Stripe, so PayPal is not an option there.

Worth weighing if PayPal is your main gateway: the first-sales hold runs up to 21 days, per PayPal’s own new-seller page, which is longer than either Stripe route. Once that clears, the money sits in a PayPal balance you can move whenever you like. Our PayPal fee breakdown for sellers has the rates alongside it.

Which one fits what you are selling

Pick the WordPress payment plugin that matches what you are selling this month, not the one that covers everything you might sell one day.

I used to be the person who planned everything a long way in advance, running through all the things that could go wrong before any of them had happened. I have moved most of the way to the opposite habit now, preparing things just in time. Back when I was doing sales calls I would build the slides days ahead. Now I put them together the morning of the call, and if the phone is not ringing there is nothing to prepare for.

That habit maps onto plugins better than it has any right to. A shop plugin installed for the 40 products you might list next year is a plugin you update, patch and debug all year for the 3 things you actually sell today.

So, by what you sell:

1 digital file, or a handful. A payment button. WP Simple Pay Lite or Paymattic’s free version, and Paymattic is the one that takes no cut. You will need to handle file delivery separately, which is the honest downside of the button route, and our roundup of digital delivery systems covers what fills that gap.

A service, a deposit or an invoice. WPForms or Paymattic, on a form. The form collects the details you need alongside the payment, which a checkout page will not do.

Digital products as a real business. Easy Digital Downloads, which is built for it. Budget the Extended pass rather than Personal, because Personal leaves the 3% running. If that number puts you off, our Easy Digital Downloads alternatives piece lays out what else covers the same job.

Physical stock, shipping, tax by region. WooCommerce, and then a gateway on top. Which gateway matters less than most guides suggest, though the WooCommerce checkout plugin you pair with it changes the buying experience more than the gateway does.

Courses and memberships. A different category of plugin again, and the fee stacking gets worse rather than better. Our WordPress LMS plugin comparison has the numbers.

Anything where you want affiliates selling for you. Also its own category, covered in the WordPress affiliate plugin breakdown, and worth reading before you pick a cart rather than after.

WordPress payment plugin FAQ

Can WordPress handle payments?

Not on its own. WordPress core ships with no payment feature, no checkout and no connection to a card processor. Every payment on a WordPress site is a plugin doing the work, and that plugin connects to a processor like Stripe or PayPal.

The processor holds the money and pays it to your bank. WordPress only draws the form.

How much do WooPayments cost?

The plugin is free. The processing is 2.90% plus $0.30 on a US card, with 1.50% added for an international card and 1.00% for currency conversion. A disputed payment costs $15.

Orders containing a subscription payment carry an extra 1.00% applied to the whole order, and instant payouts cost a further 1.5% once you qualify.

Which WordPress payment plugin is free with no transaction fee?

Paymattic’s plugin listing answers this outright: it “doesn’t charge any transaction fees or percentages”. Neither WooCommerce core nor the official Stripe gateway lists a cut of its own either. WP Simple Pay Lite, the free Easy Digital Downloads and SureCart’s free Launch plan all add a percentage of their own on top of the processor’s rate.

Do I need WooCommerce to take payments on WordPress?

No, and installing it anyway is a common waste. WooCommerce is a shop: products, cart, orders, stock, shipping, tax. If you are selling a single product or taking a payment for a service, a payment form or button does the job with a fraction of the setup and much less to maintain.

How long before the money reaches my bank account?

On a new account, expect 7 to 21 days before the first payout, whichever plugin you installed. Stripe schedules a new account’s first payout within 7 to 14 days. WooPayments holds new accounts for 7 days and then applies a pending period on top. After the first one, payouts settle into whatever schedule you choose, usually daily or weekly.

Can I use 2 payment plugins at once?

Technically yes, and it is usually a mistake. 2 plugins means 2 sets of records, 2 places refunds can happen and 2 dashboards to reconcile at tax time. The common exception is running a card gateway alongside a PayPal one inside the same cart, which is 1 system rather than 2.

If the payment does not have to live on your site

Every WordPress payment plugin above assumes the payment happens on your own site, so a plugin has to run it, and the plugin’s rules become your rules.

That assumption is worth testing. If you sell digital products, the site is where people read about the thing and the checkout is a separate job that happens to be bolted onto it. A hosted checkout takes the payment on its own page and leaves your WordPress install as a website again, with no checkout left to maintain.

That is what CartMango does. The money goes straight to your own Stripe or PayPal account, exactly like the free plugin routes in the table above, and CartMango takes no commission on top.

CartMango includes order bumps on every plan, so a buyer can add a second item at the moment they pay. CartMango is free while the beta runs until October 2026, and then starts at $10 a year, which is a year rather than a month. If you have no site at all, CartMango’s Mini Pages builds and hosts the sales page too.

The honest limits: CartMango does not host courses or run a community yet, with both planned for October 2026, and affiliate management planned for September 2026. CartMango is built for digital products, so a shop with stock and shipping still belongs on WooCommerce with a WordPress payment plugin behind it.

About the Author

👋 I’m Welly, founder of CartMango (the site you’re on), a checkout platform for digital product sellers. We’ve previously processed $179M+. I also run BirdSend (email marketing tool, 3.1B+ emails sent). On the side I show other non-techie digital sellers how I use AI workflows to automate 50%+ of my operations. Find me on LinkedIn.

Related Reading

• WordPress ecommerce plugin comparison: year 2 licence costs and the percentage most of them take on the cheapest plan
• WooCommerce checkout plugin options: what actually changes the checkout experience, and what does not
• How much does PayPal charge: the fee math for the other processor most WordPress sellers run
• SureCart alternatives: for readers weighing a full WordPress store plugin against a hosted checkout