Plugin profile · observed daily since 02 Aug 2026
Bitcoin payment for Gravity Forms
Active installsfewer than 10 rounded
Current authorCoinsnap
Owner changesNone while we have been watching
Last release19 days ago 20 Oct 2026
Support— no recent threads
Releases on record11
Rating— no ratings yet
Added to directory05 Apr 2025
Requires WP5.2
Requires PHP7.4
Version lag0.1 behind
Tested up toWP 7.0.8 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 Coinsnap 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 |
|---|---|---|---|
| coinsnap | 11 | 05 Apr 2025 | 24 May 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: fewer than 10 active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
6 downloads a day over the last 7 days, falling 44% 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 23/day31 Oct 2026
No ratings on record, so there is no sentiment to report.
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 | — | 11 | 0 | 11 | 23 | 11 | 22 | 0 | 11 | 11 | 11 | 0 | 0 | 11 |
Unchanged throughout: ratings total (0) · active installs (0+) · version (1.3.6) · 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 directory19 months ago 05 Apr 2025
Requires WP5.2
Requires PHP7.4
Version lag0.1 behind
Is anyone still maintaining this?
- Last released 20 Oct 2026, 19 days ago.
- Declares compatibility only up to WordPress 7.0.8, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- The same account maintains 13 other plugins, 11 of which were updated in the last 90 days. the account is active.
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.
- 20 Oct 202619 days agoVersion 1.3.6 released
- 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.
- 07 Apr 20267 months agoVersion 1.3.5 releasedfrom the release logCommitted by coinsnap.
- 07 Mar 20268 months agoVersion 1.3.4 releasedfrom the release logCommitted by coinsnap.
- 29 Dec 202510 months agoVersion 1.3.1 releasedfrom the release logCommitted by coinsnap.
- 29 Dec 202510 months agoVersion 1.3.2 releasedfrom the release logCommitted by coinsnap.
- 29 Dec 202510 months agoVersion 1.3.3 releasedfrom the release logCommitted by coinsnap.
- 11 Jul 202516 months agoVersion 1.2.1 releasedfrom the release logCommitted by coinsnap.
- 24 Jun 202516 months agoVersion 1.2.0 releasedfrom the release logCommitted by coinsnap.
- 07 Jun 202517 months agoVersion 1.1.0 releasedfrom the release logCommitted by coinsnap.
- 29 Apr 202518 months agoVersion 1.0.1 releasedfrom the release logCommitted by coinsnap.
- 05 Apr 202519 months agoVersion 1.0.0 releasedfrom the release logCommitted by coinsnap.
- 05 Apr 202519 months 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 Coinsnap for all 91 days we have observed it.
- It was last released 19 days ago (20 Oct 2026).
- Its author declares it tested up to WordPress 7.0.8; WordPress is now on 7.1.
- WordPress.org reports fewer than 10 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.
- No release in the 91 days we have been watching, so how often it ships cannot be said. Every further day of silence tells you more.
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.
Bitcoin Payment for Contact Form 7
Accept Bitcoin and Lightning in Contact Form 7 for donations, products, bookings, downloads, services, registrations and micropayments.
fewer than 10 installsupdated 20 Oct 2026
Bitcoin payment for Ninja Forms
Accept Bitcoin and Lightning in Ninja Forms for payments, donations, registrations, newsletters, CRM leads, file uploads and micropayments.
fewer than 10 installsupdated 20 Oct 2026
MyCryptoCheckout – Bitcoin, Ethereum, and 100+ altcoins for WooCommerce
Crypto payment gateway for WooCommerce and Easy Digital Downloads. Accept 100+ coins: Bitcoin, Ethereum, BNB, Solana. Peer2Peer transactions.
8,000+ installs4.3★ (49)updated 19 Aug 2026
BareBits – Lightning Payments via Bitcoin
Accept Bitcoin (on-chain and Lightning) in WooCommerce through a BareBits server. No approval process, no middlemen. Low 1% fee.
fewer than 10 installs5.0★ (1)updated 29 Oct 2026
Bitcoin payment for WPForms
Accept Bitcoin and Lightning payments in WPForms for donations, products, bookings, downloads, services and micropayment workflows.
fewer than 10 installsupdated 20 Oct 2026
Bitcoin and Lightning Payments for FluentCart
Accept Bitcoin and Lightning payments in FluentCart through your own self-hosted BTCPay Server.
fewer than 10 installsupdated 02 Sep 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 Bitcoin payment for Gravity Forms: a person reads every submission, and corrections get a reply within 5 business days.