teo_unexpected | Stripe Developers | Page 1

green tulipBOT Sep 5, 2024, 9:29 AM

#

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

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

#

outer ridge Sep 5, 2024, 9:33 AM

#

Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request

heavy thunder Sep 5, 2024, 9:43 AM

#

req_OJLg0cp8HUHM0y

#

Thanks!

outer ridge Sep 5, 2024, 9:45 AM

#

Thanks

#

Could you also share a request Id for a successful call ?

green tulipBOT Sep 5, 2024, 9:54 AM

#

grim cove Sep 5, 2024, 10:03 AM

#

basically this field is unsupported for legacy objects (like card_xxx ) when used through the compatibility layer of /v1/payment_methods

#

the only use we saw for doing this on the update call was backfilling pre-existing legacy cards and the team decided nobody had asked for that and it was unlikely to be needed, so the API just errors on this today

#

I am curious what you're trying to do overall

#

cc @heavy thunder

#

ok, well if you see this later, you don't need to (and well, can't) set allow_redisplay on the legacy objects, but legacy objects do appear in surfaces like the PaymentElement if you include unspecified in the redisplay filter https://docs.stripe.com/api/customer_sessions/create#create_customer_session-components-payment_element-features-payment_method_allow_redisplay_filters

#teo_unexpected