Arvind

[crisp spire]

👋 happy to help

would you mind sharing what's PaymentIntent ID?

[atomic pivot]

Sure let me give you shortly

[atomic pivot]

pi_3NM79XHhzXcPYLMM1UOHKjlt

[crisp spire]

taking a look

[atomic pivot]

That error occurred on many other ids,

From the stack trace it appeared error is on some date value under stripe.net, nothing to do with the intentid the paremeter which we pass

[crisp spire]

I think I know why

let me just double check something internally and get back to you

[atomic pivot]

Sure

[crisp spire]

https://dashboard.stripe.com/test/logs/req_zyiKoYtN4yqTXL

as you can see in this request the parameter you passed for payment_method_options.card.mandate_options.start_date https://stripe.com/docs/api/payment_intents/object#payment_intent_object-payment_method_options-card-mandate_options-start_date is 1687515823343 which is a timestamp in milliseconds whereas we expect a timestamp value in seconds

when the SDK is trying to deserialize the object it's considering it to be in seconds which gives a date on Apr 1st 55445

~33000 years from now

[atomic pivot]

you mean the payment method options when making the pyament first time?

[crisp spire]

when you created the PaymentIntent

the request I linked to

in your dashboard

https://dashboard.stripe.com/test/logs/req_zyiKoYtN4yqTXL

[atomic pivot]

Ok, I'll check the code our side

Will this chat window will remain open?

[crisp spire]

yes