#xu_code
1 messages ยท Page 1 of 1 (latest)
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.
- xu_webhooks, 1 day ago, 7 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253690825028800533
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
hi there!
but I can't delete the "old" subscription items when the payment behavioour is PENDING_IF_INCOMPLETE.
did you try this and got an error? if so, can you share the request ID (req_xxx)? you can find it here https://dashboard.stripe.com/test/logs
indeed this looks like it's not possbile. can you clarify why you are trying to delete items in this case?
The case is when a user wants to change from an existing subscription to a new subscription, and I'm trying to get rid of the "old" subscription price(s)
got it, looking into this
thanks ๐
Yeah this isn't possible with pending updates unfortunately. Supported params you can modify with pending updates are here: https://docs.stripe.com/billing/subscriptions/pending-updates-reference#supported-attributes
Are there any suggested workarounds?
I have previously worked around this by .setQuanitity(0), but this fails when the plan is billed in different interval
If they're different intervals, then no I can't think of a workaround that uses pending updates unfortunately
Because if they're different intervals you also couldn't do it in 2 requests where adding the new price is the pending update and deleting the old one is a normal update since you can't mix interval types