#rachel-bingham_api
warm wedgeBOT
đ 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/1400841336709451969
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
jade talon
Hello
The API version shouldn't affect your client-side apps as much as it does your server-side integration (assuming you create Objects like PaymentIntents server-side and retrieve them client-side using retrievePaymentIntent or similar functions)
The client-side SDKs are typically pinned to a specific API version so upgrading your account won't affect them directly - https://github.com/stripe/stripe-android/blob/master/stripe-core/src/main/java/com/stripe/android/core/ApiVersion.kt
However, if your server-side SDKs rely on certain properties which are either updated/removed from the newest API version then that could break the communication between your app and your server causing issues for the end user
The best way to make sure that things don't break would be to upgrade the API version in test mode (by setting API version explicitly) and see how your client-side app behaves
white vapor
Okay, thanks, that's good to know. Our client flows are pretty straightforward (create/update PI in the backend and send id to clients who confirm) so hopefully, it won't be a problem (just needs a bit of integration testing). Thanks.
jade talon
Yup, NP!