Visma Pay for Woocommerce
by vismapay · Payments
Also makes 1 other plugin · 1.1K+ installs across the portfolio →
Visma Pay plugin for Woocommerce.
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.
Health
Not scored
no reviews to score from
Active installs
1K+
≈1.7K estimated
Momentum
+75%
downloads vs prior 30d
Biggest opportunity: “pay” and “payment gateway” 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.
Not scored yet. Nobody has reviewed this plugin, so a grade would come from directory averages rather than from anything measured here.
Install conversion
How it's measured →2.5%
of downloads still active
At least 1K of 39.4K lifetime downloads are still running, above its category: the median Payments plugin keeps 1.0%, across 1,044 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
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.
Excellent listing optimization
Most to gain: Rating quality
Updated 26 days ago
Tested up to WordPress 7.1.4, the current branch or newer
No reviews yet, so wp.org scores it as a middling unrated listing
5 of 5 tags set · short description in place
To rank higher: No reviews yet. wp.org scores an unrated plugin as middling on rating, so the first good reviews lift it.
Get the full rank-higher report →Search visibility
How it's tracked →Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.
33
Momentum
Mixed: one swing, the rest drifting
0.0
Velocity
places per keyword, 23d
0%
Breadth
of keywords climbing, 23d
0.0
Acceleration
recent half vs earlier
wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.
| Keyword | wp.org | On merit | wp.org move, 90 days |
|---|---|---|---|
| visma your tag | #1 | #2 | 0 |
| verkkomaksut your tag | #1 | #1 | 0 |
| pankit your tag | #1 | #1 | 0 |
| pay your tag | Not in the top 24 | ||
| payment gateway your tag | Not in the top 24 | ||
6 searches this plugin appeared in over the last 90 days, 3 listed. 3 left out as unrelated or noise (years, numbers, stray words). 2 of its tags aren't in the top 24 for their own search.
What to do about it
- “pay” and “payment gateway” 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.
Daily downloads
Since 5 Oct 2022 · 1,489 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peak 2.8K · peaks are release surges
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
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.
What its installed base runs
via wordpress.orgShare of active installs on each version of this plugin · 80% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.
Estimated active installs
The public count shows “1K+”. Our estimate pins where the real number sits.
Crossed into this band 3 months ago; a band this size takes about a year or more to cross, which places it about 73% of the way through.
Install history since 4 Oct 2022
Latest updates
via wp.org changelogRecent releases and news for this plugin
- — Version 1.2.1 Updated ‘tested up to’ versions. Updated Siirto logo 1.2.1
- — Version 1.2.0 Updated ‘tested up to’ versions. Added new option to automatically capture payments of Completed orders. Normally payments are always captured instantly once they’re accepted, but if a merchant chooses to use separate ca 1.2.0
- — Version 1.1.6 Updated ‘tested up to’ versions. Removed Alisa Yrityslasku 1.1.6
- — Version 1.1.5 Fixed an issue with incorrect shipping tax rate being sent to Visma Pay API. 1.1.5
- — Version 1.1.4 Changed Visma Pay API version to w3.2 which supports decimals in tax percent Updated ‘tested up to’ versions. 1.1.4
- — Version 1.1.3 Increased specificity of plugin styles Updated ‘tested up to’ versions. 1.1.3
Security history
via Wordfence IntelligenceThe 1 disclosed vulnerability is patched in the current version (1.2.2). Sites still on an older version should update.
- 2026-10-14 CVE-2026-103308 Insufficient Verification of Data Authenticity Affects < 1.2.2 Patched in 1.2.2
Vulnerability records provided by Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. License and terms.
CVE records: Copyright 1999-2026 The MITRE Corporation. CVE terms of use.
Languages
via translate.wordpress.orgTranslated into 1 language, 1 at 90% or more · development strings
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
2 of 8 pass · checked 1 Nov 2026Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.
- ! Says what it does Short description is 33 characters, too short to say what the plugin does.
- ! 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 0 lists; assistants quote headed sections and bullet lists, not paragraphs.
- ! Enough to quote 639 characters of description; under 1,000 there is little to quote.
- ✓ Tags match the text 3 of 5 tags appear in the text; "pankit", "verkkomaksut" do not.
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2026-07-25 2K+ → 1K+ down after 5 days in tier
- 2026-07-20 1K+ → 2K+ up after 2 days in tier
- 2026-07-18 2K+ → 1K+ down
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).
-
Visma Pay (Embedded Card) for Woocommerce 100+ installs · 3.6★ · 4 shared tags -
افزونه پرداخت امن زرینپال برای ووکامرس (ZarinPal for WooCommerce) 60K+ installs · 3.7★ · 1 shared tag B -
Paystack WooCommerce Payment Gateway 20K+ installs · 4.3★ · 1 shared tag A -
PayU GPO Payment for WooCommerce 10K+ installs · 3.8★ · 1 shared tag B -
PhonePe Payment Solutions 10K+ installs · 3.3★ · 1 shared tag B -
Pay for Payment for WooCommerce – Payment Gateway Fees & Discounts 10K+ installs · 4.6★ · 1 shared tag A
Embed this report card
Drop a live Pulse card for Visma Pay for Woocommerce into a readme, a review or a deck. It updates itself.
<iframe src="https://plugins.wpmayor.com/embed/visma-pay-payment-gateway" width="480" height="300" style="border:0" loading="lazy" title="Visma Pay for Woocommerce — Plugin Pulse"></iframe> Visma Pay for Woocommerce: 1K+ active installs, no reviews yet. Plugin Pulse (WP Mayor), as of 2026-11-01. https://plugins.wpmayor.com/plugin/visma-pay-payment-gateway
Spotted a number that looks wrong? Report a data issue and we'll check it against the source.