An LNURL-withdraw link with a specified number of withdrawals and delay/interval between when the next withdrawal is allowed could achieve this. There may be a better solution, but that’s one that comes to mind.
Is there a debit authorization key available in Lightning?
If I want to subscribe to a service using Bitcoin, I don't want to keep paying monthly invoices. Ideally, I would just authorize a service to debit a maximum amount per month and let them pull funds from with my node automatically.
Maybe I can create a new Nostr Wallet Connect key and pass the NWC uri to the service provider so that they can automatically debit.
Maybe nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszymhwden5te0wp6hyurvv4cxzeewv4ej7hjm7rj can code this as part of their own monthly invoicing tool. nostr:nprofile1qqsptdw0dn05l5wq9u5tens0r972ltjv337xdglzuga0nlnppp6nzhspzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uaz3cpw
Discussion
Hum.. I didn't know people could reuse withdraws...
You can play around with the on LNbits demo site. You can sign in with nostr, and then make sure to add the “withdraw link” extension. Here’s one I created just now. It allows up to 5 withdrawals of 21 sats each, with 60 seconds between withdrawals. You can define longer delays.
LNURL1DP68GURN8GHJ7ER9D4HJUMRWVF5HGUEWVDHK6TMHD96XSERJV9MJ7CTSDYHHVVF0D3H82UNV9A5X2D3EDY6KVAMRF4RNJ5RYGDTK63F4F3N8JZ2TZNY
Very interesting! I see that you are not just a memer after all. I will try it out.
🤣🤝 I’m tech savvy enough to be dangerous and have fun. Not enough to know how to code though 😂
This would be nice, most of the reason i didn't implement nwc is because I couldn't find somewhere that would even do a monthly limit, basically, if it hits the limit, and then what? same as paying in advance or paying each time if you keep having to go somewhere to re-fill it.
there is a sketched out scheme plus a go client and mock wallet service implementation in https://orly.dev that nostr:npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw just vibe coded - i'm going to clean it up and refactor it for https://next.orly.dev when i get to that point with it.
it's simple, 30 days free for a new npub, and then 6000 (about 2 euro) sats/month (can be changed, i may add a euro or dollar based price indexer that fetches price data) for 30 days. you pay by zapping the relay's identity npub and it automatically recognises the incoming payment. i have to work on the notification scheme, which will use a "privileged" tag of some sort, probably like Z or something, which the relay will only send to a client authed to the same pubkey. i figured this could also become a way to contact the clients directly by making a little UI to write these messages. it's a bypass on the shitty state of DMs.
in the future, you will use next.orly.dev, and be happy :p
even with zapping (thats nice and frictionless), users still dont really want to think about their payments more than once (ie, they want the automatic widthdraws now, like a subscription that never turns off)
either way, im on a break from code for a bit here but ill check it out at some point 😎
yeah i still have to actually look at it lol.
also, direct debit is a dark pattern in my opinion. that's why i devised the scheme of "only visible to you" kind 1s. the user can just send whatever sats and get whatever period. it's cheap so it's trivial to think about. the idea would be that users would prefer to buy 3 months blocks or so at a time anyway. then, a week out from expiry a message appears that only they can see, that mentions them as well to ensure it comes up in notifications, reminding them to top up.
my post-paid phone service bugs me every month about shit but it does allow me to pay 3 months into my account at a time. making it lower friction would be a client side thing, where it just automatically triggers a zap periodically and maybe alerts the user if the balance of the account is too low to make the zap, purely client side of it. i don't think people would really be that bothered by whatever payment period they prefer, that's the point of it, basically works out to, at current bitcoin price, something like 200 sats a day, like 13 cents or something. as the bitcoin price goes up, their subscription would automatically extend as it would bill on a daily basis according to the exchange rate. i mean, or you could just have it fix a period. idk, the current design that was made just converts whatever the price is to the period. but if you model the micro-account as sats and change the per day price based on the exchange rate, they would wind up very often with overall a benefit to pay ahead, then you would get people deciding to opt for an annual payment and just zap 72000 at once and most of the time that would work out to like 13-14 months actually. there's options for the calculation, i think working it as a micro account is more friendly, and you can also then create an option where they can cancel and refund automatically as well, and get their remainder zapped back.
i like that idea of it being a kind of custodial account like that, i have used several VPS services that accept crypto payments but you have to hassle them to refund and cancel. i think people would like the "sats based" option in that they can get their sats back whenever they decide they don't want the service... and jump back in just as easily. having to contact customer service to get advance balance back, and it being denominated in fiat, is ugh. i can't help but think of the fact i paid when the price was lower for the sats and then my refund they are basically, if they stacked it, making money off me.
