pull down to refresh
Ok, now make more sense. Still I think is unfair to replace and existing setup. In our case we offer multiple payments gateways (all bitcoin-only).
With this small test I was hoping to add BareBits as new payment method, but if this mean remove BTCpay server (the most trusted and used by our beloved customers), I'll need to stop here and wait until BareBits is a complete and independent system.
Ping me anytime when you have news on this particular point :)
reply
Totally understandable! We're hoping to add this feature at some point in the future so I'll drop you a ping.
reply
Basically, when you install the BareBits woocommerce plugin, it either "points to" an existing BareBits installation you have (on the same server or a different one) OR you can have the plugin automatically install BareBits alongside it at install time.
No matter how it was installed, your BareBits installation offers a "BTCPay Compatible Gateway" aka it presents as if it is a BTCPay Server. So to get woocommerce talking to it, we install + configure the BTCPay Server plugin in woocommerce and "point it" at your BareBits installation. And everything just works.
The benefit of this is that it means any e-commerce software that can talk to BTCPay Server can now talk to a BareBits installation instead (we don't have to write 50 plugins across 50 different e-commerce platforms). The downside is that, at least for woocommerce, you can only have one BTCPay Server payment plugin installed per installation. Other e-commerce platforms may enable side-by-side installation, I haven't tested that much on the other platforms.
** Just to clarify -- All this is happening on your own servers. BareBits devs don't run any servers.