christian-blackburn_api | Stripe Developers | Page 1

polar leafBOT Jun 23, 2025, 10:32 PM

#

👋 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/1386836286358421651

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

wispy patio Jun 23, 2025, 10:35 PM

#

hello! wrapping up some other questions, will get back to you asap

#

ok looking at this now

#

sadly we can't see the results of GET requests so they can be a little tricky to troubleshoot

dry shadow Jun 23, 2025, 10:41 PM

#

fair enough, I can give you the screenshot/output of the shell call?

#

wispy patio Jun 23, 2025, 10:55 PM

#

hmm i'm not able to reproduce it

#

would you mind trying to run this using a curl request real quick? also try using full quotes instead of apostrophes?

#

also is it just the one PaymentIntent showing up in the query results or are there others?

dry shadow Jun 23, 2025, 11:33 PM

#

Sorry, was in meetings, sure, I'll run this as a curl.

The Shell functionality doesn't like the full quotes.
And yes, it's only this one paymentintent showing up with the incorrect status

wispy patio Jun 23, 2025, 11:34 PM

#

no worries! let me know what happens with the cURL requests

dry shadow Jun 23, 2025, 11:52 PM

#

Having issues with the cURL at the moment, it keeps giving me a 400 Bad Request response, just working through it

wispy patio Jun 23, 2025, 11:53 PM

#

can you share a request ID? i can help with the 400 maybe

polar leafBOT Jun 24, 2025, 12:00 AM

#

dry shadow Jun 24, 2025, 12:10 AM

#

Ok, got it to work, the API client I was using was giving incorrect curl

curl -G
--url https://api.stripe.com/v1/payment_intents/search
--header 'Authorization: Basic cmtfbGl2ZV81MUtkcDBYQ1BPRGxTTmV3Wmk2TUZmcWRKcGowQzhmWDZRc1NuRk85dFJ4UGdvYTJiTjBRbnREaTRPclNqTElzTUd5bEhoVVRaYjl2SlBlS1VTZnhSZXBpODAwRU91R0dUdlE6'
--data 'query=status:'''requires_payment_method''''

outer jungle Jun 24, 2025, 12:13 AM

#

Hi! Stepping in for my colleague! Glad you were able to get it to work!

dry shadow Jun 24, 2025, 12:25 AM

#

So that query is still giving the single payment intent with a status of 'canceled' when I am specifically querying status of 'requires_payment_method'

outer jungle Jun 24, 2025, 12:33 AM

#

Looking into this!

outer jungle Jun 24, 2025, 12:55 AM

#

Do you have the payment intent that is being returned with a status of 'canceled'?

dry shadow Jun 24, 2025, 1:39 AM

#

oh sorry, yes, it's pi_3RYxElCPODlSNewZ17ghwYIY

outer jungle Jun 24, 2025, 1:45 AM

#

Thanks! You're getting pi_3RYxElCPODlSNewZ17ghwYIY because the Search API filters using a cached version of the PaymentIntent status. This payment intent previously has a status of requires_payment_method (https://dashboard.stripe.com/logs/req_2S8XzWZpUioNuI). Hence, even if it's not in a cancelled status, it's still showing up in the search.

More details about it here: https://docs.stripe.com/search#data-mismatches

dry shadow Jun 24, 2025, 1:54 AM

#

Righto! So that cached version is more than 3 days old

outer jungle Jun 24, 2025, 2:00 AM

#

Yes, but that is still taken into consideration.

#christian-blackburn_api