I have need and not sure AMember can do it out of the box. Product 1 - Free gets you A Product 2 - $9.95 per Month - Gets you A and B Product 3 - $19.95 per Month - Gets you A,B and C If I set up the products A,B, and C and a user signs up for B, then wishes to upgrade to C how can I get Amember to not bill them monthly for B and C? I need C to cancel B. If not out of box feature then I need to start coding. Don
Yes amember can do this right out of the box. You can charge 0 for product a 9.95 for product b 10 for product c Set a dependency that requires a user to have subscribed to b before being allowed to purchase c ths handles the upgrade options. If a user purchases C to begin you can have a product that contains a,b and c all in one for 19.95 Product B and product c and an all in one product d (a+ B + C) all give access by default to A ================================ Just reread what Id written and it might not be clear... so to put it a little clearer. Set up Product A (free) gives access to directory A Set up product B ($9.95) gives access to directory A and B Set up product C ($10) - this is the upgrade option from B ---> C. It has a dependency set that user must be subscribed to B before they can purchase this option. It gives access to directories A,B and C Set up Product D (19.95) that is a straight out purchase of product C from scratch. It gives access to directories A, B and C Set a dependency on Product D that it cant be purchased if you are already subscribed to B or C (that way a member cant accidentally be charged twice
Hello, The cancellation of a rebilled product is the tricky part and will be payment system dependent. It depends on if amember is in charge of the rebill (i.e. credit card info stored locally) or is 3rd party payment system in charge of rebill and amember notified after the fact. If its the latter then I believe the user has to cancel the contract manually. I use CCBill and a rebilled product will show a cancel link in the members page. If you hit cancel it only takes you to CCBills customer support page where the user has to enter the subscription_id and one other form of identification in order to cancel the product. It is not an automated process. So check how your payment system handles rebills. It would be nice if someone did a write up on how all the payments systems handled rebills because I suspect that everybody has to do this research or at least you should before setting up your payment systems. Jimmy
Thank you. I've been looking for the setup for this and can't find it. Where would I setup such a thing? Don
Agreed! I have 2 amembers set up. One is a straight forward to phpBB but this new one will require the routine I described. I have yet to sign the second billing up and would like to know which one would allow this and which one will not. Don
Yes the solution mentioned by Steve would work. As a user though if I purchased a standard membership and then upgraded to a premium membership and I saw two separate charges on my credit card bill every month it would bother me. It wouldn't matter the price(s) it would just bother me. I would wonder why CCBill was so stupid and couldn't just bill me 1 price for the premium membership that I subscribed to. But thats just me I am an anal person. Jimmy
I somewhat agree with Jimmy on seeing double charging (albeit for the correct total amount)and it would be nice if amember had an upgrade dependency section whereby if you signed up for product c then product B was unsubbed. Unfortunately that doesnt exist at this time so its basically a work around method. Not pretty but it works. One of the problems in the scenario is that with payment processors that keep the billing details on their own servers is that amember would need to somehow be allowed to cancel payments on the processor. With payment processors that keep the billing details in the amember database this upgrade dependency scenario would work fairly seamlessly. The downside of keeping credit card and billing details on your own server is you are a target for hackers
I echo exactly what Steve said. Using a payment system where the credit card info is stored in Amember offers the most flexibility. With this solution you can make anything work pretty much flawlessly. But this flexibility comes with a price in that it is your responsibility for protecting their credit card information. I personally would not feel comfortable doing this especially when the server was not at the same physical location of where my business is. To be honest I am really suprised that there are payment processors available that Amember supports that even offer this as an option where the credit card information is stored locally. I'm a senior software engineer and I could not look someone in the face and say I could 100% guarantee that my server cannot be hacked and information compromised. Again thats me I am anal and very paranoid. Jimmy