Plugin profile · observed daily since 02 Aug 2026
ScanForPay – Alipay & AlipayHK & WechatPay Payment Solutions for WooCommerce
Active installs60+ rounded
Current authorscanforpay
Owner changesNone while we have been watching
Last release1 month ago 06 Oct 2026
Support— no recent threads
Releases on record23
Rating— no ratings yet
Added to directory13 May 2019
Requires WP4.9.10
Requires PHP5.4.16
Version lag0.3 behind
Tested up toWP 6.8.12 WordPress is now on 7.1
PluginsPedia 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 scanforpay 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 |
|---|---|---|---|
| scanforpay | 22 | 13 May 2019 | 09 Jan 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: 60+ 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 24% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
11 Sep 2026peak 47/day31 Oct 2026
No ratings on record, so there is no sentiment to report.
Install band fell to 60+ on 15 Oct 2026, from 70+. 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 | 18 Oct | 19 Oct | 20 Oct | 21 Oct | 22 Oct | 23 Oct | 24 Oct | 25 Oct | 26 Oct | 27 Oct | 28 Oct | 29 Oct | 30 Oct | 31 Oct |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 22 | 11 | 11 | 0 | 22 | 11 | 12 | 11 | 11 | 11 | 0 | 11 | 11 |
Unchanged throughout: ratings total (0) · active installs (60+) · version (1.2.0) · support threads (0) · threads resolved (0)
91 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 directory7.5 years ago 13 May 2019
Requires WP4.9.10
Requires PHP5.4.16
Version lag0.3 behind
Is anyone still maintaining this?
- Last released 06 Oct 2026, 34 days ago.
- Declares compatibility only up to WordPress 6.8.12, while 7.1 is current. The author has not confirmed it runs on the last 3 releases.
- scanforpay 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.
- 06 Oct 20261 month agoVersion 1.2.0 released
- 24 Sep 20262 months agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 22 Sep 20262 months agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 20 Sep 20262 months agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 19 Sep 20262 months agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 18 Sep 20262 months agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 10 Sep 20262 months agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 09 Sep 20262 months agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 06 Sep 20262 months agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 29 Aug 20262 months agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 22 Aug 20263 months agoInstall band moved to 60+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20263 months agoInstall band moved to 80+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20263 months agoFirst observed by PluginsPediaDaily 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.
- 09 Jan 202610 months agoVersion 1.1.9 released
- 13 Oct 202513 months agoVersion 1.1.7 releasedfrom the release logCommitted by scanforpay.
- 13 Oct 202513 months agoVersion 1.1.8 releasedfrom the release logCommitted by scanforpay.
- 02 Sep 202514 months agoVersion 1.1.6 releasedfrom the release logCommitted by scanforpay.
- 12 Apr 202519 months agoVersion 1.1.5 releasedfrom the release logCommitted by scanforpay.
- 13 Mar 20242.5 years agoVersion 1.1.4 releasedfrom the release logCommitted by scanforpay.
- 02 Dec 20214.5 years agoVersion 1.1.3 releasedfrom the release logCommitted by scanforpay.
- 08 Feb 20215.5 years agoVersion 1.1.2 releasedfrom the release logCommitted by scanforpay.
- 07 Dec 20205.5 years agoVersion 1.1.1 releasedfrom the release logCommitted by scanforpay.
- 04 Dec 20205.5 years agoVersion 1.0.9 releasedfrom the release logCommitted by scanforpay.
- 04 Dec 20205.5 years agoVersion 1.1.0 releasedfrom the release logCommitted by scanforpay.
- 19 Feb 20206.5 years agoVersion 1.0.8_1 releasedfrom the release logCommitted by scanforpay.
- 30 Dec 20196.5 years agoVersion 1.0.8 releasedfrom the release logCommitted by scanforpay.
- 13 May 20197.5 years ago9 earlier releasesfrom the release logBetween 13 May 2019 and 13 Dec 2019. Listed individually in the public release log rather than here.
- 13 May 20197.5 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 scanforpay for all 91 days we have observed it.
- It was last released 1 month ago (06 Oct 2026).
- Its author declares it tested up to WordPress 6.8.12; WordPress is now on 7.1.
- WordPress.org reports 60+ active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- 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.
Yedpay for WooCommerce
Easily accept Alipay, AlipayHK, Wechat Pay, UnionPay, Visa and mastercard on your Wordpress site using Yedpay WooCommerce payment gateway in one plugi …
300+ installs5.0★ (2)updated 26 Aug 2026
Wenprise Alipay Gateway For WooCommerce
Alipay payment gateway for WooCommerce, WooCommerce 支付宝免费全功能支付网关。
700+ installs5.0★ (1)updated 22 May 2026
Express Payment For Stripe
Shipping with a variety of standalone Stripe payment widgets and woocommerce addon, including options for credit cards, Alipay and WeChat pay, and ACH …
30+ installs5.0★ (3)updated 29 May 2026
China Payments Plugin | Accept WeChat Pay, Alipay & UnionPay | Chinese Checkout Optimization
Accept WeChat Pay, Alipay & UnionPay via Stripe with WooCommerce, MemberPress, LifterLMS & Simple Membership.
200+ installs5.0★ (17)updated 08 Oct 2026
AlphaPay for WeChat Pay, Alipay, UnionPay, and Credit Card（微信支付，支付宝，银联，信用卡支付）
Allow Canadian merchants to connect all the mainstream payment channels like WeChat Pay, Alipay, UnionPay, Visa, and MasterCard upon single activation …
60+ installsupdated 13 Mar 2026
Bayarcash GiveWP
Accept online donation from Malaysia and international payments. Supports FPX, DuitNow, NETS, Alipay, WeChat Pay, PromptPay and more payment channels.
30+ installsupdated 14 Nov 2025
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 ScanForPay – Alipay & AlipayHK & WechatPay Payment Solutions for WooCommerce: a person reads every submission, and corrections get a reply within 5 business days.