#Sebastian Cortabarria-subscription-cancel

1 messages · Page 1 of 1 (latest)

candid fox
#

Hi there 👋 canceled_at will hold the time of the update to schedule the cancelation if cancel_at_period_end is used. Otherwise it will hold the actual date of the cancelation. Do you have a sample subscription we can take a closer look at?

hollow bronze
#

For example this subscription sub_1JnPtUDlgG4V75nn4PEkF3m6. I can see in the dashboard that the last event is got 2 different dates, the canceled_at one is previous to the cancel_at date. And we using the api to retrieve it I see the same thing. But retrieving it from the tables directly is giving us canceled_at == cancel_at. Could you please check if they are different on your side?

@candid fox Thank you very much!!!

candid fox
#

Pulling it up now

#

I'm seeing:

  • canceled_at set to Dec 8th
  • cancel_at_period_end set to true
  • cancel_at set to Dec 22nd
  • ended_at set to Dec 22nd
hollow bronze
#

And that makes perfect sense. So I'm guessing something IS wrong on our side. Thank you Toby

Cases in which customers fail to pay for a while or manual cancelations through the dashboard would have canceled_at == ended_at right?

candid fox
#

For manual cancelations, if cancel_at_period_end isn't used then canceled_at should equal ended_at. For cases where the customer can't pay, that's going to depend slightly on whether your settings say the subscription should be canceled or go into an unpaid state.

hollow bronze
#

Thank you so much!