Developer experience

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.

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 user, I want to keep track of the credit note status without having to query Lago. It would be useful to have a credit_note.refund_status_updated webhook (similar to invoice.payment_status_updated ).

Currently we must execute loginUser mutation and store token in cache. We can simplify things here (and minimise latency) if we will use API KEYs instead.

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

Currently, the retry function is only available for failed webhook messages. It would be useful to be able to resend successful messages as well (e.g. the message was received but the webhook URL was outdated).

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