#ironbeard_api
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1310640320433754162
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- ironbeard_best-practices, 4 days ago, 7 messages
Sorry the request id is req_thKNlVo2MA8KKM
Hi ๐ taking a look
hey toby, thanks ๐
The result of the request is shown in the log for it:
https://dashboard.stripe.com/logs/req_thKNlVo2MA8KKM
as well as in the customer.subscription.updated Event that the change generated:
https://dashboard.stripe.com/events/evt_1QP4rjCoTIfwbn28lmVhIOX1
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
The request included billing_cycle_anchor: now, which caused the Subscription to be moved to a new billing period as well as being scheduled to cancel at the end of its period (which the request updated).
hmm gotcha
So it's probably the case that if I'm just changing cancel_at_period_end that I don't want to set billing_cycle_anchor to now.. what would be the correct value for that?
unchanged, or omit the parameter.
Gotcha. So from the customer's point of view, is it likely they received an invoice via email? They emailed us asking to not renew.
If you have emails set up for Invoices, then probably.
Do you see any emails in the Sent emails section for that customer's page in your Stripe dashboard?
Thankfully no, looks like they just got the upcoming renewal email from a few days ago, which is why they emailed us asking to cancel.
Okay. So, typically I send billing_cycle_anchor: 'now' on all update requests, but I suppose that if I'm toggling cancel_at_period_end I should not include it? Would that be generally safe?
I have it default to 'now' to allow people to upgrade subscriptions in a way that charges them when they upgrade
I'd recommend testing the flow in testmode to ensure it's behaving the way you're expecting, but generally, yes. If you only want to set the Subscription to cancel at the end of the current billing period, you likely don't want to also provide the billing_cycle_anchor parameter.
Gotcha. Thanks ๐
Any time!