Example scenarios

Scenario A — standard billing cycle

1. The customer purchases a subscription and declares a limit of PLN 100.
2. During the cycle, the developer submits the current charge daily based on usage (e.g., PLN 20, then PLN 35, then PLN 42).
3. At the end of the cycle, the last submitted amount (PLN 42) appears on the customer's invoice.
4. The developer's balance is credited PLN 42, minus the commission.

Scenario B — end of trial

1. The customer's trial period ends and they enter the first paid pay as you go cycle.
2. From the first day of the paid cycle, the developer submits charges according to actual usage.
3. At the end of the cycle, the last submitted amount is billed — exactly as in subsequent, standard cycles.

Scenario C — cancellation and repurchase

1. The customer uses the subscription; the amount billed at the end of the cycle is PLN 100.
2. The customer cancels the subscription — the subscription ends at the end of the current cycle, PLN 100 appears on the invoice, and the developer receives their commission.
3. A month later, the customer orders the same subscription again, declaring a new limit (e.g., PLN 150).
4. A new, independent billing cycle begins — charges are counted from zero.

Scenario D — changing the limit during the cycle

1. The customer has a limit set at PLN 100; the currently billed amount in the cycle is PLN 60.
2. The customer wants to change the limit to PLN 40.
3. This is not possible — the new limit cannot be lower than the amount already charged in the cycle (PLN 60). The customer can set the limit at PLN 60 or higher at most.

Scenario E — minimum limit set by the developer

1. The developer has set the minimum limit at PLN 50.
2. When purchasing the subscription, the customer tries to set a limit of PLN 30 — the system will not allow this configuration; the minimum value is PLN 50.
3. During the subscription, the customer wants to lower the limit from PLN 100 to PLN 40 — also not allowed, as this is below the minimum limit (PLN 50).

Scenario F — package plan upgrade (Standard → Pro)

1. The developer offers the following plans: Standard (PLN 100), Pro (PLN 500), Ultra (PLN 1000).
2. The customer uses the Standard plan; their limit in the IdoSell panel is PLN 100.
3. The customer selects the Pro plan (PLN 500) in the application interface.
4. The application informs the customer of the need to change the limit in the IdoSell panel to PLN 500.
5. The customer changes the limit in the IdoSell panel to PLN 500.
6. In accordance with the rules described by the developer in the terms of service (e.g., "from the next cycle"), the charge corresponding to the Pro plan is submitted at the moment chosen by the developer — immediately or from the next cycle.

Scenario G — selecting a plan without changing the limit in IdoSell

1. The customer selects the Ultra plan (PLN 1000) in the application interface but does not change the limit in the IdoSell panel (the limit remains at PLN 100, corresponding to the Standard plan).
2. The developer cannot submit a charge of PLN 1000, as it exceeds the customer's current limit set in IdoSell.
3. Billing consistent with the Ultra plan is only possible once the customer actually changes the limit in the IdoSell panel.

Scenario H — plan downgrade with a minimum limit set

1. The developer has set the minimum limit at the level corresponding to the Standard plan (PLN 100).
2. The customer uses the Ultra plan (limit PLN 1000) and wants to switch to the Free plan (PLN 0).
3. Changing the limit in the IdoSell panel to PLN 0 is not allowed, as it is below the minimum limit (PLN 100).
4. The customer can at most go down to the minimum limit level, i.e., effectively to the Standard plan — the Free plan is not available to them in this case.