Developer experience

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).

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.

When using Lago and the Stripe integration, we'd like to be able to define a success_url and cancel_url for each checkout session. This request relates to the following endpoints: /customers/:customer_external_id/checkout_url /invoices/:id/payment_url This would allow us to display different web pages depending on the workflow (e.g. specific page for payment method registration and specific page for successful payments).

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

The Subscription objects returned from the "List Subscription" endpoint don't include the "plan" property (defining potential plan overrides), as it's it is done in the "Get Subscription" endpoint results. As a developer, when listing all the subscriptions of a customer, that forces me to do a "List" followed by multiple "Gets" (as many as there are subscriptions) in order to get the subscription details along with the potential plan overrides. The goal is to display the actual subscription price to our users (which could custom for a customer) Not urgent on our part, but just better dev XP [Edit] - I opened github issue - https://github.com/getlago/lago-api/issues/3299

As it says on the tin, some users wish to set the specific date that they are charged (IE to the 15th, or the first etc. Allow getting the date that they are expected to be charged, as well as updating that date, so that the user is invoiced immediately, and then will next be invoiced the anniversary starting from that date. This can somewhat be emulated via removing and re-creating the subscription, but that can cause problems with recurring metrics resetting when they are not supposed to.

Terraform is a great infrastructure as code tool, and having the ability to define metrics, plans, addons etc. via IAC would be a huge boon for consistency and tracking the changes over time. That said, I do recognize that there are some considerations that need to be taken given some values appear immutable once created, so I know its more difficult than just plugging the go lago api into a terraform module.

Create a single API endpoint that retrieves customer total lifetime spend

Create a single API endpoint that retrieves the ongoing customer balance, including all coupon credits, wallet credits, and credit notes, rather than requiring multiple separate API calls.

Have an estimate_fees endpoint, similar to this one ( https://getlago.com/docs/api-reference/events/estimated-fee ), but for charges paid in arrears. The use case is that we have various APIs and UI views that show customers the prices of using things. We want to pull the pricing information directly from Lago.