Product feedback

After the customer has already started a subscription, they may want to change their payment frequency from monthly to weekly, fornightly, annually for example (any number of times). Billing period should be able to change while the subscription is already active, and if they are prepaid, any change would take effect at the end of the period they have paid until. If appropriate, the period should be prorated so they don't pay more or less than required if changing multiple times.

Ability to pause and resume subscriptions (sometimes after several billing periods) via the API and user interface as well. If a subscription is paused, the customer should not be billed. If the subscription is resumed over the course of a billing period, fees should be prorated.

It would be awesome to upload html templates per Organisation for the invoice creation to match the orgas look and feel.

Currently, a customer can only have one active payment method linked to their Lago account. It would be useful if Lago could manage multiple payment methods for a customer (e.g. method 1 used to pay for subscription A, and method 2 used to pay for subscription B).

If Lago detects a lost dispute linked to a wallet top-up transaction, the credits should automatically be voided. Fraudulent users should not be able to keep their wrongfully acquired credits.

Some times, we need to charge an item once only such as integration fee for a specific feature and we don't want to send 2 invoices to our customer but one invoice with the subscription fee, the usages and the one-off items.

Currently Lago does not provide any options to delete past event data. But in production this leads to accumulation of events data and soon database size increases to tens of GBs. It'll be helpful if there is an option where retention time can be specified, which routinely deletes old events(for example events older than 1 year) making database manageable and cost effective

for a subscription, I'd like to specify the debit date and change it throughout the subscription life if necessary

We currently query the current usage endpoint to determine whether a customer should still be able to access some features based on their plan and allowance. It would be easier if Lago could alert us when a customer has used up their usage quota.

It’s currently not possible to top up a wallet using a different ratio than the one defined. However, this flexibility could be very useful — for example, when a customer purchases credits at a discounted rate.