Seems like there's a simple solution to this: I have a calendar item that pops up every month and reminds me to check my balance.
When it gets low, I recharge it with enough to last me for anywhere from 3-12 months at a whack because sometimes I'm busy when the reminder pops up. It's worked pretty well for a long time now...and when it didn't, I have a reasonably configured mail system and I get several messages from Colin reminding me that I forgot for several months in a row. Failing all that, I'm pretty sure tarsnap will start failing backups, and if I'm a competent geek, I'm monitoring cron output for failures...especially when it deals with the ability to recover data in a disaster. If there was a way to store a card and recharge based on settings (maybe "When my account balance drops below $x, automatically charge $y to the card") I would probably use it...but I couldn't care less if it got implemented or not. -A On Thu, Mar 7, 2024 at 9:09 AM Michael Sierchio <[email protected]> wrote: > > On Thu, Mar 7, 2024 at 11:55 AM Jeffrey Goldberg <[email protected]> > wrote: > > >> ... I am extremely sympathetic to focusing on the core service instead of >> having to build, maintain, and protect systems that store secrets needed >> for payment. >> > > There is no need to store payment information. A token corresponding to a > user is all that's required for payment systems (of which there is a > multitude). Even enrollment doesn't require a merchant to capture or even > see credit card information. > > This is what most merchants do – focus on their core business and > outsource payment processing. > > One could argue that autopay is less disruptive and intrusive than having > an account deleted. > > – M >
