Re: How to implement a yearly subscription system
SubZero
Hello,
Since the release of our software in mid-2003, we have not
re-asked for money from customers--they have been using it with just
one payment and that's something we did not promise. We want to have
them charged every year for updates beginning from 2008 and to do that, we
need to
get the code rolled out on January 2007. What we need,
1) A shareware component that is capable of expiring paid customers
every one year in case they update to a newer version (they should not
be asked for money if they keep using the old version but if they want
to update to the latest version unless the 1 year period is not over
OR if they get a new license, they should not be allowed to do so)
2) This component's keys should be supported by/producable by
share-it/esellerate (share it is better).
Does anybody know of a good shareware protection system that can do this?
Best Regards,
SZ