#JoeAdroit
vast locust
quartz stone
Hi 👋
Can you share a request ID where this is occurring?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
chrome orbit
req_Yc6YCImDuzfxp7
This is on stripe.confirmCardPayment customer using prev. payment_method
I've explicitly set to auto going forward, but older payment_methods seem to be affected
quartz stone
Yikes. there are a lot of requests on this Payment Intent
chrome orbit
Yeah..
quartz stone
I don't know what to tell you except that it was explicitly created with confirmation_method: "manual",
You can see that here: https://dashboard.stripe.com/logs/req_eQ6dWB4t4yMvaW
chrome orbit
Right. Weird we weren't getting these before. Just started a week ago
Can this be controlled somewhere else e.g. security rules on stripe.com dash?
I have an idea
quartz stone
This request was made with your accounts secret key and PHP code
chrome orbit
Re-use of an old payment_intent. I'm putting a block on intents with confirm_method manual
Added. Weird it was just never enforced before. We haven't changed anything on creation and have been auth. via JS awhile. I don't see anything in the Intent Creation req. body calling for confirm_method = manual
https://dashboard.stripe.com/events/evt_3LAsthF5MBsWwkQH19wyDHJP
quartz stone
That event is too old. I can't see anything about it on my end
But looking at older logs for you account it looks like you were using a 3rd party service to create Payment Intents.
This one, for example: https://dashboard.stripe.com/logs/req_IHt3gEuP9g4fqd
chrome orbit
In that example, I don't see confirmation_method in Request, only response. Is that default?
quartz stone
It just means it wasn't passed in so it defaults to automatic
chrome orbit
Ok, but PI with confirmation_method is my issue. I've since set confirmation_method = 'automatic'. Just curious how the error started occuring with confirmation_method = 'manual'
quartz stone
As I said, it's what was provided by your PHP code