#akhil_om
ancient geode
dense rapids
no
when I gave such a transaction to your support team, they said the following - "I can see in the case the reason why this is not complete is that the customer has not completed 3d secure authentication with there bank for this charge."
sick comet
do you use stripe checkout or custom?
sterile linden
@dense rapids can you give me an example PaymentIntent that I can look at? Is your integration set up to handle 3DS?
sick comet
are you handling the case of 3d secure on client side then?
dense rapids
we are not handling anything with 3d secure
sterile linden
So yeah looks like the customer just didn't complete 3DS here
There isn't really any action that you need to take
If you want, you could cancel the PaymentIntent
sick comet
you should check for payment intent next_url in that case and redirect the user for 3d secure authentication.
dense rapids
and let the merchant know that patient authorization is needed for this transaction
what if the user called via phone to make a payment to the merchant?
sterile linden
@sick comet this user isn't setting a return_url so they aren't handling the 3DS redirect here
If the customer called via phone then that is considered a MOTO payment
It is important to classify these as MOTO correctly so that 3DS is not requested. See: https://support.stripe.com/questions/mail-order-telephone-order-(moto)-transactions-when-to-categorize-transactions-as-moto
You'll want to reach out to our Support team to request access to the MOTO feature if you are taking payments over the phone.
In terms of these PaymentIntents that are in requires_action, you really don't need to do anything with them
You don't want to cancel them right after they move to requires_action as that stops the customer from being able to authenticate. If you want to do clean up later on, you can use https://stripe.com/docs/api/payment_intents/cancel to cancel them
dense rapids
thanks for the MOTO suggestion, a fair number are over the phone or customer handing the card to a front desk person.
sterile linden
Yeah then you definitely want to look into MOTO so that 3DS isn't requested on these
dense rapids
appreciate it; for the MOTO, is there anything we need to do on the API calls?
and is that setting for each connected account or can that be setup at the platform level?
sterile linden
Yes there is a small adjustment to the API call. You can set it at the platform level — no need for each Connected Account to have the feature.
Next step is to get approval from our Support team and then they will provide you with the relevant docs to set up your integration to utilize MOTO