#jeffrey_api
tired fractalBOT
👋 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/1463565384194986097
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
feral iris
We recently upgraded our integration to API version 2025-11-17.clover. Shortly thereafter we received the following email from Stripe:
We noticed that your live Stripe integration is experiencing payment failures because you’re not providing the return_url parameter in your PaymentIntent. The return URL is where your customer is directed after they complete their payment, and is required at PaymentIntent confirmation.
To prevent future payment failures, include a return URL when confirming the payment. To learn more about how to include a return URL, visit our docs.
I see that this breaking change states that return_url is now required when confirming a PaymentIntent: https://docs.stripe.com/changelog/2023-08-16/automatic-payment-methods
It also says you can get around this require by using automatic_payment_methods[allow_redirects]=never.
But when investigating automatic_payment_methods further, it seems those only kick in if you're not passying the payment_method_types parameter. From this doc (https://docs.stripe.com/upgrades/manage-payment-methods), it says:
In prior versions of the Stripe API, if you didn’t specify a payment_method_types parameter during the creation request, Stripe would default to using the card payment method for both PaymentIntents and SetupIntents.
Moving forward, Stripe applies eligible payment methods that you manage from your Dashboard to your PaymentIntents and SetupIntents by default if you don’t specify the payment_method_types parameter in the creation request.
We always set our payment_method_types param when generating a payment intent, and we don't use any payment methods that require redirect...so it's unclear to me how/why we would be getting any failures due to a missing return_url param.
In fact, I can't find any relevant errors at all in the log history.
We don't want to make use of any of the automatic payment methods, we only want our payment intents to accept the payment types we define via the payment_method_types parameter.
Should we be setting automatic_payment_methods[enabled]=false? Or does the fact that we're setting payment_method_types automatically prevent those payment methods from kicking in already.
rare sedge
does the fact that we're setting payment_method_types automatically prevent those payment methods from kicking in already.
Correct
What's the account id?
I can try to check for errors
feral iris
acct_1Mgs6mFsxVqrj2TH
rare sedge
Did the email provide a contact email you can reach out to?
feral iris
no, but there's a message Id if that's helpful:
Need to refer to this message? Use this ID: em_7cvhnatknsm4jsairhm4gfaki4oq09
rare sedge
Yeah I don't see any such errors on your account
But I recommend clicking that "let us know" link
And reaching out
Just to see if there's some other underlying issue
feral iris
So I should open a case with support?