Subscription service

Jump to bottom Edit New page

inspiran edited this page Feb 14, 2011 · 2 revisions

Home > Use Cases

A customer can purchase a subscription to a website by:
- Selecting the level of access (ie. micro, small, medium) and the period of renewal (monthly, yearly)
- Select payment type and giving payment info
- When payment transaction is successful
  - the access level is set for the user
  - The user renewal date, with duration and rate, access level and non-payment access level is set for the user in the subscription payment pool
- A cron task is executed on a daily bases to run a command to find payments needing processing
  - Payments are processed using payment information on success the access level is set for the user
  - Failure follows rules set for lack of payment (email, restricted access, put back in queue, etc)