#chiefwhitecloud_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1417138621450027138
đ 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.
- chiefwhitecloud_customer-source-expiring, 3 days ago, 29 messages
Hi, on the event, evt_3S746NIJYO6sWeqO0cdJUMrP you'd see the invoice related to the payment. You can attain then retrieve the invoice, https://docs.stripe.com/api/invoices/retrieve?api-version=2025-07-30.preview to look at the lines data to see that it's from a subscription
Ok thanks. I'm getting that but, I need to determine if it is subscription creation. The invoice "billing_reason" is set to "subscription_update".
How can I determine if the payment intent or the invoice was used to create the subscription?
I would like to use this information to set up access to the subscription in our system
The billing_reason should tell you that: https://docs.stripe.com/api/invoices/object?api-version=2025-07-30.preview#invoice_object-billing_reason
In this case, you see that the reason is subscription creation.
In this event... evt_1S746TIJYO6sWeqOZh29hYQc.. the invoice has a billing reason of subscription_update. This is always the case for us. We are using an older version of the api
Looking
Yeah, that seems to be buggy. Does this happen every time or just on this invoice?
With our API version it happens all the time. That is why I was using the description on the payment intent to determine this.
Now that the description is automatically translated, my integration is broken.
The first translated PI description was at 2025-09-13 02:46:17
Prior to that the description was always 'Subscription creation' on the payment intent
Oh, that is beause we introduced that at a later version. With the older API version like, 2016-07-06 it's expected
you will need to ensure that you migrate to the newer version
ok but I need fix for now
I see that I can set the locale for the Checkout session
Might try fixing this to "en" for now
Is there another property that I could use on the invoice or payment intent?
Maybe compare the creation dates to the subscription creation
Hello, unfortunately there isn't an easy alternative to the billing reason field. The alternative would be something like listing all of the subscription's invoices and seeing that there has only been one so far