basementfilms

[fathom salmon]

In other words how can we tell **if **a card always requires authentication?

[viscid harness]

Basically we are wondering if there's a way to detect if the card being used is setupintent -capable or not.
I'm not sure what this means. All cards should be capable of using Setup Intents.

this leads us to displaying two back-to-back authentications for the user
If you're creating Setup Intents to charge the card, then you shouldn't need to present them with authentication a 2nd time. You should just pass the already authenticated Payment Method in for creating the payment. Setup Intents are used to charge customers who aren't currently on-session, so you don't need them to be present for that step at all

[fathom salmon]

when we tried to charge the SetupIntent using the payment method created while setting up, we received an error "This card needs authentication".

We need to use PaymentIntent in order to really charge the card.

With PaymentIntent, we didn't receive the error and the payment went through.

Also the SetupIntent document clearly states that SetupIntent is only used to setup card for future usages.... And if the card cannot be setup in this case - setupIntent can't be use to apply the charge.

[viscid harness]

Also the SetupIntent document clearly states that SetupIntent is only used to setup card for future usages
Yes, but if you create the Setup Intent first, then authentication should happen during that step and you would create the payment afterward (which would be a future payment)

You need to dial in your Setup Intent flow first and foremost such that it authenticates the customer and results in a usable Payment Method.

[fathom salmon]

Thanks for your reply - but how about when using this test card for example: 4000002760003184
where it always requires authentication (for future usage as well)

it works for the card that is "Authenticate unless set up", ie. 4000002500003155

[viscid harness]

I'm not sure I understand what you're asking

That's a test card that will always require authentication, regardless of if it is needed or not. This will behave entirely different in a live environment, as you won't have a card that always requires authentication no matter what

[fathom salmon]

ok understood, but that's interesting - how confident are you that there is no such card that always requires authentication in live environment?

we were under the impression that was a card for testing so that we'd be prepared for live environment situations where the card always needs authentication.

[viscid harness]

No, that is just used to test the flow where you know you'll need to authenticate (e.g. on first payment attempt)

[fathom salmon]

ah ok I think that's what threw us off and sent us in the wrong direction - thanks a lot for clearing that up!