#panpetar
1 messages · Page 1 of 1 (latest)
Hello panpetar, we'll be with you shortly! 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.
• panpetar, 7 minutes ago, 23 messages
• panpetar-account-support, 2 hours ago, 2 messages
Yep okay that would do it then
Those triggers basically create API requests on your account in order to generate the Events
I don't understand this. When user pays successfully I receive this event 'customer.subscription.updated' but this information is set in past,
I would expect this information to represent when will this users subscription end. Am I right ?
I keep getting this value 1970-01-21T00:32:32.639Z
Or by looking at the Subscription in the Dashboard
There is a section for Events
Or really there should be an Event ID provided whenver you recieve this webhook
That looks like evt_xxxx
https://dashboard.stripe.com/test/events/evt_1O5UTlDhjDyCovQ5vltfDcVa
here I see `` "cancel_at_period_end": false,`
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
evt_1O5UTlDhjDyCovQ5vltfDcVa
oh sorry,, i am interested in stg else
"current_period_end": 1729952639,
But why, Why isn't it a date 1 year from now ?
I would expect that date but it is not the date you mentioned
1729952639 is some date in 1970
Try with https://www.epochconverter.com/
Using new Date() will not give you the correct UNIX time
what date format this even is ? i don't know how I am supposed to interpret this
Our API always returns dates in UNIX timestamps by the second