#piercy_api

1 messages ¡ Page 1 of 1 (latest)

shy coveBOT
#

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

📝 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.

nimble lintel
#

hi there!

random pumice
#

acct_1NmyL4E4rxSZDG11 - Default API Version 2023-08-16
API Subscription: sub_1RlT6WE4rxSZDG11kkOGH8Vi
1st: pi_3RlT6XE4rxSZDG111UPRzloA
2nd: pi_3RlT9WE4rxSZDG110UtlqmSc

Checkout Subscription: sub_1RlTCUE4rxSZDG116zloRMvL
1st: pi_3RlTCUE4rxSZDG110hqBZcK3
2nd: pi_3RlTDLE4rxSZDG111LGIFkIk

acct_1FH7OoCgbe7Mkyma - Default API Version 2019-09-09
API Subscription: sub_1RlSMfCgbe7MkymaIR7ew9rT
1st: pi_3RlSMfCgbe7Mkyma1nYnftII
2nd: pi_3RlSOcCgbe7Mkyma1bKmXvoN

Checkout Subscription: sub_1RlAMjCgbe7Mkymax33QsDDA
1st: pi_3RlAMkCgbe7Mkyma1wvHZzvw
2nd: pi_3RlSOJCgbe7Mkyma0AjLPuhM

#

So I was chatting with @prisma forge about this earlier. There was a belief this wasn't related to API version and I was asked to create a bug, but I wanted to make sure I hadn't given you bad information. So I went away and tested it further.

What we are seeing is that the installment payments have an incorrect description for different API versions

nimble lintel
#

The issue is that the description on subscription installments isn't maintained for the subsequent payments.
can you share more details about what you mean exactly by this? which field are you look at? what where you expecting to see, and what did you see instead?

random pumice
#

The initial PI has the correct description, but the subsequent PI's lose the description.

#

So on account acct_1NmyL4E4rxSZDG11 we created 2 subscriptions one via API one via checkout, and in both cases the second installment PI had the correct description.

On account acct_1FH7OoCgbe7Mkyma we did the same test but in this case the second installment PI's had Invoice XXX as the description and not the original description

nimble lintel
#

thanks for the summary! give me a few minutes to look into this.

#

yep I agree that looks like a bug. could you contact Stripe support as mentioned in the preovous thread so we can look into this in more details?

random pumice
#

I can, do you think this is a difference between the Default API versions though? As were considering bringing them forward.

#

Earlier, Yonnj believed that the checkout and the API reacted differently, and that was the bug they wanted me to create. However, now it seems they behave consistently on the same account, but differently across accounts

nimble lintel
#

based on your tests, it looks related to API version yes. but I checked the changelog, I couldn't find any mention of this change.

#

one solution for you would be to make sure all your account use the same API version.

random pumice
#

yeah, I can do that. that leads me back to my original question from the earlier thread:

All our code, goes through a service that's dedicated to stripe . It sets the API version to a specific version. The webhooks also have an API version set as well.

If these are the only two interactions with stripe, we think the default API version shouldnt really be doing much as we are setting the version manually. This should mean we are safe to change the default version, does that make sense or are there other considerations we should have when upgrading?

prisma forge
#

If you're manually passing Stripe-Version, then the default version is (mostly) irrelevant. But if you want to upgrade, then the regular breaking change upgrade recommendations apply: https://docs.stripe.com/upgrades

API upgrades

Keep track of changes and upgrades to the Stripe API.

#

Overall, I don't think the behaviour you're describing relates to API versions so I'd encourage you write in like previously advised and we can investigate further