#chris2me_best-practices
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/1365256357611044957
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐
Can you share a failure request Id to better understand what kind of updates you are trying to make ?
ID: req_zznBEzU0vn8kwq
We understand why this error happened because we forgot to limit subscription changes for pending updates only for charge_automatically subscriptions. That has since been fixed.
What we're trying to understand, given the subscription collection method is send_invoice in this case, is there anyway we can enable pending updates for the prorated invoice that is charged immediately while also preserving the subscription collection method as send_invoice for renewal?
Maybe to add some extra details here about what we do:
- Customer is set up with subscription with collection method
send_invoice - Customer is allowed through our checkout system to add seats to their subscription
- We prorate the changes and charge invoice immediately. Invoice collection method is set to
charge_automaticallyin this case. - Customer pays for their upgrade in our checkout but subscription collection method remains as
send_invoicefor their renewal
Ok I see yeah according to the error message:
You cannot set
payment_behaviortopending_if_incompletewhen the collection method issend_invoice
is there anyway we can enable pending updates for the prorated invoice that is charged immediately while also preserving the subscription collection method as send_invoice for renewal?
Nope.
hi! I'm taking over this thread. let me know if you have other questions.
That is a shame. We really like the pending update features but send_invoice customers are usually our larger ones and rolling back changes because they failed to pay for a seat upgrade is currently a bit of a headache sometimes.
Is there a reason why pending updates is limited to the subscription's collection method as opposed to the invoice collection method?
sorry, but we don't know why the API was designed that way. but that's how the API works currently.
No worries, is there another way we can get that question answered? Or just email Stripe support?
you can try Stripe support yes: https://support.stripe.com/contact
but getting an answer on the "why" won't change the issue itself.