joey_api

[sweet wren]

👋 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/1333416666037747786

📝 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.

• joey_api, 2 days ago, 32 messages

[outer portal]

Just to provide more context, here is the schedule with "remove automatic tax". This is after we've updated the customer's shipping address, then updated the subscription to enable automatic tax, and we believe that "remove automatic tax" is because of our subscription schedule

[tulip axle]

"validate_location" isn't an optional parameter with stripe subscription schedules, we cannot apply "automatic tax"
Sure, because you set it when you create/update the Customer. This is why the other day when we spoke I recommended you validate the address with us first before creating the subscription

Unfortunately I think you'll need to refactor your integration a bit to account for that otherwise you'll be in this loop

[outer portal]

Thank you for the information. I have already recommended to the team that we should look into refactoring this. But our current matter is urgent, so for now we'll need to find a way to update the automatic tax for subscription schedules

is there any clean way to do this? Or will I have to: pull the current subscription schedule, duplicate the data, enable automatic tax for each phase, and then update it again afterwards?

[tulip axle]

But we get several error messages about the data when duplicating phases,
Got an example?

[outer portal]

it's just been a whole debugging process

```then
````handle_error_response': You can not modify the start date of the current phase. (Stripe::InvalidRequestError)
```etc. I'm still just trying to make the data correct. Simply duplication and updating won't work, and having to make these tweaks to update it just feels messy

[tulip axle]

Yeah I'd guess you're just trying to pass the sub/phase object directly into the phase params?

Which unfortunately won't work because of various issues like the above. It's a cumbersome API to work with

[outer portal]

yeah, that's exactly it

okay, thank you for reassuring me. I'll have to just do my best to copy the data & make an update. Then I'll push for my team to reinvest more time into refactoring our system, so that we do not create any more subscriptions without a proper shipping address

and thanks again for the switft responses on this!