#originalowl_docs
native riverBOT
đ 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/1425550783642075258
đ 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.
- originalowl_error, 22 hours ago, 84 messages
noble sigil
I'm trying to figure out if I need to guard against the invoice or confirmation_secret being null. Or is it safe to assume and non-null-assert them for this workflow.
dark pecan
Hi, this is expected with the newer API ersion: https://docs.stripe.com/changelog/basil/2025-03-31/add-support-for-multiple-partial-payments-on-invoices#use-confirmation_secret-for-payment-element-integrations to support multiple payments on an invoice.
noble sigil
Gotcha, thanks for the "why". So will an invoice always have a confirmation secret if it needs payment? Is that what affects its nullability?
native riverBOT