Skip to content

Support for Persistent Recurring Charges Without Monthly Events (Grouped Billable Metrics / Addons) #552

@utkarshMall91

Description

@utkarshMall91

Hi team,

We’re using Lago for metered billing in a Twilio-integrated SaaS platform, where each user can purchase multiple phone numbers (devices). Each phone number should incur a monthly recurring charge starting from the time it’s added, and continue until the user removes it.

Our setup:

Subscription is monthly.

Charges are either modeled as:

Grouped billable metrics (e.g., twilio_device_<device_id>)

We were under the impression that once such a recurring charge is registered (via an event or addon), Lago would persist and bill for it automatically each month, without requiring additional monthly events or API calls—unless explicitly paused or removed. And it kinda does,...
But the sitaution is complex, if we use grouped billable metrics
I add 3 twilio devices for first month, 1.15, 2.00, 1.15 monthly cost
But from next month decide to remove one 1.15 device--- how am I supposed to do it??

Update subscription doesnt have-- mapping of each twilio device,
it just has an object of subscription.plan.chage{ representing just the billable metrics entity. Not whats inside it}

Question:
Is there a recommended approach in Lago to support:

And the ability to pause/stop that specific recurring charge in future cycles?
Specifically for grouped billable metrics and editing them
But anything would Work

If not supported today, is this behavior on the roadmap or is there a recommended pattern to achieve this?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions