It's also not great when they're devalued over time. They serve a couple useful purposes though, even from a consumer's perspective (unless we fix enough other

It's also not great when they're devalued over time. They serve a couple useful purposes though, even from a consumer's perspective (unless we fix enough other broken things about our payment infrastructure). There's an inherent conflict between convenience, security, transaction fees, and the chance of not being paid (or for online services like this, the guarantee that somebody orchestrates millions of accounts to distribute a compute load while fully expecting to never pay a dime) when dealing with very frequent or very small transactions. Other options Adobe might have considered include: 1. Don't offer the feature (if the feature is good enough to tolerate company currency then this seems like a worse option) 2. Pay per use (high transaction costs, high friction if you don't store payment details, low security if you do, risk of default if you batch uses over time, ...) 3. Monthly subscription giving unlimited uses (not tenable for AI that has very real compute costs associated with it, you'll have users abuse the limits) 4. Monthly subscription with a max number of uses (just a different way to pay for credits, strictly worse than buying credits and having them last indefinitely) 5. Batch uses over time, bill if they exceed a threshold (lowers transaction fees, increases security, increases consumer goodwill, vulnerable to targeted attacks) And so on. Do they actually have any good options, or are they choosing between a bunch of least-bad solutions? I ask partly because I was planning to use a similar model of charging up-front for credits for an unrelated service because I thought it would be the most consumer-friendly in that domain.