Szymon

[mortal beacon]

For #1 and #2 can you clarify what you mean by "automatically confirmed" here? It sounds like that means "when confirm is called, the SetupIntent goes to succeeded rather than requires_action"?

[static kettle]

Exactly - although I thought that every setup intent first goes to 'processing' status and only then I get notified about this status via webhooks?
Anyway - yes, I mean here that the setup intent changes its status from 'processing' to 'succeeded' without any external action

[mortal beacon]

Some payment methods, mostly bank payment methods, go in to the processing state, most others immediately go to succeeded (or requires_payment_method if they fail)

Ah gotcha, so here you would even consider a card with 3DS to be an "automatic" setup because it is confirmed while the user is still on your site rather than finding out via a webhook later?

[static kettle]

II don't think it's actuallly true: I have one ugly usecase when one user adds other's cards in bulk. I'm trying to figure out whether it's fine if I display some waiting screen while waiting for setup intent to change its status to 'succeeded' - I don't think 3DS would work since it might take too long and obstruct the process; if I can expect many cases when 2FA is required it seems we need to do it more asynchronously (although this would harm the UX)

[mortal beacon]

For credit cards, the confirmation will always be immediate or require 3DS (and be immediate after 3DS is confirmed). Card setups won't go in to a processing state

For that use case, you can choose to just not allow cards that require 3DS during that initial setup but if someone wanted to add those cards, 3DS would need to happen at some point

[static kettle]

Great - thank you!