pull down to refresh

126 sats \ 6 replies \ @tomlaies 4 Jul \ on: New major release! Phoenix Android/iOS/Server now supports BOLT12 lightning
I feel like Bolt12 on Phoenix could almost replace BTC Payserver. Just a static QR code for payment then then some kind of REST request to Phoenix if it has been payed?
write
preview
13 sats \ 5 replies \ @moneyball 6 Jul
refunds? accounting?
reply
4 sats \ 3 replies \ @k00b 6 Jul
If the app can call a webhook on payment, then you could do that in some other system.
reply
13 sats \ 2 replies \ @moneyball 7 Jul
Right, like BTCPay :) (or, Zaprite)
reply
0 sats \ 1 reply \ @k00b 7 Jul
Do BTCPayServer or Zaprite allow your lightning keys to live on your phone? I'm not too familiar with either. That's the main advantage here I guess.
reply
100 sats \ 0 replies \ @moneyball 7 Jul
That's a goal with the BTCPay app project https://github.com/btcpayserver/app
There's been some discussion of a BOLT 12 protocol modification to allow for Zaprite to integrate with merchant LN wallets.
There's of course all the challenges of mobile including availability to sign to receive money. Async payments protocol helps but whether applicable to a merchant depends on the volume and type of merchant.
reply
0 sats \ 0 replies \ @tomlaies 7 Jul
You're right that a static QR code and a webhook into payment history is not quite there to be a fully fledged payment system. That's why I said "could almost" - because it can already do a lot, enough for some usecases, of course not everything.
reply