#cargo-billingcycleanchor

1 messages · Page 1 of 1 (latest)

silver shale
#

This feels like a bug

#

basically billing_cycle_anchor:'now' and proration_behavior: 'none' don't really work well together

#

if you are not charging upfront I'd recommend using trial_end instead

wide carbon
#

to be clear we are setting billing_cycle_anchor to a future date, not 'now'. Would setting trial_end also have the effect of setting the billing_cycle_anchor to the same date?

silver shale
#

yeah

#

basically if you do no proration upfront why use the billing cycle anchor?

wide carbon
#

are their any side effects to the subscription being in a trial state?

silver shale
#

it appears as a trial, so it depends how your business thinks about it. With your flow, if you hange the Price before the next cycle, proration would happen as if they had paid

#

so it depends what you really want

wide carbon
#

I'm worried about the consequences of being in a trial state affecting things like reporting. Basically these are users who are migrating onto our platform but they already have paid plans we need to map to what is in Stripe, so they are not technically trial users. Is there any other workaround?

#

we are considering calculating the max start/end dates from the line items themselves? Does that sound safe?

silver shale
#

hum

#

why do you use upcoming invoice in that case?

#

it should work after the subscription creation

wide carbon
#

we are trying to preview in our UI to the customer their next upcoming payment

silver shale
#

but do that after

wide carbon
#

this flow happens the first time they log in to our app and right after we have found their old plan and mapped it to the new plan. We want to show them the details of their subscription before collecting payment information for future payments

#

you are saying to create the subscription first and then show them the upcoming invoice?

silver shale
#

yeah

#

that's what I would do at least

wide carbon
#

I did consider that. It will require some significant changes to our code. I will investigate the feasibility further. I appreciate your insight.

silver shale
#

I still think what you found is a bug

#

it's because we cut no invoice upfront

wide carbon
#

haha I was going to ask but don't want to be rude. any chance that will be investigated further and fixed?

silver shale
#

I can't promise we can fix it though, it depends on what happens

wide carbon
#

cool. I understand. I will report the issue and help out where I can. thanks again

silver shale
#

@wide carbon I think I realized what is wrong and it'snot a bug

#

it's always how our invoices work with subscriptions

#

they charge for the future but the period represents the past