I've been using a hosted BTCpay with woocommerce to accept LN for a few years now, integrated with Blink wallet, which is working really well, but I don't know how things would work when Blink changes to non-custodial, since the new account created now doesn't even have API access, not to mention that Blink also got a light KYC.
Or I could use Rizful as backend to accept LN, but the hosted BTCpay that I'm currently using doesn't support it.
So it seems here are the options:
- Running the BTCpay server myself, lunanode might be the choice, but I remember it had light KYC a few years back when I tried it.
- Finding/paying for the hosted BTCpay which enabled the NWC plugin so that I could use Rizful - any good recommendations?
- Running both the node and the BTCpay server myself, I would really like this, but since not many people are paying in Bitcoin yet, probably it's better to opt for the more cost-effective option at the moment.
Or does anyone know a better setup?
Sum up all the solutions in the commect secession
I read you are using woocommerce. My simplest suggestion in this case is:
That's it! You are sorted, and you can also charge sats in auto-renewal for subscriptions. You also gain privacy, as there are no HTTP/HTTPS calls for the lighting payments. Everything goes through Nostr relays.
just tested it, magic 👀
That's great! I'm helping out SHOCK, and it would be great to hear your experience with shockwallet an clink, in case you tried the auto-renew subscriptions.
Do you have any suggestions on how we could do things better from a Ui/UX ~Design perspective?
I will write down some of the issues first:
cc @06bc1a977d
Design-wise: the payment page feels a bit crowded now.
That's all that comes to mind now, I would try the auto-renew subscriptions later:)
Thank you for your feedback. Some of your suggestions have been considered in this last release #1538237
Consider upgrading to the latest version and let me know if something else can be improved.
so when users paying with CLINK not compatible, payment would fail? wouldn't this be a potential issue?
The renewal feature is really cool!
The autorenewal without further auth is really useful, it well simulate fiat subscriptions ux. No clink is just the transport protocol, via nostr relays (no http calls). The lightning.pub (LND) node in the other site will generate bolt11 invoices every time they are needed, and the woocommerce plugin will serve them to the frontend for the user to pay sats with any lightning wallet, does it matter if is custodial, non-custodial, trustodial, fa(r)ke-odial.
I host some merchants on my btcpay instance (on start9 with luna node as VPS). I never got kycd from Luna node, works great.
For lightning, my merchants have opted for Aqua wallet (Samrock protocol; holds liquid at rest). Its not the most sovereign solution for them but its private and simple. Only fees are 0.25% boltz swap fee.
I'm happy to host you for free if your traffic isn't high.
Thanks for your kindness, but I am going to stay with the same instance now.
However, have you listed your instance here? I'm sure some people are willing to pay if they know it works, since it's taking away so much trouble https://directory.btcpayserver.org/#type=Hosted+BTCPay
Thanks I'll check it out.
@pretyflaco did this video for blink+btcpay server about using the blink plugin with their new non custodial wallets.
He says that the plugin is updated to support the non custodial options.
Many thanks! So I guess things could stay unchanged: WooCommerce + BTCpay server + Blink.
Another thing that annoys me is that it's harder to pass Blink's verification with a burner number now. Has anyone found new tricks? ( I don't know should I even ask this in public 😹 )
With the new Spark Blink you can connect a BTCpay. You have instructions right into the app. You have to do the migration.
The bad thing is that Blink now uses Spark soooo:
You have been warned. Is time to ditch all these crap things, especially boycott the fucking spark.
warning received. 👀
You used Blink, a custodial lightning wallet. Spark has better trade-offs than custodial lightning.
bullshit. Is a sidechain pretending to be bitcoin through submarine swaps. A dangerous thing.
IT'S A TRAP WHERE MANY WILL FALL.
It's a statechain, not a sidechain like Liquid.
same shit.
At least a custodial service is sincere and tells you: these are not your coins meanwhile are in our custody. So user take the decision based on a truth not a lie.
Also let's never forget WHO is behind that Spark crap; the Marcus family, mafia.
I haven't been using blink, but maybe such verification with a phone number won't be requires for the non custodial option.
KYC will come later, when will be applied to all spark providers.
Now is the trap being advertised as "non-custodial". LIES
Why Blink choose this path?
As Darth will no doubt point out, I seem to have a fascination for these trustodial setups.
I suppose it's all in the name of convenience and navigating regulation.
There seems to be a big chunk of users who do not want to run a lightning node and probably who do not want to manage channels.
Phoenix kinda solves it but phoenixd still means running a server.
Ecash solves it but then who is going to run the mint?
Bark and arkade solve convenience, but users still need to come online every month or two weeks and the unilateral exit isn't exactly easy.
Spark solves it but it seems like it's almost the same as custody. It seems to me that the tradeoffs between Spark and plain vanilla custody are more or less the same.
The big problem is that people talk about Spark like it's not custody. Which was what everyone used to dislike about ecash, if I remember correctly.
Do you see a strong difference between Blink's custody option and Spark?
I think I'm going to start calling preferring a custodial lightning wallet over Spark LNDS: Lightning Network Derangement Syndrome.
Thanks for not being part of the derangement.
is a fiat business with investors
deleted by author
https://twiiit.com/BtcpayServer/status/2079943462992969948
I thought this @nitter bot is gone.
@ek
it was gone, now it’s back, powered by NixOS and no longer suffering from bots filling up my server’s disk space by downloading git archives
I have been using Luna node for about 9 months now. I don't recall whether your "light" kyc description still applies.
I remember they asked for a number to verify; are you happy with it after 9 months?
I am. I use woocommerce on a wordpress site, and BTCpay server is connected to my LND node. I do also have an open node option for the few people who have problems with BTCpay.
OpenNode is pretty solid, and the 1% option they ask for is fair. On our side, we offer options at checkout so customers can choose what best works for them.
isn't OpenNode require KYC?
deleted by author
Just checked your site, interesting setup, but isn't it a bit redundant having both? may I know why people would have problems with BTCpay?
I don't know. Maybe @SimpleStacker can weigh in. I know he has mentioned this in the past.
it has just failed to work for me on multiple occasions. I never figured out why. might be something about my browser settings? or maybe I just had bad luck
Failed to pay? maybe wallet problem? I haven't run into any issues with BTCpay so far.
BTCpay server is not the only solution. Have you thought about other alternatives like LNbits?
Or do you prefer to stay with BTCpay?
Another option is that you switch BTCpay instance provider, there are many out there #1272207
I would prefer to stay with BTCpay, keep things simple. Did you find out any good solution?
Ok, that makes sense. Just try to find the BTCpay instance that fits your needs, and in the best-case scenario you could also consider running your own instance in a vps
I was actually also considered this, but not sure I'm technically enough. 😹
Learning towards sovereignty does not have any collateral effects, apart one: you'll never look back 🤣
I got an Umbrel node sitting at home, but the whole Cleanet and Tor thing is too much of a headache for me.
these days there are some apps like TunnelSats that make the clearnet setup really easy. When you have some time...
It is very easy.
Tunnelsats umbrel app?
Obviously I got a lot to catch up on, thanks both! @AG @siggy47
Indeed, I tested a few of them, some required admin approval, some charged for monthly fee to use, which I am okay paying. But I am trying to see if anyone has found a good one here, and which one are you using atm?
We are with btc.aw and they offer NWC. We have it indeed connected with @Rizful
Our go-to is Lunanode. I can't remember if they ask for much information but setup is super easy and you can pay for the server in BTC.
We had some luck connecting CoinOS to BTCPay Server recently. If you are running the BTCPay Server, it may be worth it to run a Lightning node too (LND or Core Lightning), since you'll have a server already.
interesting, with NWC?
BTCpay works with NWC backend.
Rizful provide NWC connection and also they have a nice guide how to connect to BTCpay on their website,.
I know, but the hosted BTCpay that I'm currently using doesn't support it, literally no NWC. 👀
Did you add the plugin?
https://docs.megalithic.me/using-rizful/use-btcpay-server/
I can't add it, since I'm not admin. 👀
I tried it with another hosted BTCpay with Rizful before, it works well indeed, but that hosted BTCpay is not being maintained well, so my problem isn't really about integrating with Blink or Rizful, but the hosted BTCpay server. 😹
Sounds like a good time to future proof your setup.
I'd avoid migrating twice if you can.
Looking forward to seeing what setup people are happiest with.
Feels like the ecosystem is shifting pretty quickly right now.
WooCLINK connects Woocommerce to a Lightning.Pub: https://github.com/WoompaLoompa/woo-clink
There's also a CLINK plugin for BTCPay if you want to keep BTCPay itself: https://plugin-builder.btcpayserver.org/public/plugins/clink