#joshuberx

1 messages · Page 1 of 1 (latest)

next hatchBOT
pure osprey
#

Hi there

#

So you are setting cancel_at_period_end but seeing it cancel immediately?

#

Can you provide an example that I can look at?

teal ravine
#

Give me a moment to produce an example. I'm not an Engineer but am our Head of Support and trying to resolve this for our eng team. I may not be able to answer all technical questions but can loop back with any info that I'm unable to provide.

#

It appears correctly handled in Stripe but on our backend it immediately cancels subscription with a Support Cancellation Date

pure osprey
#

Okay so that's a bit different then. We don't control your backend. If it shows in Stripe that it will cancel at period end then that is what it is set for. You will have to work with your team for why your backend data doesn't align with our data.

#

Oh

#

I think I see the confusion

#

This is the timestamp for when the Subscription is updated to be canceled.

#

Meaning the time when you set cancel_at_period_end

teal ravine
#

Yes I believe so

pure osprey
#

That property does not actually indicate when the Subscription will cancel

#

That would be the cancel_at timestamp

#

canceled_at and cancel_at are tow different properties

#

Sounds like you want your backend to show cancel_at but currently it is using canceled_at

teal ravine
#

Yes I think that is right

#

Its strange that it works correctly on non-scheduled subscriptions though

#

So if I'm understanding correctly, we just need to change the property we're using from canceled_at to cancel_at?

pure osprey
#

Well canceled_at will reflect the same timestamp as cancel_at if the Sub is canceled immediately and not set for a future time to cancel

#

Yes most likely. I would relay the above to your Eng team and have them take a look at what you are using in your backend right now

teal ravine
#

Yes I understand that canceled_at will reflect the same timestamp as cancel_at if the Sub is canceled immediately and not set for a future time to cancel. In our case when we cancel at period end any sub that was not scheduled, the cancel_at end date seems to log correctly in the backend.

#

But I'll share this with our Eng team and ask them to dig into this further based on your feedback.

#

Thanks very much!

pure osprey
#

Sure thing. Feel free to pop back in if we can help