Installed by hand from a release zip before? The folder is renamed in this\nversion, so the old one stays behind as a separate, still-active plugin.\nDeactivate and delete it \u2014 the new copy will tell you if you forget. Your\nsettings and existing orders are unaffected.<\/p>","1.0.0":"
First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3741919,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3741919,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3741919,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3741919,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.3","1.1.4"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[1886,12578,12611,6593,1887],"plugin_category":[45],"plugin_contributors":[286190],"plugin_business_model":[],"class_list":["post-378171","plugin","type-plugin","status-publish","hentry","plugin_tags-bitcoin","plugin_tags-btc","plugin_tags-cryptocurrency","plugin_tags-payment-gateway","plugin_tags-payments","plugin_category-ecommerce","plugin_contributors-gobtcpay","plugin_committers-gobtcpay"],"banners":{"banner":"https:\/\/ps.w.org\/gobtc-pay-for-woocommerce\/assets\/banner-772x250.png?rev=3741919","banner_2x":"https:\/\/ps.w.org\/gobtc-pay-for-woocommerce\/assets\/banner-1544x500.png?rev=3741919","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/gobtc-pay-for-woocommerce\/assets\/icon-128x128.png?rev=3741919","icon_2x":"https:\/\/ps.w.org\/gobtc-pay-for-woocommerce\/assets\/icon-256x256.png?rev=3741919","generated":false},"screenshots":[],"raw_content":"\n
GoBTC Pay for WooCommerce adds Bitcoin as a payment method to your store. The\ncustomer is sent to a hosted checkout operated by GoBTC Pay, pays there, and \u2014\nif your store is served over https \u2014 comes back to its usual order-received\npage. Your store never handles\nprivate keys, wallet software or on-chain transactions.<\/p>\n\n
The plugin keeps the order in step with the payment through two independent\nchannels: it polls the payment status on a schedule, and it accepts signed\nwebhook deliveries from GoBTC Pay. The two overlap almost everywhere, so a\nsingle missed poll or a single undelivered webhook does not strand a paid\norder. They are not interchangeable, though: once an order's payment window and\nits grace period have both run out, polling for that order stops, and a payment\nthat arrives after that reaches the store only as a webhook. Keeping the webhook\nendpoint reachable is therefore not optional.<\/p>\n\n
This is the part worth understanding before you install, because it decides\nwhen your goods are released.<\/p>\n\n
Paid from a wallet inside the GoBTC Pay ecosystem (instant).<\/strong> The payment\nreports as paid in one step. The order is marked paid and moves straight to a\nstate that allows fulfilment \u2014 Processing, or Completed for an order that needs\nno shipping. There is no waiting period. The plugin keeps polling in the\nbackground until the on-chain settlement time appears, but the order is already\npaid and the merchant is not asked to wait for it.<\/p>\n\n Paid from an ordinary Bitcoin wallet (external).<\/strong> The transfer is first seen\nin the mempool, and the order is held On hold while it waits for network\nconfirmation. Only once the payment is confirmed on-chain does the order move\nto a state that allows fulfilment. This usually takes about 10 to 30 minutes,\nbut it can take considerably longer when the Bitcoin network is congested.\nConfirmation time is a property of the network: neither the plugin nor your\nstore can influence it.<\/p>\n\n Both routes end with a paid order. The difference is the path the order takes\nand how long it takes to get there, so an On-hold order from an external\npayment is a normal, expected state and not a fault.<\/p>\n\n If the payment window closes before the customer pays, the order is held rather\nthan cancelled, and the plugin keeps watching it for a configurable grace period\n(12 hours by default). A payment that arrives inside that window still pays the\norder.<\/p>\n\n What happens after the grace period. If nothing arrives before it ends, the\norder is cancelled: WooCommerce restores the stock and sends its own\ncancellation e-mail. In most cases that is the end of it, because the payment\nis cancelled on the GoBTC Pay side at the same time. Occasionally the money is\nalready on its way and that cancellation does not go through. The payment is\nthen applied after all: the order returns to Processing, the stock is reduced\nagain, which leaves the count correct because cancelling had returned it, and\nthe order gets a note saying it was cancelled and paid after all. The\ncancellation e-mail your customer has already received is not retracted, so\ntell them the order is going ahead. Treat it as any other paid order and ship\nit.<\/p>\n\n This plugin is a client for a third-party service and does not work without it.<\/p>\n\n See \"External service\" below for the service, its endpoints and its legal\nterms. This subsection covers the one thing that section does not: exactly what\nleaves your store, and the one configuration that can cost you real money.<\/p>\n\n Endpoints contacted by your server:<\/strong> the API base URL you configure in the\nplugin settings \u2014 What your server sends to GoBTC Pay:<\/strong><\/p>\n\n What GoBTC Pay sends back to your server:<\/strong> the payment's status, amount,\ncurrency, identifiers, timestamps and, where present, its on-chain transactions.\nWebhook deliveries are signed and their signature is verified before anything is\napplied to an order.<\/p>\n\n What the customer's browser sends:<\/strong> the customer is redirected to the GoBTC\nPay hosted checkout, so their browser contacts GoBTC Pay directly and that\nservice sees whatever a website normally sees about a visitor. The redirect\ncarries the two addresses the customer is returned to on your store \u2014 the\norder-received page and the pay-again page.<\/p>\n\n Terms of service:<\/strong> https:\/\/gobtcpay.com\/terms\nPrivacy policy:<\/strong> https:\/\/gobtcpay.com\/privacy-policy<\/p>\n\n This plugin connects your WooCommerce store to GoBTC Pay, a Bitcoin payment\nservice operated by GoMining. The plugin does not process payments itself:\nit creates a payment through the GoBTC Pay merchant API and redirects the\ncustomer to the GoBTC Pay hosted checkout page to complete it.<\/p>\n\n The service is contacted in the following cases:<\/p>\n\n The customer is redirected to the hosted checkout page at\nhttps:\/\/pay.gobtcpay.com. Whether they are sent back afterwards depends on your\nstore: a return address is only handed to the hosted checkout when the store is\nserved over https, and without one the customer stays on the checkout page after\npaying \u2014 see \"Installation\" for the requirement. The payment itself is\nunaffected either way: the plugin reads the payment status from the service on\nits own schedule, so an order still reaches its final state whether or not the\ncustomer comes back.<\/p>\n\n The data sent to the service for each payment is the order amount, the\norder currency, and an order reference generated by the plugin. Your secret\nAPI key is sent as an authorization header and is never exposed to the\ncustomer's browser.<\/p>\n\n Service provider: GoMining (GoBTC Pay)\nMerchant API: the GoBTC Pay merchant API, at the base URL configured in the\nplugin settings\nHosted checkout: https:\/\/pay.gobtcpay.com\nTerms of Service: https:\/\/gobtcpay.com\/terms\nPrivacy Policy: https:\/\/gobtcpay.com\/privacy-policy<\/p>\n\n\n Saved secrets are never displayed back on the settings page: the field renders\nempty, and leaving it empty when you save means \"keep the current value\".<\/p>\n\n\n No. The plugin talks to the GoBTC Pay API and the customer pays on the GoBTC Pay\nhosted checkout. Your store never holds keys or funds.<\/p><\/dd>\n Most likely it was paid from an ordinary Bitcoin wallet and is waiting for\nnetwork confirmation \u2014 usually about 10 to 30 minutes. See \"Two payment routes\"\nabove. An order can also be On hold because the payment window closed and the\nplugin is waiting out the grace period in case the money still arrives.<\/p><\/dd>\n It was paid from a wallet inside the GoBTC Pay ecosystem. That route reports the\npayment in one step, so the order is completed immediately and no confirmation\nwait applies.<\/p><\/dd>\n No. The plugin declares support for products only; refunds are not part of it.<\/p><\/dd>\n For an order that is still being watched, nothing is lost: the plugin also polls\nthe payment status, so the order reaches its final state anyway.<\/p>\n\n It does matter for one case. Once an order's payment window and its grace period\nhave both expired, the order is cancelled and polling for it stops \u2014 a payment\nthat arrives after that point can only reach the store as a webhook. With the\nendpoint unreachable, such an order stays cancelled while the customer believes\nthey have paid.<\/p>\n\n That is why, when payments are being created but no webhook has arrived for a\nwhile, the plugin raises an admin notice pointing at the usual causes: a changed\nURL, a firewall or security plugin blocking the request, or a signing secret that\nno longer matches. It is shown on WooCommerce's own screens, to users who can\nmanage WooCommerce, and it is worth acting on.<\/p><\/dd>\n Yes. GoBTC Pay runs a separate non-production contour; set the API base URL to\nit and use the credentials issued for that contour.<\/p>\n\n It is not a sandbox.<\/strong> That contour settles on Bitcoin mainnet, so any payment\nyou make against it spends real BTC and cannot be reversed. Treat an order\nplaced there exactly as you would treat one in production.<\/p><\/dd>\n Never let a copy run with the live secret key.<\/strong> Before the copy is first\nopened, not after, do one of two things on it: deactivate this plugin, or save a\nseparate key over the live one. Emptying the \"Secret API key\" field does not<\/strong>\nremove the stored key \u2014 a blank field means \"keep the current value\" \u2014 and\ndisabling the payment method does not stop the plugin talking to GoBTC Pay\neither. The key is not read-only: a copy that has it can cancel your production\ncustomers' payments. A copy carries the same orders and the same\npayment identifiers, and the plugin asks the service to cancel a payment\nwhenever its order is cancelled or has outgrown it \u2014 so cancelling an order on\nthe copy, or letting it expire there, cancels the real payment of a real\ncustomer. Nothing on the copy looks wrong while this happens; the damage shows\nup in the live store.<\/p>\n\n Second, and only once the key is dealt with: clear the plugin's site identifier\non the copy, the No. Turning the payment method off removes it from checkout, so no new payment\nis created. It does not stop the plugin working on payments that already exist:\nit keeps polling them, keeps accepting webhook deliveries, keeps applying\npayment results to orders, and keeps cancelling the payment of an order that is\ncancelled or whose total has changed. That is deliberate \u2014 an order whose\ncustomer has already sent bitcoin still has to reach the right state.<\/p>\n\n Deactivating the plugin is the only thing that stops all of it.<\/p><\/dd>\n Both. The classic shortcode checkout and the Cart & Checkout Blocks checkout are\nsupported.<\/p><\/dd>\n\n<\/dl>\n\n\nLate payments<\/h4>\n\n
What the plugin does not do<\/h4>\n\n
\n
External service disclosure<\/h4>\n\n
https:\/\/api.gobtcpay.com\/public\/api\/v1.2<\/code> for production, or\n https:\/\/pay.dev.gobtcpay.com\/public\/api\/v1.2 for the separate non-production\ncontour operated by GoBTC Pay. That contour runs on Bitcoin mainnet: payments\nmade against it move real BTC.<\/strong> It is not a sandbox and there is no test\nnetwork behind it.<\/p>\n\n\n
External service<\/h3>\n\n
\n
\n
\n
sk_live_\u2026<\/code> key from your GoBTC Pay dashboard. A\npublishable key (pk_live_\u2026<\/code>) is rejected outright when you save. A key\nrestricted to a single store is rejected too, provided the platform answers\nthe check; if it cannot be reached, the settings are saved with the key\nunverified and the check is retried in the background.<\/li>\nwhsec_\u2026<\/code> secret of the webhook endpoint\nyou create in the GoBTC Pay dashboard.<\/li>\n\n
Do I need a Bitcoin wallet or a node to use this?<\/h3><\/dt>\n
Why is an order stuck On hold?<\/h3><\/dt>\n
Why did another order go to Processing straight away?<\/h3><\/dt>\n
Can I refund through the plugin?<\/h3><\/dt>\n
What happens if my webhook endpoint is unreachable?<\/h3><\/dt>\n
Can I point the plugin at a non-production environment?<\/h3><\/dt>\n
I copied my store to a staging or test site. What must I do?<\/h3><\/dt>\n
gobtc_pay_site_id<\/code> option. It is what keeps this store's\npayment identifiers apart from your other stores', and a copy starts out\ncarrying the original's. Deleting the option is enough \u2014 the plugin creates a\nnew one by itself. The current value is shown as \"Installation identifier\" at\nthe bottom of the payment method's settings screen, which is how you can tell\nthe copy from the original once you have done this.<\/p><\/dd>\nI turned the payment method off. Has the plugin stopped?<\/h3><\/dt>\n
Which WooCommerce checkout does it work with?<\/h3><\/dt>\n
1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
wc-<\/code>, for example\n wc-a1b2c3d4-order-1234-USD-4999. Two stores of one merchant that reached\nthe same order number for the same amount used to produce the same\nidentifier, and the platform treats one identifier as one payment \u2014 so the\nsecond store was handed the first store's payment. Payments created before\nthis update keep working unchanged.<\/li>\napi.gobtcpay.com<\/code>, the merchant\nAPI's own host. Stores that already have a value saved keep it \u2014 this changes\nonly what a fresh install starts with.<\/li>\ngobtc-pay-for-woocommerce<\/code>. Nothing a store has\nsaved moves with it: the settings, the payment method and the payment data on\nexisting orders are keyed by identifiers that did not change.<\/li>\n1.0.0<\/h4>\n\n
\n