baramouille

[peak locust]

hi! do you have any example of this happening like the request ID req_xxx from a failed request?

[minor birch]

Shoud I find this information in the stripe dashboard ?

[peak locust]

that's one way see also https://support.stripe.com/questions/finding-the-id-for-an-api-request

its also in the HTTP headers of the API response

[minor birch]

Thank you, I find an exemple in the logs, I do have the id request

Do you need I send you the content of the POST request ? (I don't feel confortable putting this in a public chanel ^^)

[peak locust]

no just the ID

[minor birch]

req id : req_Ft9dKwBmutv1gx

[peak locust]

so that request did not return a 404 'no such payment intent' error

[minor birch]

So the problem should definitively come from our application ? Not a set-up of stripe issue ?

I can see in the log payment that the status is :requires_payment_method

However, payment information has be filled in

[peak locust]

well that's a separate thing so let's focus on your first question

getting "no such payment intent" (a 404 status in the API response) usually means

• you used a live/test mode key and the PaymentIntent exists in the other mode instead
• you are using Connect and don't use the Stripe-Account header in the right way to make a request on the correct connected account/platform
• you have multiple Stripe accounts and you used the API keys of a different account than the one whose keys you used to create the PaymentIntent in the first place

[minor birch]

If the problem was indeed one of the three you mentioned. Shouldn't I have a problem with every payment?

[peak locust]

depends how your server works and how it's configured

if you have an example of a failing request I coud tell you why it failed

[minor birch]

Actually I only do have exemple of payment failing, not request, they all return 200

sorry for the quality, it's from a user on a mobile device

[peak locust]

then I'd suggest setting up more logging in your application so that the next time this happens you can capture information like the Request-ID header https://stripe.com/docs/api/request_ids and we can go from there

without having something to work with like an exact failing request ID or exact UTC timestamp + PaymentIntent ID of the time you know this error happened I can't say much , it's a generic error with multiple causes

[minor birch]

Okay, I'll set it up.
Thank you for taking the time to look at my problem and help me.
I'll be sure to post again when I have more information.

have a nice day !

Just in case, here the information of a specific failled payment :

request_ID : req_Ft9dKwBmutv1gx
payment_ID: pi_3OgsFZCN7b44IDnX1xf5sx2R

@peak locust

[peak locust]

well if i look at API requests around that time you have a 404 because on your frontend web page you used the API keys of a different account

you create that PaymentIntent on the V____M_C__ Rambouillet account but on the frontend you call confirmPayment using the API keys of a different account V____M_C__

[midnight tangle]

Hello, hope you're fine
I'm one of @minor birch's developers, I'd like to intervene

I understand the problem better, but one question persists: Why are certain payments working if we're using the wrong key?

[peak locust]

because the ones where it works you are not using the wrong keys; the ones where it doesn't work you are using the wrong keys

you need to look into the logic you use to decide e.g. which publishable key you pass to Elements on the frontend

[midnight tangle]

Oh I see
Thank you for your help, we're gonna see that 🙂
Have a good day