#andy_code
sullen otterBOT
👋 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/1428270004276822016
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
somber field
It's this changelog: https://docs.stripe.com/changelog/basil/2025-03-31/add-support-for-multiple-partial-payments-on-invoices
You can see the alternatives mentioned here 🙂
zinc summit
I read through that. The solutions require us to make one additional network request for every invoice returned in our list request
so invoices.list(params) -> array of invoices with payment objects and payment intent in those objects (only the id, can't get the status)[]
then for each invoice object we need to Fetch individual invoices with the full payments object expanded to include the payment_intent
that's an n+1 problem we didn't have before. So wondering if that's just the nature of the API or is there another workaround to get the payment intent in the initial request.
somber field
Yes I agree it isn't great and we have received a lot (really a lot ) similar feedbacks. It's unlikely Stripe API will roll back, but personally, my suggestion would be selectively think of which Invoice you want retrieve the Payment Intents