Hello nate, Am 2004-11-14 11:46:57, schrieb nate@xxxxxxxxxxxxxxxx: > I'm creating a subscription service where customers will signup and pay $X > per month to have access to this service. I've done the easy part, which is > communicating back and forth with paypal. Anytime a transaction is made, > it's sent to my ipn.php script. The part I'm having difficulty with is > figuring out how to manage who does and doesn't have access to the service > based on what paypal sends me. > It looks like there are 6 different transaction types possible for > subscriptions. > For example, what if someone cancels their subscription? I don't think I can > turn off their service immediately because their month might not be over > yet. This is handled by you and your program... > Another thought. Would I just mark their account active if they are > "subscr_signup" or "subscr_payment" and leave it at that unless paypal tells > me otherwise (from subscr_failed, or subscr_cancel, or subscr_eot). OR > should I record the date of the "subscr_signup" or "subscr_payment" and only > allow them access for one month after that date? The last one... I do not use paypal but a bank (VISA/Master/...) and I let my $USER pay for 3m, 6m. After this time the account will expire. For the 1m I using auto-renew and I have the permission to make banktransfers automaticly. If the bank reject, the Accout expires... ...and if not it will be renewed 1m. > Anyone have experience creating something like this? Would really appreciate > hearing how you did it. Or if you haven't, but have ideas, let me know! > > > Thanks! > Nate Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Attachment:
signature.pgp
Description: Digital signature
