#maverick_api
hardy forumBOT
👋 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/1489375648395952128
📝 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.
- maverick_refund-invoicebalance, 39 minutes ago, 43 messages
cedar onyx
Hello again 👋
As our bot mentions, we close threads due to inactivity (~30 - 45 minutes).
Are you asking about the failing refund request? Since I think that was already addressed in the previous thread. Or are you asking about Invoice object and Payment Intents & Charges?
hollow phoenix
I'm asking about the invoice object with the seemingly missing payment intents and charges
cedar onyx
Are you still investigating through the Stripe Shell in the dashboard?
I noticed in your request that you are using the Java SDK and that version is pinned to the API version 2022-11-15.
hollow phoenix
long story short, company is in the middle of shutting down so using the Java SDK is more trouble than it's worth so I switched to the Python sdk just now, and I'm using version 15.0.1
cedar onyx
The reason I ask is, the Stripe Shell in the Dashboard will use the latest API version and there were HUGE breaking changes specifically in how Invoices relate to Payment Intents between that version and the current one.
Specifically, this change: https://docs.stripe.com/changelog/basil/2025-03-31/add-support-for-multiple-partial-payments-on-invoices
Now that Invoices can be related to multiple Payment Intents, we had to change the way those objects are related in the API.
Stripe Python 15.0.0+ pins to API Version 2026-03-25.dahlia
There have been a very large number of breaking changes in the 3.5 years between the Java SDK's API version and the current one.
hollow phoenix
I've been using "/workbench/shell" to play with the API before making changes to the script, and according to the cli commands there, the invoices object both a charge and a payment intent
I have not been basing my understanding on the outdated java sdk but rather the shell, but it seems the shell is at odds with the version of the python sdk I am using?
cedar onyx
The shell does some "helpful" things. You should not rely on it to be the authoritative source of information
I recommend reviewing the API reference doc, which allows you to pin an API version to ensure you can review the properties of the Invoice object as it appears for a given API version: https://docs.stripe.com/api/invoices/object?api-version=2026-03-25.dahlia&rds=1&lang=curl
For API versions after 2025-03-01.basil, you would look here to get the Payment Intent associated with an Invoice
hollow phoenix
thank you
cedar onyx
Sure thing!
hardy forumBOT
hollow phoenix
I think I managed to issue refunds to a couple of customers so I'm unblocked here
acoustic grove