Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

China Payments Plugin

by Brandon Ernst · 200+ active installs · Checked 3 Nov 2026
Limited data

Limited data: China Payments Plugin has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

95/ 100Limited data
Canary Score

Based on 3 of 5 areas

Capped at 95: not enough support or review data for a full score.

Sub-scores for China Payments Plugin
Ownership100
Maintenance100
Security100
SupportNo data
ReputationNo data

How the score works

Active signals

Open issues right now, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Quick answers

Is China Payments Plugin still maintained?
Yes. Last release 8 Oct 2026, 14 releases in the last 24 months. 8 Oct 2026 · wordpress.org
Who owns China Payments Plugin, and has it changed hands?
No change recorded. Main committer brandonfire since Mar 2019. 3 Nov 2026 · SVN log
Was China Payments Plugin removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is China Payments Plugin safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest China Payments Plugin update safe to install?
No ownership change before 3.6.1. No one-star spike after it. 8 Oct 2026 · Release history

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
plugin-master3 Mar 2019 to 3 Mar 2019, 1 commits
brandonfire5 Mar 2019 to 8 Oct 2026, 112 commits
victoralbala18 Aug 2019 to 29 Dec 2020, 56 commits
paulmiller30008 Jan 2021 to 26 Jan 2021, 3 commits
juanobrach31 Mar 2021 to 5 May 2021, 4 commits

5 committers recorded. No ownership changes recorded since 2019.

Maintenance

Last release
28 days ago
Releases, 24 months
14
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for China Payments Plugin
Q1 20240
Q2 20241
Q3 20244
Q4 20241
Q1 20251
Q2 20250
Q3 20250
Q4 20251
Q1 20261
Q2 20269
Q3 20261
Q4 20261

Last release 8 Oct 2026. Tested with WordPress 7.1 (current).

Support

Resolved, last 2 months
n/a
Threads, last 2 months
0

Trend appears after 8 weekly snapshots.

Security record

No published vulnerabilities on record for this plugin.

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Last 90 days vs lifetime average rating for China Payments Plugin
Last 90 daysNo reviews
Lifetime5.0
Rating distribution
5 star17
4 star0
3 star0
2 star0
1 star0

Momentum

Active installs
200+

Trend appears after 8 weekly snapshots.

Facts

Full name
China Payments Plugin | Accept WeChat Pay, Alipay & UnionPay | Chinese Checkout Optimization
Version
3.6.1
Author
Brandon Ernst
Added
5 Mar 2019
Last updated
8 Oct 2026
Active installs
200+
Requires WordPress
5.1
Tested up to
7.1.4
Requires PHP
7.4
Category
not stated
Tags
alipay, stripe, unionpay, wechat pay, Chinese Payments

Other plugins by this author: Version Info, Payment Page, Split Pay, Blocked in China, Gyta Buyback, Login for Stripe Customer Portal, Speed in China

Questions about China Payments Plugin

Is China Payments Plugin still maintained?

Yes. Last release 8 Oct 2026, 14 releases in the last 24 months.

Who owns China Payments Plugin, and has it changed hands?

No change recorded. Main committer brandonfire since Mar 2019.

Was China Payments Plugin removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is China Payments Plugin safe?

No known vulnerabilities on record.

Is the latest China Payments Plugin update safe to install?

No ownership change before 3.6.1. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue