[kjmr]

I wouldn't want to give my credit card info to a CLI. When it's on the web I can see if the connection is encrypted, I can (usually) see who the payment processor is (like Stripe). What happens with my credit card number that I enter into the CLI? How is it sent, where does it get stored, etc.

You also wouldn't be able to support Apple Pay or Google Pay, or international payment methods (like iDEAL in The Netherlands).

Payments seem like a huge problem to go pure CLI without a web UI.

[las_nish]

I agree with you. What if the CLI tool used a Stripe payment link for the subscription? Let’s assume the app is called ABC. When a user enters ABC in the terminal, they would see options like accessing the customer portal, deleting their account, etc. Since it’s a developer-focused tool, what are your thoughts?

[kjmr]

Yeah, you'd have to outsource the payment processing completely to a third party, which handles everything like updating payment methods etc. Stripe payment links might work well, although I have no experience with them.