The Real Cost of Stripe on WordPress: Plugin Fees and Break-Even Calculator

Using a free Stripe plugin is reminiscent of adopting a free puppy – the initial adoption fee is nothing, but the ongoing expenses reveal the real commitment. Here, the ongoing cost is a minor percentage deducted from each payment you process, which can eventually surpass the cost of purchasing a dedicated solution outright.

This article elucidates the costs associated with Stripe payments on WordPress, dissecting the expenses step by step. Additionally, it offers a concise formula along with a worksheet to assist you in determining your personal break-even point. No spreadsheets needed, and the entire process can be completed in roughly five minutes.

Understanding the Two Levels of Costs (Only One is Optional)

Each Stripe payment on your WordPress site involves two levels of costs:

• Level 1: Processing Fee by Stripe. For online transactions with US domestic cards, Stripe typically charges a fee of 2.9% plus 30¢ for each successful transaction. Other fees may apply for different cases, such as international cards or currency conversions. This layer is non-negotiable and can’t be waived; extra monthly or setup charges may also apply. ^[1]
• Level 2: The Plugin Fee. This layer is completely up to you. Some methods impose no fees, others charge between 3% to 5%, and some operate on a flat annual licensing model.

Since Level 1 remains constant across the board, your decisions hinge solely on Level 2. Here’s how popular options stack up:

A quick note on Level 1: the fixed 30¢ fee means that smaller payments incur a relatively higher percentage cost compared to larger sums. For instance, a $10 donation can result in about 5.9% being deducted in Stripe fees, whereas a $100 invoice incurs around 3.2%. What you select in Level 2 can modify these costs if you’re collecting many small payments, so consider your typical payment size rather than solely focusing on the 2.9% headline rate.

The first option serves as a surprising twist: if a hosted checkout page fits your needs, you’ll completely eliminate the plugin fee dilemma. The continuation of this guide focuses on scenarios where an embedded form is essential, making Level 2 worth discussing. (As a quick note, WPFullPay belongs to the ThemeIsle family, just like this blog.)

The Key Formula that Clarifies Costs

Break-even volume = license price ÷ plugin fee rate. If you earn less than this annually, the free tier is more beneficial. Earn more, and the license pays off.

Substituting the actual figures gives you two critical thresholds to remember:

• WPFullPay: €79.50 ÷ 5% = €1,590 annually at the introductory rate, or €159 ÷ 5% = €3,180 at renewal pricing. ^[2]
• WP Simple Pay: $49.50 ÷ 3% = $1,650 annually introductory, or $99 ÷ 3% = $3,300 upon renewal. The vendor consistently showcases the same $1,650 example on their comparison page, which indicates the formula is trustworthy. ^[3]

Take note of the potential pitfalls between the two columns: introductory prices typically double after the first year, meaning your decision might change upon renewal. A site generating €2,500 each year incurs €125 under the free tier, which seems more expensive than the €79.50 introductory license in the first year but becomes more cost-effective than the €159 renewal from the second year onward. The smartest approach is to choose the introductory year and reassess the formula at renewal time with the full price.

Three Business Scenarios, Three Distinct Answers

While formulas provide clarity, real-world examples often shine brighter. Here’s the same calculations applied to three realistic businesses (considering only plugin-related costs, since Stripe’s fees remain constant regardless):

The weekend bakery presents an intriguing scenario. With $3,600 in annual revenue, it exceeds both break-even thresholds, making even the “cheaper” 3% approach more expensive than a license. However, its preorder form for Saturday sourdough doesn’t necessitate subscriptions or donation targets, and a hosted payment page within a well-designed checkout can be achieved at $0 in plugin fees. Therefore, for most hobby-level operations, the solution lies in bypassing the plugin layer altogether.

The consultant is a volume-driven case. At $24,000 annually, the 3% option results in $720 per year, significantly higher than the license. Invoices tolerate a redirect since the client knows whom they are paying. Consequently, either a license or Payment Links is beneficial; the choice boils down to whether the invoice page will reside on the consultant’s website or on Stripe’s, which is more a branding decision than a financial one.

The small shop is where feature considerations become contentious. An embedded form is essential (since its checkout is part of a sales page designed for conversion), making Payment Links not viable. Given a yearly revenue of $96,000, the license practically pays for itself against the 5% alternative. The only lingering decision is which tier is most suited, which requires examining the features based on the shop’s actual sales.

Two lessons emerge from this table. Firstly, “free” options can accumulate costs very quickly: the small shop spends more on plugin fees every three weeks than the license costs for a whole year. Secondly, the practical answer might sometimes involve neither plugin: both the bakery and consultant don’t strictly require an embedded form, and a hosted payment page won’t incur any charges beyond Stripe’s fees. Opt for a plugin based on its features, not by default.

A Three-Year Overview

Percentage fees increase along with your sales, while license fees generally remain static. At an annual volume of $10,000, here’s the total cost over three years for each Level-2 option (the first year utilizing introductory prices, followed by years two and three at renewal prices):

WPFullPay displays pricing in euros while WP Simple Pay uses dollars. Therefore, compare each license against its equivalent free tier rather than against one another. In both cases, the pattern remains consistent: at stable volume, three years’ worth of percentage fees more than cover the cost of the license. Additionally, the license does more than eliminate fees; both plugins also provide a year’s worth of updates and genuine support, which you’ll value when a payment form malfunctions just before launch.

Managing multiple sites complicates matters as well. Each WPFullPay license covers a single site, so for three sites, you’ll need three licenses. In contrast, WP Simple Pay’s higher tiers can bundle support for three or even unlimited sites into a single plan. If you’re overseeing payments across various sites, evaluate the multi-site tiers before assuming the per-site calculations remain applicable.

Your Turn: Complete the Five-Minute Worksheet

Use last year’s figures (or your best estimate) and fill in the following:

Once filled out, it could look like this: if your site earned $850 monthly last year, then A = $850, B = $10,200, C = 5% for the free WPFullPay, leading to D = $510 annually in plugin fees. E = €159 for the basic renewal. Since D exceeds E by more than threefold, the worksheet suggests a purchase; similarly, the same $10,200 with WP Simple Pay Lite (D = $306 vs E = $99) makes the case even clearer. Just two minutes for one answer, and this solution works for both plugins.

One addition: if your sales are increasing, use next year’s projections instead of last year’s figures for line B. Stagnant break-even decisions often lead to sites inadvertently missing out, with a plugin retaining 5% of record-breaking months.

PRO TIP: Set a yearly reminder in your calendar for this worksheet. Prices for plugins can fluctuate, your income can change, and the right decision made last year may no longer be valid.

Identifying When the Free Tier is the Best Option

This isn’t an argument against free plugins; they often present the best choice more frequently than license promotions imply. Stick to the free options when your income remains below the break-even threshold, when trialing an idea that may not generate payments in the next six months, or when the functionalities offered by the free tier already meet your needs. The WPFullPay free version accommodates subscriptions and donations, while WP Simple Pay Lite is ideal for single payment forms, making “free” synonymous with “adequate” here. ^[4]

The only truly erroneous decisions are continuing to pay a percentage on substantial volumes because switching seemed laborious, or opting for a license for a form that generates merely $30 monthly. Everything that falls between those extremes warrants a quick five-minute worksheet.

Prefer a feature-based comparison instead of numbers? The accompanying guide evaluates Stripe Payment Links against embedded WordPress forms in straightforward terms. Additionally, if you complete the worksheet for your site, feel free to share your results in the comments!

References

1. [1] Stripe pricing: processing fees and fee structure
2. [2] WPFullPay pricing: Basic license and renewal conditions
3. [3] WP Simple Pay Lite vs Pro: the 3% fee with an example of $1,650
4. [4] WPFullPay on WordPress.org: capabilities of the free tier

FREE GUIDE

Four Key Steps to Enhance Your WordPress Website Speed

Utilise our four-part mini series to cut your loading times by 50% to 80%.

Congratulations! You’ve reached the conclusion of the article!