piercy_best-practices

[edgy wagon]

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

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

[cunning fulcrum]

Do you have some examples of where it behaves differently? And can you confirm which API property on which object you're referencing?

(I'd like to confirm the behaviour you're seeing before I recommend you change API versions as I don't think that is related)

[open bear]

Account A: acct_1No1t4L6xpXYTbdr uses default API version is 2023-08-16

Account B: acct_1FH7OoCgbe7Mkyma uses the API version 2019-09-09

When a payment intent for a subscription is created using an account with a recent API version, the description from the Stripe subscription is copied across as expected. This can be seen in the first screenshot. pi_3RjLbjL6xpXYTbdr1yR4bbCx

However, on the Stripe account, which uses the older API version, the invoice number is used as the description for the payment intent. This can be seen in the second screenshot. pi_3RknWBCgbe7Mkyma1nLxn2Wh

[cunning fulcrum]

Thanks for the details, checking

[open bear]

The payment intents aren't the same ones from the screenshots, but the issue is the same

[cunning fulcrum]

• pi_3RjLbjL6xpXYTbdr1yR4bbCx

  • in_1RjLbZL6xpXYTbdrsOtcA5z4
  • sub_1RjLa6L6xpXYTbdrI41IHKnl

• pi_3RknWBCgbe7Mkyma1nLxn2Wh

  • in_1RkmZHCgbe7MkymaDrDTrZ9y
  • sub_1ROfUgCgbe7MkymaXT51lHlH

(still looking, just leaving a trail for my colleague)

[open bear]

It may help if I give the end goal too. We are trying to standardize our subscriptions around one description. In doing this we noticed the problem.

${Our Product Type} subscription at ${location} for ${product} .

So the expectation is that the transactions for the subscription all say something like:

Membership subscription at Aaron's Test Location for Adult
Coaching subscription at London Tennis Centre for After School Tennis

[cunning fulcrum]

I think it might be more to do with how the subscription was created as opposed to API version. One was via Checkout, the other direct via API:

• https://dashboard.stripe.com/test/logs/req_unDFB8Dmxpzdgh
• https://dashboard.stripe.com/test/logs/req_x05X8TK9SLvzYT

They shouldn't behave differently I don't think so this may just be a bug

[cunning fulcrum]

Yes, that is how it should work

[open bear]

Interesting ill check that on our side. This came to me from QA and another developer, ill check on this and see if thats the cause.

[cunning fulcrum]

Can you please write in to our team? I think we're going to need to figure out what is expected here and file a bug accordingly

[edgy wagon]

Hello @open bear, we have sent you a direct message, please check it at https://discord.com/channels/@me/1394968364614422540

• 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.

[open bear]

no worries I can do. Im going to setup some specific examples to test on our side too. So ill make sure I have comparable information when i sent it in.