#yathartha_webhooks
north sequoiaBOT
royal sorrelBOT
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.
- yathartha_api, 1 hour ago, 5 messages
- yathartha_api, 2 hours ago, 9 messages
- yathartha_unexpected, 1 day ago, 16 messages
- yathartha_unexpected, 5 days ago, 4 messages
north sequoiaBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252911867278655519
đ Have more to share? Add details, code, screenshots, videos, etc. below.
proud basin
hi! by "in the test mode" I assume you mean a different Stripe account entirely right?
fair ore
yes
proud basin
do you have an example of where this event has the other type you expect?
in any case, I imagine this relates to the change in https://docs.stripe.com/upgrades#2019-12-03 (so it's important you always test on the exact API version you expect to be using).
fair ore
can i provide the payload from the test mode one and live mode one
proud basin
I just need the evt_xxx ID not the payload
proud basin
also looking at the first event you shared, it seems normal
that item is not the subscription item, it's a proration item. type:"susbscription" is only for the item that corresponds to the recurring Price directly.
yeah in evt_1PTHw1IG8Ha7XjkSR6EUFx7k the item is the recurring Price, not a proration.
So that's all normal and consistent.
nothing to do with API version, sorry for that confusion
fair ore
if it is proration item then will have type: "subscription" and incase its not a proration item then it will be "type":"invoiceitem"
I have used 2024-04-10 in the live mode
proud basin
if it is proration item then will have type: "subscription" and incase its not a...
no, the opposite.