Plugin Pulse Beta
← Pulse

Paguelofacil Checkout for Woocommerce

by PagueloFacil SA · Payments

Enable your store to accept payments via PagueloFacil and customize payment options, allowing customers to pay through our Checkout.

Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.

⚠ Stale⚠ Few reviews

Health

C 59/100

Stale · Few reviews

Active installs

300+

≈350 estimated

Momentum

+10%

downloads vs prior 30d

Biggest opportunity: “credit card”, “payment” and “woocommerce” aren't earning a slot. You list them, but you're not in the first 24 results for those searches. WordPress.org counts only your first five tags, so free the slot for a search you can win.

How scoring works →
59 Health · C
Maintenance 50/100
Rating quality 62/100
Support 70/100

59 health vs 68 average across 1,680 Payments plugins

Install conversion

How it's measured →

4.9%

of downloads still active

At least 300 of 6.1K lifetime downloads are still running, above its category: the median Payments plugin keeps 1.0%, across 1,042 plugins.

Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Payments plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.

Details

Version
4.2
Last updated
1.3y ago
Added
2022-04-03 · 4 yrs old
Requires WP
—
Tested up to
6.8.12
Requires PHP
8.0

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

76 / 100

Well optimized

Most to gain: Update recency

Update recency 58/100

Updated 465 days ago, past the ~180 days where wp.org starts discounting

WP compatibility 100/100

Tested up to WordPress 6.8.12, the current branch or newer

Rating quality 50/100

1.0★ over 2 reviews, smoothed to 3.98★ and held back under 25 reviews

Listing tuning 100/100

5 of 5 tags set · short description in place

To rank higher: Last updated 465 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

Get the full rank-higher report →

Daily downloads

Since 5 Oct 2022 · 1,488 days · wp.org + Plugin Pulse archive

+10% vs prior 30d
331 Oct 2026

30-day downloads

Rolling 30-day volume · peak 672 · peaks are release surges

17631 Oct 2026

Directory rank

Ranked about #10,100 to #11,100, alongside the other plugins at 300+ installs. Plugins with the same install count swap places between wp.org requests, so this is where most of them sit. Checked monthly, last on 21 Oct 2026.

Health trend

Composite health score, snapshotted daily

5931 Oct 2026

Update activity

How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.

58731 Oct 2026

Release cadence

No release in a year
from wp.org release tags

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

0

releases in the last 12 months

1.3y ago

latest release · v4.2 · 23 Jul 2025

10

tagged releases on record

Recent releases

4.2 · 23 Jul 20254.1 · 22 Jul 20254.0.4 · 19 Jul 20254.0.1 · 17 Jul 20254.0 · 27 Jul 20243.8 · 27 Jul 20243.7 · 30 Mar 20233.6 · 30 Mar 20233.2 · 15 Feb 20233.3 · 15 Feb 2023

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 74% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v4.2 74%
v3.7 26%

Estimated active installs

The public count shows “300+”. Our estimate pins where the real number sits.

tracked estimate
300–400 ≈350

Crossed into this band 15 months ago; a band this size takes about a year or more to cross, which places it about 50% of the way through.

Install history since 4 Oct 2022

30031 Oct 2026

Recent reviews

All reviews on wp.org ↗
  1. ★★★★★ mpweblab
    6mo ago

    Based in Panama, I am currently facing payment integration challenges for my online store. I therefore conducted some research and came across this plugin. Before implementing it in my WooCommerce store, I performed a code review. This plugin exhibits significant structural issues for production-grade WooCommerce usage. The integration is primarily based on an off-site payment flow using HTTP redirects and GET parameters, without any robust implementation of server-to-server validation (signed webhooks). Transaction confirmation appears to rely on the browser return URL, which is inherently unreliable by design and not aligned with modern payment gateway standards. No clear implementation of standard security mechanisms such as: HMAC signature verification of payloads Callback integrity validation Transaction idempotency handling Anti-replay attack protection is visible or documented within the WooCommerce payment flow. Furthermore, the absence of an explicit API key / secret key (API key pair model) within the plugin prevents any strong server-to-server authentication. This significantly limits the ability to cryptographically verify the origin and integrity of payment events. From a compliance perspective, this deviates from expected best practices for modern payment integrations aligned with PCI DSS principles (segmentation of trust boundaries, minimization of client-side trust, and backend-first validation). Practical consequences include: Frequent desynchronization between WooCommerce and the payment gateway (orders remaining “pending” despite successful payment) Reliance on the client browser for payment confirmation Increased attack surface through potential manipulation of return URLs / GET parameters Risk of replay or callback tampering in the absence of verifiable signatures Unstable user experience (post-payment redirect errors) Finally, the plugin appears to be poorly maintained, and support is effectively non-existent, significantly increasing operational risk in production environments. As it stands, this integration does not meet the security standards expected of a modern e-commerce payment gateway (HMAC-signed webhooks, server-side verification, PCI DSS-aligned architecture), and should not be used for production-critical online stores.mp-weblab This topic was modified 2 months, 3 weeks ago by mpweblab. Reason: Recommended security updates to the developpers

    Read on wp.org ↗
  2. ★★★★★ jsfarfan
    9mo ago

    This doesn’t work as it should with WooCommerce. First, this is more of a limitation than an error but.. forget about checking out in your website, this only works redirecting back and forward to process the payment. The real problems are the following: It seems like this plugin doesn’t get a lot of updates, which can be a security risk. I had a problem, even to it process payments with the redirecting, it shows an error page and doesn’t redirect back to the website as it should, so this can be very confusing for customers and even for us because on WooCommerce it shows as pending payment but in paguelofacil.com it does show up. So we have placed 2 tickets/messages some days ago, THEY DON’T REPLY ANYTHING… NO SUPPORT AT ALL. Careful if you want to risk using this plugin. This topic was modified 5 months, 4 weeks ago by jsfarfan.

    Read on wp.org ↗

Behavioral tests

via WP Hive

Automated install-time checks, tested on PHP 8.1.12 · WP 6.8.2

✓ Low memory footprint
✓ Low page-speed impact
✕ Runs on latest PHP + WP
✕ No PHP errors
✓ No JS errors
✓ Activates cleanly
✓ No resource errors
✕ No external HTTP errors
✓ Optimized database use
✕ Frequently updated

AI assistants

How it's measured →

Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.

Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.

Readme readiness

4 of 8 pass · checked 25 Oct 2026

Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.

  • ✓ Says what it does "Enable your store to accept payments via PagueloFacil and customize payment options, allowing customers to..."
  • ! Has a FAQ No FAQ section.
  • ! FAQ asks real questions No FAQ to judge.
  • ! Names who it is for Never says who the plugin is for or what they use it for.
  • ✓ Names what it works with Mentions WooCommerce.
  • ! Headings and lists 1 heading and 3 lists; assistants quote headed sections and bullet lists, not paragraphs.
  • ✓ Enough to quote 2,653 characters of description.
  • ✓ Tags match the text 3 of 5 tags appear in the text; "credit card", "panama" do not.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

  1. 2025-08-07 400+ → 300+ down after 1 days in tier
  2. 2025-08-06 300+ → 400+ up after 1 days in tier
  3. 2025-08-05 400+ → 300+ down after 18 days in tier
  4. 2025-07-18 500+ → 400+ down after 433 days in tier
  5. 2024-05-11 400+ → 500+ up after 6 days in tier
  6. 2024-05-05 500+ → 400+ down after 1 days in tier
  7. 2024-05-04 400+ → 500+ up after 4 days in tier
  8. 2024-04-30 500+ → 400+ down after 2 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Embed this report card

Drop a live Pulse card for Paguelofacil Checkout for Woocommerce into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/paguelofacil" width="480" height="300" style="border:0" loading="lazy" title="Paguelofacil Checkout for Woocommerce — Plugin Pulse"></iframe>
Preview card ↗

Paguelofacil Checkout for Woocommerce: 300+ active installs, 1.0★ (2 reviews). Plugin Pulse (WP Mayor), as of 2026-10-31. https://plugins.wpmayor.com/plugin/paguelofacil

Spotted a number that looks wrong? Report a data issue and we'll check it against the source.