pull down to refresh

There are just few BTCpay server instances available for merchants to use. The ones I found are:
We have been testing all of them with our SWAG shop. There was another in Canada, can't find it anymore.
Usually we tend to install and run BTCpay server for personal/single-access use. These instances above have publicly made the decision to enable access for others to register and use the server, with no extra cost added, simply to support their surrounding community and promote bitcoin adoption.
I think it is a great service for the community and there must be more, because merchants and businesses we talk with often are not tech literates, simply sue phone and PC. But asking to install a software in a server is kind too much. They just want to run their business. Accept bitcoin? Sure... how? Too complicated or technical? They probably skip and miss the opportunity.
Should be there more instances available for businesses and vendors?
Found it, the fourth one we tested is https://btcpay.bithelm.com managed by @craigonbitcoin
reply
These public instances are supposed to be used only as demo or as a preliminary preparations, testing before use of a full BTCpay server on your own hardware.
Nevertheless, it could be also like "community servers" but they should well inform the users about terms of use, risks, etc. In the end you are using somebody else infrastructure so you will depend on them. Nothing wrong with that if they offer the service with specific warnings and limitations.
Yes, I agree, we should have more servers like these, "serving" local merchants. These could be an easy ramp-on for many hesitating merchants.
reply
21 sats \ 5 replies \ @AG OP 2 Nov
The instance hosted by BTCpay server is pretty clear about the conditions and take no responsibility in case of a loss.
Same for the other two I tried, the fact is that using them in a self-custodial manner does not affect the fact of using the open source software as payment gateway for onchain transactions.
Everything change if a lightning node is connected, especially if the business chose a custodial service to node. In this case the risks are much higher, it is always good to withdraw any fund once a certain threshold is reach. There should be no issue with a sovereign non-custodial lightning node.
From your experience, what would be the worst thing happening using such services?
reply
what would be the worst thing happening using such services?
Shut down and will disrupt your webshop services until you redirect, re-build everything on a new instance...
About the LN node thing. Did you tried also to run a hosted BTCpay instance, with Rizful (cloud node) ? You can easily connect BTCpay with NWC. You control the Rizful node liquidity, channels, funds etc, but you still depend on their cloud servers. Anyways is a good alternative if you do not want / can't run your own hardware. Amd is simple as fuck. Just few clicks.
reply
Shut down and will disrupt your webshop services until you redirect, re-build everything on a new instance...
From my experience, does not take long to set up the hardware wallet in BTCpay. So if one shut down, there is another one ready to use.
Yes tried BTCpay on various service providers too, it definitely round smoothly and give access as admin instead of just a shop admin. Another benefit is that as admin, one can install various plugins, that would not be available in the instances mentioned above.
No did not try rizful yet, mostly played with the LNbits integration and our own node. I'll create one and play, great suggestion :)
reply
Be aware:
Are not the same thing. I suggest to use the node option as a LN backend for a BTCpay. Even 1 max 2 private channels with a good LSP will be enough for a webshop.
reply
100 sats \ 1 reply \ @AG OP 2 Nov
too easy... decoy activated!
reply
hahaha even the "huh cat" can do it!
reply