Implement pricing model for LRS based on the statements per billing period.

- Learnexa - All the sites will have the same subscription period (which is configured at super site.)

- LRS - As expertus one customers each of them may have different billing periods (some may have annual, some may have quarterly), each site's billing period is configured differently per site.

- Super admin can set offline payment to any subsite under site subscription page(This will be like flag super site admin can set it, if it set's true to any subsite that site should not have the “subscribe now” notification bar)

LRS pricing model implementation is similar to learnexa pricing model, Subsite can be billable based on the statements per period. So the plan is similar to learnexa where admin can set the subscription setting, subscription plan and that can be used for subsite subscription. If the price of the subscription changes then the user shall be notified, A User will have an option to Un-subscribe at any time. User can change the pricing plan either by the end of the period or middle of the period.

Trail period

There will be a trail period for few days that can be configured by super site admin in the subscription settings under the site subscription tab.

Subscription

There will be a various subscription plan which can be created and maintained by the super site admin. Super site admin can assign the default/custom subscription to the subsite. Subsite admin has to subscribe in order to use the site and the statements,Which is similar to learnexa. eg:

a) FREE - 500 Statements - $0.00
b) PlanA - 2000 Statements - $20.00
c) PlanB - 5000 Statements - $40.00
d) PlanC - 10000 Statements - $70.00

Subscription Type

a) Day
b) Week
c) 2Week
d) Monthly
e) Quarterly
f) Yearly

Overage Statements

Statements count will be tracked, if the statement count exceeds the subscribed plan count, overage statements will be notified to the user and that will be billable, The overage statement and the pricing information will be shown under the Billing tab, Subsite admin has to pay it from billing page.

The following Models will be used for Implementation

class Company < ActiveRecord::Base
  #This model already exists just add below association
  belongs_to :site_subscription
  has_one :merchant_account, :as => :owner
  has_many :statements, :through => :client_applications
  has_many :site_orders, :through => :site_subscription
end

class SubscriptionSetting < ActiveRecord::Base 
end 

class SubscriptionPlan < ActiveRecord::Base
  has_many :site_subscriptions
  has_many :site_orders
  has_many :site_custom_plans , :dependent => :destroy
end

class SiteCustomPlan < ActiveRecord::Base
  belongs_to :subscription_plan
  belongs_to :site_subscription
end

class SiteSubscription < ActiveRecord::Base
  belongs_to :subscription_plan
  has_one :company, :dependent => :destroy
  has_many :site_orders
  has_many :site_order_items, :through => :site_orders, :dependent => :destroy
  has_many :payments_made, :class_name => "SitePayment", :foreign_key => "payer_id"
  has_many :site_usages
  has_one :site_custom_plan, :dependent => :destroy
  has_one :custom_plan, :through => :site_custom_plan, :source => :subscription_plan
end

class SiteOrder < ActiveRecord::Base
  belongs_to :site_subscription
  belongs_to :subscription_plan
  has_one :site_payment, :dependent => :destroy
  has_many :site_order_items, :dependent => :destroy
end

class SiteOrderItem < ActiveRecord::Base
  belongs_to :site_order
  belongs_to :item, :polymorphic => true
end

class SitePayment < ActiveRecord::Base
  belongs_to :site_order
  belongs_to :payer, :class_name => "SiteSubscription"
  belongs_to :user_paid, :class_name => "User", :foreign_key => "payer_user_id"
end

Table Name: companies(This table already exists. Just add following columns)

Table Name: subscription_settings

Table Name: subscription_plans

Table Name: site_custom_plan

Table Name: site_subscriptions

Table Name: site_orders

Table Name: site_order_items

Table Name: site_payments

Table Name: site_usages

Saves the statement details for each and every billing cycle at the end of the billing cycle.

Wepay payment gateway will be used for payment subscription similar to learnexa.

When company purchases subscription

1. Create a record in site_orders and site_order_items. At present the items for an order will always be 1 viz. subscription. Set payment_status = NIL
2. Generate the parameters that need to be sent to payment gateway and based on those parameters and the site_order_id create a record in site_payments table. Set 'status' column to NIL. After the response from the gateway is received, update the 'response' column of site_payments and based on the success or failure update the 'status' column. Also update the payment_status column in site_orders table to proper value i.e. success or failure.
3. Also if payment was successful then update the site_subscriptions table with proper status, preapproval_id and last_payment_id and last_payment_status

1. Similar to learnexa
2. Enabled - When the site subscription is enabled subsite admin has to subscribe before the trail period expires inorder to use the site, Default option Enabled
3. Disable - When the site subscription is disabled, subscription status will be active and the site has no more payment required, site can be used as it's

1. Similar to learnexa

Offline Payment process

1. Offline Payment mode option will be listed to each subsite under site subscription page
2. Super admin can set the offline payment to any subsite, If it set's true the normal “subscribe now” notification bar and the payment flow will not be shown to the subsite
3. Email will be sent to the subsite admin from super admin via backdoor with the required details and the payment will be done through offline
4. Once the payment is received super admin will have the option to mark 'payment received' to the site for the corresponded subscription period.
5. Site will not be suspended on overdue
6. Super admin will have option to view all the subsite billing history under site subscription
7. Super admin can cancel any subsite subscription from both offline/online payment mode

1. We can disable the indivitual subsite site subscription from subscription settings or we have the backfill which will disable all the site subscription(bundle exec rake backfill:disable_all_existing_site_subscription)
2. We can completely hide the site subscription from super admin page by changing the settings in settings.yml(disable_site_subscription: true)
3. After this setting if we create new subsite those sites subscription will be automatically disabled by default

When the user upgrade the subscription in the middle of the subscription period,

1. Do we need to upgrade the subscription plan immediately or when the current subscription period ends?

» Uday: For now, this just works like learnexa, plan features are upgraded immediately but users are charged extra amounts only from next billing cycle. Will confirm this with Murali.
» Murali: Correct

1. Please confirm the above offline payment process flow

1. Add delayed_job and rufus restart task in the deployment steps
2. Run all the Backfill task in server
3. configuration file changes in development.rb/staging.rb/production.rb - Add PUBLIC_URL constant

• *Backfill a) bundle exec rake backfill:create_subscription_setting b) bundle exec rake backfill:populate_site_subscription_plans_default_values c) bundle exec rake backfill:create_site_subscription_for_default_company d) bundle exec rake backfill:create_site_subscription_for_existing_companies e) bundle exec rake backfill:create_or_update_supersite_wepay_account f) bundle exec rake backfill:disable_all_existing_site_subscription Files to remove from svn track**

  a) public/javascripts/base_packaged.js
  b) public/stylesheets/application.css
  c) public/stylesheets/base_packaged.css
  d) public/stylesheets/client.css
  e) public/stylesheets/columns.css
  f) public/stylesheets/forms.css
  g) public/stylesheets/ie.css
  h) public/stylesheets/layers.css
  i) public/stylesheets/lightbox.css
  j) public/stylesheets/panels.css
  k) public/stylesheets/site_frame.css
  l) public/stylesheets/tabs.css
  m) public/stylesheets/tincan.css
  n) public/stylesheets/typography.css