Developer implementation checklist

Changed the application's payment method to "based on usage" in the developer panel

Defined and published a price list visible in the application description

Implemented logic for tracking customer usage

Implemented multiple charge submissions during the cycle (in line with usage)

Implemented reading of next_invoice_day to monitor the billing cycle

Implemented customer limit validation (no ability to charge above the limit)

Determined and described in the terms of service the rules for changing the limit during the cycle (proportional / from the next cycle)

(Optionally) Determined a minimum limit and validation at purchase and at limit change

Performed end-to-end tests: charge submission, limit retrieval, behavior on cancellation and repurchase

Verified handling of the first paid cycle after the trial ends

(Optionally) Defined package plans (tiers) along with their corresponding limits

Implemented in the application interface information about the need to change the limit in the IdoSell panel after selecting a plan

Determined and described in the terms of service the timing of when a plan change takes effect (immediately / from the next cycle)

Verified that the charge consistent with the new plan is submitted only after the limit has actually been changed in the IdoSell panel