Plugin profile · observed daily since 02 Aug 2026
FLIZpay Gateway für WooCommerce
Active installs90+ rounded
Current authorFLIZpay
Owner changesNone while we have been watching
Last release13 days ago 02 Sep 2026
Support— no recent threads
Releases on record55
Rating3.0 /5 · 1
Added to directory12 Sep 2024
Requires WP6.4
Requires PHP8.2
Version lag0.1 behind
Tested up toWP 7.0.4 WordPress is now on 7.1
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by FLIZpay throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| flizpay | 55 | 12 Sep 2024 | 02 Sep 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Very early-stage: 90+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
10 downloads a day over the last 7 days, falling 57% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 95/day15 Sep 2026
Install band rose to 90+ on 15 Sep 2026, from 80+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep | 09 Sep | 10 Sep | 11 Sep | 12 Sep | 13 Sep | 14 Sep | 15 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 36 | 95 | 11 | 0 | 11 | 0 | 0 | 11 | 0 | 20 | 11 | 0 | 28 |
| Active installs | 90+ | 90+ | 90+ | 90+ | 80+ | 80+ | 80+ | 80+ | 80+ | 80+ | 80+ | 90+ | 80+ | 90+ |
| Version | 2.5.4 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
Unchanged throughout: ratings total (1) · support threads (0) · threads resolved (0)
45 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory2 years ago 12 Sep 2024
Requires WP6.4
Requires PHP8.2
Version lag0.1 behind
Is anyone still maintaining this?
- Last released 02 Sep 2026, 14 days ago.
- Declares compatibility only up to WordPress 7.0.4, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- FLIZpay publishes no other plugin in the directory, so there is no wider activity to compare against.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 14 Sep 20262 days agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 13 Sep 20263 days agoInstall band moved to 90+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 06 Sep 202610 days agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Sep 202614 days agoVersion 2.6.0 released
- 01 Sep 202615 days agoInstall band moved to 90+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 31 Aug 202616 days agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 29 Aug 202618 days agoVersion 2.5.4 released
- 29 Aug 202618 days agoInstall band moved to 90+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 26 Aug 202621 days agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 25 Aug 202622 days agoInstall band moved to 90+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 22 Aug 202625 days agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 21 Aug 202626 days agoInstall band moved to 90+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 04 Aug 20261 month agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 03 Aug 20261 month agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 14 Jul 20262 months agoVersion 2.5.3 released
- 26 Jun 20263 months agoVersion 2.5.2 releasedfrom the release logCommitted by flizpay.
- 17 Jun 20263 months agoVersion 2.5.1 releasedfrom the release logCommitted by flizpay.
- 26 May 20264 months agoVersion 2.5.0 releasedfrom the release logCommitted by flizpay.
- 21 May 20264 months agoVersion 2.4.20 releasedfrom the release logCommitted by flizpay.
- 22 Apr 20265 months agoVersion 2.4.19 releasedfrom the release logCommitted by flizpay.
- 15 Apr 20265 months agoVersion 2.4.18 releasedfrom the release logCommitted by flizpay.
- 19 Feb 20267 months agoVersion 2.4.16 releasedfrom the release logCommitted by flizpay.
- 19 Feb 20267 months agoVersion 2.4.17 releasedfrom the release logCommitted by flizpay.
- 17 Oct 202511 months agoVersion 2.4.15 releasedfrom the release logCommitted by flizpay.
- 19 Sep 202512 months agoVersion 2.4.14 releasedfrom the release logCommitted by flizpay.
- 17 Sep 202512 months agoVersion 2.4.13 releasedfrom the release logCommitted by flizpay.
- 25 Jul 202514 months agoVersion 2.4.12 releasedfrom the release logCommitted by flizpay.
- 12 Sep 20242 years ago40 earlier releasesfrom the release logBetween 12 Sep 2024 and 19 Jul 2025. Listed individually in the public release log rather than here.
- 12 Sep 20242 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by FLIZpay for all 45 days we have observed it.
- It was last released 13 days ago (02 Sep 2026).
- Its author declares it tested up to WordPress 7.0.4; WordPress is now on 7.1.
- WordPress.org reports 90+ active installs.
- It carries 1 rating, averaging 3.0 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.
Payment Gateway Based Fees and Discounts for WooCommerce
Set fees and discounts for WooCommerce payment gateways.
30,000+ installs4.7★ (58)updated 10 Sep 2026
ELEX WooCommerce Discount Per Payment Method
It will be a pleasant little surprise for customers if you offer a discount based on the payment method they have chosen on the Checkout page.
1,000+ installs4.3★ (6)updated 17 Mar 2026
Desconto Automático por Método de Pagamento | Cyfer
Apply automatic discounts based on the selected payment method in WooCommerce without using coupons.
100+ installsupdated 10 Jul 2026
Discounts Per Payment Method on WooCommerce
Adds discounts for specific payment methods in WooCommerce.
1,000+ installs4.4★ (35)updated 10 Aug 2020
no release in over 18 months
Simple Price Fee
Adds a fixed fee or discount to the WooCommerce cart total based on subtotal ranges, with a customizable label shown at checkout and in the cart.
20+ installs5.0★ (1)updated 19 Jun 2025
DeftCoders – Discount & Fee Rules for WooCommerce
Automatically add fees and apply discounts in WooCommerce based on cart, payment method, user role, date, time, and location. No coupon codes needed.
fewer than 10 installs5.0★ (1)updated 15 Mar 2026
Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about FLIZpay Gateway für WooCommerce: a person reads every submission, and corrections get a reply within 5 business days.