CensusPlugin profiles › WooPayments

WooPayments: Integrated WooCommerce Payments

Figures from the Plugin Directory Census · as of 28 Aug 2026

800,000

Active installs, lower bound

Group: 100,000 to 999,999 installs

8

Days since the last release

Group median: 12

3.4

out of 5, from 167 ratings

Group median: 4.7 (10+ ratings)

77.8%

Support threads marked resolved, two months

Group: 68.2%

Full profile on wordpress.orgShow on the mapCompare with your own plugins

What is WooPayments and who is behind it?

WooPayments is a WordPress plugin in the “Shop” field, made by WooCommerce. It has been listed in the directory since 8 Apr 2020, so for 6 years. WooCommerce has 16 plugins with at least 10,000 installs in the census. With 800,000 to 899,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 8 days before the reference date, and it is tested up to WordPress 7.0.

This is how the author describes the plugin on wordpress.org:

“Securely accept credit and debit cards on your WooCommerce store. Manage payments without leaving your WordPress dashboard. Only with WooPayments.”

Self-description on wordpress.org, retrieved on 10 Sept 2026

When was WooPayments last released?

The last release of WooPayments came 8 days before the reference date; the group median is 12 days.

WooPayments · 8 days today1 month3 months1 year3 years10 years
Each dot is a plugin in the 100,000 to 999,999 installs group, placed horizontally by days since its last release, on a logarithmic scale. The dashed line marks 365 days.

How many installs does WooPayments have?

WooPayments had 800,000 to 899,999 active installs on the reference date. Within its group, 6 plugins had a higher band and 7 plugins the same band.

The API reports installs only as a lower bound with one significant figure: 800,000 means at least 800,000 and at most 899,999.

Which WordPress version is WooPayments tested with?

No directory notice: tested up to WordPress 7.0, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 8.0% of the group.

How does WooPayments compare with its group?

The group holds 399 listed plugins. 28.3% of them had a more recent last release than WooPayments; 5.3% had no release for more than 365 days.

FigureWooPaymentsGroup, 399 plugins
Days since the last release8median 12
Rating3.4 (167)median 4.7 (10+ ratings)
Support threads marked resolved77.8%68.2%
Tested up to7.047.6% on 7.1
Requires PHP7.4most often 7.4 (41.6%)

All values on the reference date

Slugwoocommerce-payments
AuthorWooCommerce
Active installs800,000 to 899,999
Last release8 days before the reference date
Tested up toWordPress 7.0 · core on the reference date: 7.1
Requires WordPress6.0
Requires PHP7.4
Rating3.4 out of 5 from 167 ratings
Support threads, two months7 of 9 marked resolved
Listed since8 Apr 2020
Total downloads45,068,343, updates included
Tagsapple-pay, credit-card, google-pay, payment, woocommerce-payments

Tags

TagPlugins with 10,000+ installs and this tagRank by installsMedian days since release
apple-pay4135
credit-card9124
google-pay4135
payment7125
woocommerce-payments2115

Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.

Class of 2020

WooPayments has been listed since 8 Apr 2020. Of the 150 plugins with 10,000+ installs added in 2020, 87.3% released within the 365 days before the reference date.

Same group, shared tags

Not a recommendation; the same figures for comparison. Alphabetical.

PluginActive installsLast releaseRating
Mollie Payments for WooCommerce100,000 to 199,99939 days before the reference date3.5 (70)
Payment Plugins for Stripe WooCommerce100,000 to 199,9995 days before the reference date4.8 (301)
WooCommerce PayPal Payments800,000 to 899,99924 days before the reference date2.8 (577)
WooCommerce Stripe Payment Gateway700,000 to 799,99911 days before the reference date3.1 (235)
WooCommerce Tax500,000 to 599,9994 days before the reference date2.0 (105)

Do you maintain WooPayments?

If you maintain WooPayments, you can link to this profile, for example from your readme or your website. Both snippets show this badge:

WooPayments in the Plugin Directory Census 01/2026

HTML

<a href="https://hafenstudios.com/en/census/plugins/woocommerce-payments/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="WooPayments in the Plugin Directory Census 01/2026" width="220" height="40"></a>

Markdown

[![WooPayments in the Plugin Directory Census 01/2026](https://hafenstudios.com/census/plugins/badge-en.svg)](https://hafenstudios.com/en/census/plugins/woocommerce-payments/)

The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.

A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.

How to cite

hafenstudios (2026): WooPayments: Integrated WooCommerce Payments, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/woocommerce-payments/

Source and status

All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.

Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.