GoBTC Pay for WooCommerce
by GoBTC Pay 0 (0 reviews)

GoBTC Pay for WooCommerce

Accept Bitcoin payments in your WooCommerce store via a hosted GoBTC Pay checkout.

GoBTC Pay for WooCommerce ranks #60,309 among WordPress.org plugins with 0+ active installations, is #10,113 of 14,124 in the E-commerce category, and was last updated Oct 13, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v1.1.4 Current Version v1.1.4
Updated 2 weeks ago Last Update on 13 Oct, 2026
Refreshed 2 days ago Last Refreshed on
#10,113 of 14,124 in E-commerce Downloads -52.9% this week Actively maintained
View on WordPress.org
Rank
#60,309
— No change
Active Installs
0+
— No change
KW Avg Position
79
60 better
Downloads
175
+4 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 20%
0+ 10+
32,741
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 8 more installs to reach 10+

Rank Changes

53,014 57,523 62,032 66,540 71,049 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
53,014 57,523 62,032 66,540 71,049 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
Current #60,309
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
0 10 20 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about GoBTC Pay for WooCommerce

No. The plugin talks to the GoBTC Pay API and the customer pays on the GoBTC Pay hosted checkout. Your store never holds keys or funds.
Most likely it was paid from an ordinary Bitcoin wallet and is waiting for network confirmation — usually about 10 to 30 minutes. See "Two payment routes" above. An order can also be On hold because the payment window closed and the plugin is waiting out the grace period in case the money still arrives.
It was paid from a wallet inside the GoBTC Pay ecosystem. That route reports the payment in one step, so the order is completed immediately and no confirmation wait applies.
No. The plugin declares support for products only; refunds are not part of it.
For an order that is still being watched, nothing is lost: the plugin also polls the payment status, so the order reaches its final state anyway. It does matter for one case. Once an order's payment window and its grace period have both expired, the order is cancelled and polling for it stops — a payment that arrives after that point can only reach the store as a webhook. With the endpoint unreachable, such an order stays cancelled while the customer believes they have paid. That is why, when payments are being created but no webhook has arrived for a while, the plugin raises an admin notice pointing at the usual causes: a changed URL, a firewall or security plugin blocking the request, or a signing secret that no longer matches. It is shown on WooCommerce's own screens, to users who can manage WooCommerce, and it is worth acting on.
Yes. GoBTC Pay runs a separate non-production contour; set the API base URL to it and use the credentials issued for that contour. It is not a sandbox. That contour settles on Bitcoin mainnet, so any payment you make against it spends real BTC and cannot be reversed. Treat an order placed there exactly as you would treat one in production.
Never let a copy run with the live secret key. Before the copy is first opened, not after, do one of two things on it: deactivate this plugin, or save a separate key over the live one. Emptying the "Secret API key" field does not remove the stored key — a blank field means "keep the current value" — and disabling the payment method does not stop the plugin talking to GoBTC Pay either. The key is not read-only: a copy that has it can cancel your production customers' payments. A copy carries the same orders and the same payment identifiers, and the plugin asks the service to cancel a payment
the copy, or letting it expire there, cancels the real payment of a real customer. Nothing on the copy looks wrong while this happens; the damage shows up in the live store. Second, and only once the key is dealt with: clear the plugin's site identifier on the copy, the gobtc_pay_site_id option. It is what keeps this store's payment identifiers apart from your other stores', and a copy starts out carrying the original's. Deleting the option is enough — the plugin creates a new one by itself. The current value is shown as "Installation identifier" at the bottom of the payment method's settings screen, which is how you can tell the copy from the original once you have done this.
No. Turning the payment method off removes it from checkout, so no new payment
it keeps polling them, keeps accepting webhook deliveries, keeps applying payment results to orders, and keeps cancelling the payment of an order that is

Sign In / Register

You need to sign in or register to use this feature.