FastSpring + LimeLM Yearly Subscription

First, thank you for the very informative web content and guides to set things up. Everything is very helpful and the API is easy to use.

I have a .NET application that I plan to sell via FastSpring. The product will have an ANNUAL subscription fee with free updates. I followed the guide and successfully generated license keys via FastSpring using the PHP code example provided.

I would like for keys to expire after 365 days, which is how I set the product up in FastSpring. Correspondingly, in browsing the forum, I found the follow code for :

$feature_names = array('expires'); $feature_values = array(date('Y-m-d', strtotime('+365 days')));

Next, in my wyday account, I created a Custom License Field for "expires" and set the type to "Date/Time." Therefore, the license key will expire at the same time of the FastSpring subscription.

My question is 2 fold:

1. Is this approach appropriate? I do not want to build a script base on my server. If a user cancels their subscription, the license remains active for the rest of the year, which is fine. So, everything is handled via LimeLM + FastSpring cloud for fulfillment.

2. Is there any additional code I need to put in my .NET application with TurboActivate?

I'm sorry if this question was answered elsewhere. Just want to confirm before I start with the development and commitment to FastSpring + LimeLM.

Thanks!

Forgot to add... I would of course add in my app the following per the guide on field codes. Does this get me there without additional server side code outside of FastSpring (I don't plan to have trials)?

if (TurboActivate.IsDateValid(TurboActivate.GetFeatureValue("expires"), TurboActivate.TA_DateCheckFlags.TA_HAS_NOT_EXPIRED)){ // the updates_expires date hasn't yet been reached}else{ // the update period has expired}

First, thank you for the very informative web content and guides to set things up. Everything is very helpful and the API is easy to use.

Thanks, that means a lot.

Does this get me there without additional server side code outside of FastSpring (I don't plan to have trials)?

Yep, that all looks good.

I confirmed with FastSpring that the license fulfillment will refire at the end of the annual subscription in the customer's FastSpring account and a new license will be generated (along with the Custom License Field for the expire date). Therefore, it appears this fulfillment workflow will work. 😀

Only drawback is that they will have to enter a new license code, which is not too bad since this will occur only once per year.

If you have any other suggestions to make the workflow better or more optimized for the customer, please let me know. Thanks!

I confirmed with FastSpring that the license fulfillment will refire at the end of the annual subscription in the customer's FastSpring account and a new license will be generated (along with the Custom License Field for the expire date). Therefore, it appears this fulfillment workflow will work.

Well, you might want to check back in with FastSpring. I believe there's a way to not have it do that. That is, instead of generating a new product key at the renewal of a subscription, you can instead take another action. And the other action you should take is to change the custom license field for the product key.

Reply
Discard post