edoardomistretta_best-practices

[low grove]

👋 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/1499045160494039201

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[grim hedge]

how does the API resolve this? Will the Acacia response filter out the Basil-specific fields, or will it return the raw object regardless of the requested Stripe-Version?
Each request will respond according to the API version pinned pinned to it (if you are setting explciticly in the StripeHeader)

So there should be no issue making API call with different API versions on a single object

[dreamy dome]

what will I see in payment_method_types on the frontend if satispay does not exist for the Acacia version?

[grim hedge]

JS isn't a strong typed field, in the API response you should get the satispay

But in order to accept a payment with satispay you need to have a react version that supports that payment methods

[dreamy dome]

ok, thank u

Are there recommended patterns or official migration guidelines for managing API version upgrades when frontend and backend components are deployed independently?

[grim hedge]

It varies from one integration to another. But usually you should migrate your backend first then your frontend. Because at worst case, the frontend will not display a new feature/payment

And most importantly you should test before ship in production

[dreamy dome]

ok

thank you for your help