It should be as implement any “recurrent payment” as a banking procedure. Viewable in their apps or in the office. And being able to just cancel them at any time with your bank.
App or website? They’re talking about rolling their own code to interface with the public API of whatever service is being talked about. That’s a boatload of effort to fix something that shouldn’t be a problem to begin with.
I mentioned rolling my own code because we weren’t yet discussing the average user. Iff the time has come to make it easy for the average user, then I’d want to create an app or website instead.
Which would in turn require revenue for hosting and development. Meaning either ads, or monthly payments.
I’d rather not pay you for a service which shouldn’t need to exist. And it could be done away with by requiring an easy “cancel subscription” button which requires no hoops to go through.
You’re already paying for automated payment infrastructure; it’s just included in the price of subscription products.
The cancel subscription requirement is also very reasonable IMHO. But that makes it difficult for average users to see how many subscriptions they’ve got active; who’s currently authorized to withdraw money from their account. The default remains keeping the subscription active.
That sucks. I’d rather just pay it manually every month, or with a script running on my end.
That sounds fun and convenient to manage for the average person…
/s
our fanatical obsession with convenience (and corporations exploiting that) is what created this mess.
Autopay is so expected now that many subscriptions simply don’t offer options to pay per month.
It should be as implement any “recurrent payment” as a banking procedure. Viewable in their apps or in the office. And being able to just cancel them at any time with your bank.
“Having to use this app or website is too hard. It would be more fun and convenient to jump through whatever hoops the gym decides.”
App or website? They’re talking about rolling their own code to interface with the public API of whatever service is being talked about. That’s a boatload of effort to fix something that shouldn’t be a problem to begin with.
I mentioned rolling my own code because we weren’t yet discussing the average user. Iff the time has come to make it easy for the average user, then I’d want to create an app or website instead.
Which would in turn require revenue for hosting and development. Meaning either ads, or monthly payments.
I’d rather not pay you for a service which shouldn’t need to exist. And it could be done away with by requiring an easy “cancel subscription” button which requires no hoops to go through.
You’re already paying for automated payment infrastructure; it’s just included in the price of subscription products.
The cancel subscription requirement is also very reasonable IMHO. But that makes it difficult for average users to see how many subscriptions they’ve got active; who’s currently authorized to withdraw money from their account. The default remains keeping the subscription active.