Hi there!

Lago delivery: here comes v1.2.1! 🚚💨

Filters for billable metrics

We've made changes to our dimension system and replaced metric groups with filters.

This new feature offers greater flexibility as:

👉 You can now create as many filters as needed (no longer limited to two dimensions); and

👉 You can define specific rates based on very granular filter combinations (e.g. online card payments with Visa cards, offline card payments with Amex cards, etc.).

Learn more

Minimum plan commitment

When creating a plan, defining a commitment ensures a minimum invoice amount for the billing period.

This minimum is calculated at the end of the period, taking into account the subscription fee and all usage-based charges.

Learn more

Google SSO

You can now sign up and log in to your Lago account through Google single sign-on (SSO).

This enables a better experience and ensures that your identity provider remains the system of record for authenticating users.

Learn more

We're hiring 👋

We're looking for new talents to support our growth and help us build the best billing product for our community.

Looking for a new challenge? Click here

Improved trial period

For plans with a subscription fee paid in advance and trial period, the first invoice was initially generated when the subscription started.

Following feedback from our users, we have modified this logic to generate the first invoice at the end of the free trial.

Learn more

Payment disputes

If a payment dispute is reported as lost by the payment provider, Lago will automatically mark the invoice as disputed and send you a webhook message.

This feature is available via integrations with Stripe and Adyen.

Learn more

Heads up! 👀

1️⃣ Replacing groups with filters‍

The new filter-based system (see above) introduces changes to a number of objects, including billable_metric, plan, fee and customer_usage. In addition, the endpoint to retrieve billable metric groups is deprecated.

2️⃣ External subscription ID required

In order to develop real-time billing capabilities, we need to streamline our validation process. We've therefore decided to make external_subscription_id mandatory when sending events via the Lago API.

3️⃣ Deprecation of API fields

For the sake of clarity and to preserve the quality of the API, we're going to deprecate several legacy fields.

We kindly ask you to update your integration before July 9, 2024 to avoid any potential breaking change.

Learn more

Thank you and stay tuned!

The Lago Team

Lago is a company backed by
Y Combinator

Lago, built with love around the world!