Replying to Carlos

Re: cancelling subscriptions, fraud etc

The way I tried to address that is by letting the user choose 1) how much and 2) how often to pay. So for a service that's 30k sats per month, a user could pay 1k sats per day, or 30k / month, or go for 3-400k to pay for a full year in advance.

My thinking is the users who want more control can go for "smaller payments more frequently". Let's say for the user who pays small amounts per day, if the service provider rugpulls or goes rogue, worst case is the user loses 1 day of funds.

Could be I'm over-complicating things, but that's what I would do if there's a service provider I don't trust or somehow looks shady :)

Does this cover your point about fraud and cancellation issues?
Avatar
mrclownworld 2y ago

Yes and no. I am saying I personally don't ever want an automatic payment. A prompt reminding me to send a payment, great. Then I hit Pay or Decline. But automatic pulled payments are extremely fiat imo

Reply to this note

Please Login to reply.

Discussion

12
Carlos 2y ago

These would be automatic *pushed* payments, but I get your point. An optional y/n prompt, where yes results in an invoice via DM, sounds reasonable.

Avatar
mrclownworld 2y ago

I hear you. But the difference between someone reaching into my pocket to take some money and a programmable robot pocket that periodically flings my money at someone have the same issue in my mind 🙃