#yoann_subscription-update
loud salmonBOT
👋 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/1301238718413144086
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
indigo sage
@vernal cape there's no way to "delete" what happened. What you can do is revert the change back and then void the Invoice(s) that you don't want them to be charged for
yoann_subscription-update
vernal cape
If we were to void those invoices and resume collection later, what would the invoice then reflect? The customer won't be charged for the billing cycle and will only be charged for the next billing cycle? Could we create a new invoice that reflects what we'd want to charge the customer?
indigo sage
It really depends on the specifics of what you did, what changed, which Invoice(s) were involved, etc.
I'm not sure I follow your overall question and you shared just a request id without more context about what happened, what the Subscription did before, what it did after, what you want to change back, etc.
On this server we focus more on explaining the API and the code itself
I looked at the Subscriuption you shared and no Invoice was issued today right?
vernal cape
So we had a bunch of subscriptions that were migrated from two items (plan + addon) to a consolidated state (just a plan) and we realized that the price charged on this consolidated price/product was wrong so we want to roll them back to their initial product/price. However, some of them have already been charged and some are about to be charged. To limit the blast radius of the issue, we were considering pausing collection for these subscription, mitigate and resume collection.
What I was wondering is: given this, will the time the customer was on the consolidated price be on their invoice and what can we do to remediate this?
Does it make more sense?
indigo sage
a little bit
https://docs.stripe.com/api/subscriptions/object#subscription_object-pause_collection is likely what you want to ensure they don't receive an Invoice until you are ready to clean up.
Sorry it's still a bit vague and there isn't a way to "undo" a migration like that. All you can do is update again to reflect the old state back but all issued Invoice(s) will continue existing and would charge if you don't explicit void them
indigo sage
@vernal cape does that make sense?
vernal cape
It does make sense. Thank you very much, appreciate your time!
indigo sage
of course! Those migrations with a mistake are definitely tough to fix/recover from 😦