March 2026 monthly summary for getlago/lago-api focused on performance optimization for the Credit Notes endpoint. Implemented deep eager loading and serialization improvements to eliminate N+1 queries, resulting in a dramatic reduction in database round-trips and faster response times. The work emphasizes scalability for large payloads and sets a foundation for maintainable, high-performance data access. Overall impact: substantial performance uplift for the credit notes retrieval flow, enabling reliable handling of large per_page values with lower latency and reduced DB load.

February 2026: Delivered cross-provider payment methods lifecycle improvements in Lago API and introduced multi-payment-method support in the Lago Go client, reinforced by focused test fixes and migrations to ensure data integrity and reliability. This work reduces stale payment-method data, expands payment options (including SEPA), and enhances error handling and overall payments resilience across services.

Month 2026-01 — Lago API delivered a feature to discard old provider customers and their associated payment methods when a payment provider is removed or replaced, aligning payment-method lifecycle with provider status and reducing stale data. The implementation touched both UI and API paths (update_service.rb and upsert_from_api_service.rb) and was committed as fix(multi-payment-methods) in f3ebb6cf741a0a9a0b095f312d8a4cc33fe0f114, addressing Lago’s provider-customer relationship (#4917). In the same period, a revert was applied to preserve existing system behavior after evaluating the discard logic. The revert is captured in f49769727ac8061e95b5b5160df277ac1aad79f8, reverting getlago/lago-api#4917 (#4951).