View previous topic :: View next topic |
Author |
Message |
mutex
Joined: 22 Apr 2015 Posts: 19
|
Posted: Wed Apr 22, 2015 12:03 pm Post subject: Subscription licensing and upgrades |
|
|
Hi,
Would it be possible to create subscription based license, which could be upgraded?
Assuming that initial authenticated license would cost $5 and upgraded version $15. E.g. upgrade would cost initially $10 and recurring payments $15. |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Wed Apr 22, 2015 11:27 pm Post subject: |
|
|
This might be possible by creating a separate variant product for the upgrade with the upgrade price. However it seems like a lot of trouble to go to for what is a transient case. You would need to validate that the user is eligible for the upgrade. You would also need to work out what to do if the user purchases the upgrade halfway through or on the 30th day of their existing subscription. The new subscription will start from the purchase date - so if you give them the upgrade price they will effectively get a period of the upgrade free. It would probably be easier to handle these cases by offering users who want to upgrade a partial refund of the existing subscription. You can then work out what the refund should be and refund it manually through PayPal. _________________ Infralution Support |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
mutex
Joined: 22 Apr 2015 Posts: 19
|
Posted: Thu Apr 23, 2015 12:01 pm Post subject: |
|
|
1. Do upgrades have to be always checked manually?
Considering that there would be product 'standard' and it's variant 'pro' which is a upgrade:
2. What are the options to differentiate these in authentication phase? ProductName, ProductInfo or AuthenticationData? I assume that I cannot (manually) change the ProductName or ProductInfo for a license key in License Manager, but AuthenticationData can be changed.
3. If IPN.NET would generate a sale for a product variant which is an upgrade ('pro'), will/can it change the ProductName associated with the license? Can it actually change anything automatically to existing license?
4. How the price will be matched after the upgrade, e.g. does the IPN.NET associate the sale with a License Key? What happens to existing sale?
I guess that there will be a new IPN Reference for the new sale, but what prevents using the old subscription and it's Reference to push payments and expiry date for the upgraded license key with standard price?
Thanks for excellent support. |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Thu Apr 23, 2015 1:20 pm Post subject: |
|
|
1. Yes. It might be possible to change IPN.NET to allow automatic upgrading of products - however this would rely on the customer having previously purchased using the same email address - which often is not the case (for our own sales I'd say more than 50% of upgrades are done using different email addresses)
2. Yes normally you would use AuthenticationData to distinguish between different license types. You can't change the ProductName or ProductInfo of an existing license key.
3. Normally your would setup different Product Variants for each of your license types and set the default AuthenticationData to contain the appropriate data eg "Pro" or "Standard". For an upgrade IPN.NET will normally issue a new license key.
4. I think subscription upgrades are going to be tricky to handle automatically, because I think it will essentially involve cancelling the previous subscription and starting a new subscription (with a sale and a new license key).
If you really want to automate subscription upgrades then you will probably need to purchase the IPN.NET source code and make some changes. _________________ Infralution Support |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
|