#mebezac - 3ds question
tulip trench
Thanks!
limber estuary
Sorry. Many threads open rn. Taking a look
It won't be for everything in the future
I recommend reading this as well: https://stripe.com/docs/payments/3d-secure#manual-three-ds
To get a better understanding
tulip trench
Yeah that document didn't mention if things in the future would be affected or not, so I wanted to make sure, thanks!
tulip trench
Thanks for all your help!
limber estuary
Can you share the SetupIntent ID?
tulip trench
seti_1KcLde2R3kkGxJkDeqTRda31
limber estuary
You could see with webhook events if a setupintent required auth: https://stripe.com/docs/api/events/types#event_types-setup_intent.requires_action
But there's no way to verify that the actual popup was properly displayed to the user from the stripe side
You could also retrieve the SI to get it's status: https://stripe.com/docs/api/setup_intents/retrieve
tulip trench
ok
limber estuary
Looks like that particular SI had this issue: https://stripe.com/docs/error-codes#setup-intent-authentication-failure
tulip trench
Are there banks where the 3DS process doesn't work with Stripe.js
limber estuary
If the bank supports 3ds, stripe will show the prompt
tulip trench
👍
tulip trench
One more question 😬 :
Is there any way using the PaymentElement in Stripe.js to force the collection of the cardholder's name? I see that you can set it to never or auto, but I don't see a way to always ask for it. https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails-name
limber estuary
I don't believe there's a way to force it
Have you tried submitting the form and just leaving the name blank?
Does it succeed?
tulip trench
It's not asking for the name, we want to make it ask for the name
worldly siren
Hi @tulip trench, stepping in for @limber estuary who needs to step away. I can confirm that Payment Element doesn't currently support forcing name always. I recommend using never and creating your own name form if you want to always collect name.
tulip trench
ok
Also, if using PaymentElement from stripe.js, if we want to use Apple Pay, does that still require verifying our domain, even though the Stripe.js creates an iFrame of a Stripe domain?
worldly siren
Nope you do not need to verify your domain when using Payment Element
tulip trench
awesome!
worldly siren
🙂
tulip trench
Will a card added using Apple Pay to a SetupIntent (save and use later) act any differently than a card added using "normal" CC detail fields?
or once it's tokenized and in Stripe, does it just act like all other cards?
worldly siren
Pretty much works the same. Recommend testing it out!
tulip trench
Didn't want to test it out on live customers without knowing that it will behave the same as a "normal" card during subscription renewals
worldly siren
You don't need to test on live customers.... you can still test Apple Pay in test mode.