Developer experience

We're building analytics on top of Webhooks events and found ourselves missing some metadata on Wallets. While trying to consume wallet_transaction.created events, we found ourselves missing the wallet object itself (and therefore a way to link it with the customer object). It would be great to have additional webhooks for wallet.created and wallet.updated like you guys added for customer .

Examples of messages that could be useful: Webhook when a coupon is applied to a customer account via the user interface; and Webhook when a coupon has been fully consumed.

As a user, I want to know when the plan associated with an active subscription is updated. Use cases: When a charge is added to/removed from the plan, our internal event management system needs to be notified, so that it can adapt (e.g. start sending events for a new charge or stop sending events for an old charge); When Lago subscription data is used to manage access to certain features, and free units are added to/removed from a charge, our internal entitlement management system needs to be notified, so that it can adapt (e.g. enable or disable access to a feature).

This mainly affects on-premises customers. Currently, many things have to be configured via the UI. Since we host Lago on our machines and have a deployment, it would be very nice if we could configure Lago in the right way using environment variables or a yaml configuration file.

Stripe provides tokenized card information that we would like to retrieve through the Lago API. https://stripe.com/docs/api/tokens/retrieve Showing the card type, last 4 digits and expiration date would enhance the customer experience. For instance, enterprise customers would be able to check whether they've used the right payment method (e.g. hardware card vs recurring services card).

For self-hosted users, it would be useful to have access to data points to set up Prometheus monitoring.

Allow for AirWallex Integration for payment links etc

As a developer, I want to select the types of message that each webhook URL should be listening to, so that we don't have to process a large volume of unnecessary events.

I would like to propose a feature enhancement for Lago that involves the introduction of webhooks to handle subscription renewal events. Use Cases: Allow applications to notify users via email before their subscription renews. Example: "Your subscription will renew soon. If you wish to change or cancel your plan, you can do so now." For long-term plans (e.g., annual subscriptions), there is often a need to adjust usage metrics before the renewal period begins. Example Scenario: A user has prepaid for 100 seats but plans to reduce usage to 80 for the next billing cycle. Refunds or adjustments aren't applicable during the current billing period since they’ve already paid for 100 seats. Before renewal, we would like to update the usage metrics to reflect the reduced seat count for the upcoming cycle. In some cases, we may want to perform specific actions immediately after the renewal event, such as updating internal records or triggering follow-up workflows.

To update a charge in a plan or filter value associated with a billable metric, we currently need to perform a full update of the object, which is very heavy when the billable metric/charge includes 1,000+ filter values. Partial updates would be more efficient.