Product feedback

Let's imagine that Group A has its main entity in France, and two other entities in Spain and in Germany: Each entity may have its own contract (i.e. one subscription per entity), in which case, even if the subscriptions are renewed at the same time, they shouldn't be consolidated. There may be a different payment method for each entity. In addition, Lago should provide aggregated billing data at the group level; or There may be a group contract (i.e. a single subscription that covers all entities), in which case the fees on the invoices should be broken down by entity. Invoices are sent and paid by the main entity.

It'd be nice to see wallet topup rules in the UI so we can glance at did someone set a rule for their wallet

Our business team wants to restore an overwritten values in a subscription back to the values of the original plan. It would be great if there was a single button to do that instead of having to revert each value one-by-one.

We'd like to avoid small $1 transactions in Stripe and impose a minimum $10 amount for wallet top-ups

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

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.

This would be helpful to get metrics around dunning campaigns, such as -recovery rate -average time to collect -payment success rate -bucketing by timeframe (e.g. day)

Ability to send Lago invoices automatically to Pennylane (accounting software) via native integration.

This request is to add invoice.payment_success webhook. Currently, Lago only has a webhook for invoice.payment_failure. The only way to figure out if a payment is successful is to leverage the PSP's webhook (like stripe). It would be easiest to interface with just one API instead of multiple.

When a subscription is set up with a start date in the past, Lago assumes there is no need to generate invoices for periods prior to today. We would like the ability to manually create invoices for these periods in the past.