#aconnelly

1 messages · Page 1 of 1 (latest)

fading flickerBOT
heavy wagon
pale rapids
#

Yep, that date's a bit closer to the answer. I will still need to find the 30 days overdue cancellation setting from the account

#

I could hardcode it, but that's not ideal

#

Thank you for replying by the way

fading flickerBOT
heavy wagon
#

I will still need to find the 30 days overdue cancellation setting from the account
Not sure if there is a setting can be fetch from the public API.
Maybe you can store this information in the metadata of each subscription.

pale rapids
#

That might overcook it a bit, I would need to add that piece of metadata every-time a subscription is created(?) and if we ever change the setting we would need to write a migration to update all those bits of metadata.

Basically the problem I'm trying to solve is that we have an accounts team that will chase these unpaid invoices and they need to know the exact date the subscription will cancel so they can prioritise the list of these unpaid invoices.

heavy wagon
pale rapids
#

Yeah, I can do that but I will just need to hardcode that 30 days on my side. I think that might be the way to go for now