Plugin Pulse
← 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.

⚠ Stale⚠ Few reviews
How scoring works →
62 Health · C
Maintenance 57/100
Rating quality 62/100
Support 70/100

62 health vs 65 average across 1,095 Payments plugins

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.

78 / 100

Well optimized

Biggest win: Rating quality

Update recency 65/100
WP compatibility 100/100
Rating quality 50/100
Listing tuning 100/100

To rank higher: Too few reviews to rank on quality — nudge happy users to leave one.

Get the full rank-higher report →

Daily downloads

Since 2022-10-05 · 1,425 days · wp.org + Plugin Pulse archive

+61% vs prior 30d
2Downloads · Aug 26

30-day downloads

Rolling 30-day volume · peaks are release surges

121

now · peak 672

12130d downloads · Aug 26

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

Paguelofacil Checkou · #10416 you WooPayments: Integra · #75 WooCommerce PayPal P · #81 WooCommerce Stripe P · #85

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.

403per 1k installs · Aug 26

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.1y ago

latest release · v4.2

10

tagged releases on record

Recent releases

4.2 · 1.1y ago4.1 · 1.1y ago4.0.4 · 1.1y ago4.0.1 · 1.1y ago4.0 · 2.1y ago3.8 · 2.1y ago3.7 · 3.4y ago3.6 · 3.4y ago3.2 · 3.5y ago3.3 · 3.5y ago

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 ≈390

Refined from the date this plugin crossed into its current band.

Install history · since 2022-10-04 · 1,384 observations

300Installs · Aug 26

Estimated value

What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.

Est. annual revenue

N/A

Est. acquisition value

N/A

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.

Details

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

Recent reviews

All reviews on wp.org ↗
  1. mpweblab
    4mo 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
    7mo 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

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).

Compare head to head →

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-08-30. https://plugins.wpmayor.com/plugin/paguelofacil