#fenwicks_silent_assassin
pine notch
marble merlin
Hi there!
Two things to clarify here: test mode calls do not generate emails
the other thing is that the 3DS email you're referring to will only be sent if 3DS is required and a customer is not on session
if a PaymentIntent's status changes to requires_action as part of confirming a payment client side, there's no need to send the customer an email since they're actively trying to pay
vagrant cliff
Ok so i'll need to test in live. The customer is off_session, as the client cannot confirm the authentication
The checkout is on a POS machine and only the user has access to the checkout screen
not the customer
This is why we wish to use emails
marble merlin
Hold on a sec. If this is on a POS machine, does this mean this is a card present transaction?
vagrant cliff
We have the ability of saving cards for future use and one-off payments where the card is present during transaction
marble merlin
To be clear, is your team using a physical card reader for this integration?
vagrant cliff
Reader payments is another type of payment the platform accepts, yes
We essentially want the customer to receive an email to authenticate their payment if the Payment Intent requires a 3D secure confirmation rather than using the checkout screen
marble merlin
How is the customer providing their payment details for this payment?
vagrant cliff
They have the card on hand and provide the user of the platform their card details
so by voice? Not sure how technical we need to get into this
marble merlin
Got it. Stripe Elements is intended to be used if/when a customer is typing in their own payment details and is going through the payment flow themselves, not using a POS machine
vagrant cliff
Which is why we were thinking we could use an email for 3DS authentication?
marble merlin
No, that's not the best way to go about this. 3DS is intended to be used with card not present flows
if your customers are processing a payment in person, they would ideally use a card reader to securely transfer their payment details to your integration
no 3DS required
vagrant cliff
Ok well there is a scenario where the customer will not have the card on them as they have already saved the card in the system for future use. So there is no way to confirm 3DS authentication unless the card holder is infront of the screen?
marble merlin
You can use off_session to indicate that you're creating the PaymentIntent without having your customer in the checkout flow. Then, if 3DS is required, you can use that Dashboard setting to send emails to customers