That's interesting. If we did this we'd obviously create a "create product key" action, but would there be other actions you would need / find useful?
Zapier integration
Would you consider writing an integration to Zapier? That would enable quick and easy (code-less) access to at least 15 payment processors - https://zapier.com/zapbook/#sort=popular&filter=payment-processing
heaps of ecommerce apps - https://zapier.com/zapbook/#sort=popular&filter=ecommerce
...with one deployment.
Because it's not like you're busy with a brand new version or anything 😉
cheersEwen
It would be good to be able to change the expiry for existing licenses - use case: monthly subscriptions, so if the user paid via Stripe (or similar) then their subscription expiry date could be updated. I would probably use their email address as the identifier, or another *secure* unique identifier that you'd recommend that I can obtain from the app that matches a LimeLM database field.
The rest of this is just me thinking out loud, feel free to ignore it because I'm tired...
I initially thought of extra floating licenses but this is more of a hands-on enterprisey thing (for my current app) rather than something that needs scaling, so scratch that, maybe. Others could have a use for it.
Another disposable idea: Is there such a thing as an activation start date? Edge case: a customer pays for a subscription but doesn't want it to start until x/x/xx. Actually, that sounds more like a means-test to fire them. Scratch that.
Yes, it's something we're strongly considering. TA 4.0 is coming first (very soon), then the LimeLM interface revamp, and then maybe after that.
It's something we've considered, but haven't devoted any resources to. Our engineering resources have been devoted to things that we believe can provide a better experience for our existing customers and attract new customers.
Honestly, we're not sold on it. You can already automate license key generation and renewals. And we have pre-written examples in 3 common programming languages (and a web API that can be used in any other programming language). And you don't need a Zapier subscriptions to use it.
I think any effort we into making the "macro process" (order flow, renewal flow, etc.) easier will be integrating directly with the payment providers, etc. (rather than through an intermediary like Zapier).
And, of course, you (or they) could use the LimeLM web APIs directly from Zapier. We just haven't spent the engineering resources to make that happen (and it's so low on the priorities because the demand is tiny).
Is there something difficult for you that you think we can do better?