#ben-st-john_api-version-paymentintent-refund
dusky nimbusBOT
đ 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/1405614156857737236
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
ivory bane
Hi there,
did you already upgrade the API version? For which endpoints have you already updated or do you plan to?
crisp solstice
the "pinned" version on our dashboard is the old one and we are using the new api version only in the headers as needed.
and it's the whole payment lifecycle - assume PI creation happens on "new" version and rest of lifecycle on the legacy version.
wondering what issues could happen? Or if we should be fine
like is the data stored any differently in the Db based on which API created/managed the charge/pi/info? Or is the data all the same, but the API just has different request and response formats?
ivory bane
Sorry for the delay. I just tested this because I wasn't 100% confident. I created a Payment Intent with the '2025-03-31.basil' API Version and confirmed and captured with APR version '2020-08-27' and it worked just fine
crisp solstice
Great! Is there anything else with this method that you would be concerned about in terms of mismatched API versions working on the same data (payment intents, customers, charges, etc)?
Like we also do Stripe connect transfers on these charges/PIs after they take place
ivory bane
Like we also do Stripe connect transfers on these charges/PIs after they take pl...
Tha shouldn't be an issue either. Gnereally speaking the flow for Payment Intents/Setup Intents has no changed through the API versions.
The breaking changes primarily focus on aspects of refund handling, balance transaction behavior, and changes in the relationship between invoices and PaymentIntents
crisp solstice
so if I made a payment with a new version and refunded with an older api version, would there be any issues? Or still the same thing? Obviously individual code will have to change - but Stripe's apis are all backwards compatible with eachother, right?
ivory bane
I would recommend to double check the changelog https://docs.stripe.com/changelog for breaking changes and test each flow that you want to update to a new API version in you test enviroment.
Rgarding Refunds it is important to know that canceling a Payment Intent will not automatically create a Refund anymore with the new basil API version
https://docs.stripe.com/changelog/basil/2025-03-31/remove-refund-from-partial-capture-and-payment-cancellation-flow
dusky nimbusBOT
ivory bane
If you cancel the Payment Intent that was created with a basil version), on a older non-basil version, it sill creates the refund automatically though
crisp solstice
Got it - thank you!
ivory bane
no problem. always happy to help