We were wondering if you've ever contemplated adding something like a
lago_charge_id
to the fee object?
With our plans, a particular
billable_metric
may have multiple corresponding charges and it would be ideal for us to be able to map the resulting fees (
/estimate_fees
, webhook,
get /fees
) back to an exact charge on a given plan/subscription.
Created by Mathieu Déjean
·