Edge cases — points to note

Situation	Effect / recommendation
The developer does not submit any charge in the cycle	No basis for billing — the customer will not be charged anything for that cycle
The developer submits several charges in the cycle	Only the last submitted charge counts
The charge amount exceeds the customer's limit	The operation will be rejected — the customer cannot be charged above the declared limit
The customer tries to set a limit lower than the minimum (at purchase or during the subscription)	Operation not allowed
The customer tries to change the limit to an amount lower than the charge already billed in the current cycle	Operation not allowed
The customer cancels during the cycle	The subscription remains active until the end of the cycle; billing follows the last submitted charge
Repurchase of the subscription after cancellation	New billing cycle, newly declared limit, charges counted from scratch
Limit change during an ongoing cycle (increase)	The billing method (from the new cycle vs. proportional) depends on the developer's decision — must be described in the application's terms of service
The customer selects a package plan in the application but does not change the limit in the IdoSell panel	No basis for billing — the charge consistent with the new plan can only be submitted after the limit is changed in IdoSell
The customer tries to set a limit in the IdoSell panel that does not match any existing plan (e.g., any amount between Standard and Pro)	To be determined by the developer — may require additional validation on the application side if plans are meant to be billed strictly "in brackets"
Downgrading a package plan below the minimum limit	Operation not allowed — the same rules apply as for a standard limit change below the minimum