#rohan_error
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/1344139936701616179
📝 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.
- rohan_code, 6 hours ago, 91 messages
- rohan_api, 10 hours ago, 17 messages
Here's the payment intent ID: pi_3Qwah9IlR9VWnEGJ0cX4VJIy
Hey Sam! Thanks in advance for the help
Here's more of the error:
"code": "payment_intent_payment_attempt_failed",
"doc_url": "https://stripe.com/docs/error-codes/payment-intent-payment-attempt-failed",
"message": "The payment failed.",
Hi! Loking into this.
Thanks!
Can I check why was the payment confirmed twice? I see once from the backend (https://dashboard.stripe.com/logs/req_eHrNGgHYFnWpVi) and again from the frontend (https://dashboard.stripe.com/logs/req_julF0tpxvZCzJR).
Oh interesting. Yeah that was happening before, but it didn't seem to cause any issues—it was just returning the same info twice.
I tested this locally and in sandbox and it seemed to work fine
Typically confirming twice is not recommended. You can just confirm it once on the frontend.
Yes, that is the issue and it occurs in livemode.
Alright, one sec, let me give that a shot
Why is client_secret nullable? Under what conditions can it be null?
Where are you seeing null?
The type is listed as string | null
Which event or request are you seeing this in?
It's in the type defs, not in an actual request. I haven't actually seen it be null, so I'm wondering why the type is listed as nullable
I can't think of a scenario where it will be null.
Would it be possible to submit a feature request to update the type to just string?
There might be a scenario where it could be null. It's just that off the top of my head I can't think of one.