#tarjei_unexpected

1 messages ¡ Page 1 of 1 (latest)

valid vigilBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1240279953304719390

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

bold orchid
#

hi there!

#

it's the bank that decides when to run 3DS or not. so your system needs to handle that possibility.

#

which means: ask your customer to go back to your website/app, and re-confirm the PaymentIntent linked to the Invoice to trigger the 3DS flow.

lusty vigil
#

we are doing this as part of a subscription service

#

so what we want to be able to do is to just allow a customer to change their payment method, including going through the 3d secure process once

#

and then subsequently use that method for the future invoices on that subscription

#

is that doable?

bold orchid
#

including going through the 3d secure process once
that's not really up to you. the bank may decide to request 3DS during the SetupIntent, and then during each following payments.

lusty vigil
#

should probably have mentioned that we were doing subscriptions

bold orchid
#

that's why you need to handle the case where 3DS is requested, event if the PaymentMethod is already saved on the customer.

lusty vigil
#

aha

#

I see

#

Ok, thank you, we were unaware of that particular caveat

bold orchid
#

just to be clear: Stripe will try to avoid running the 3DS flow for subscriptions. but ultimately it's up to the bank and may happen, that's why you need to take that into account.

lusty vigil
#

Ok, thanks. One quetion - let's say our customer updates their payment method and goes through the 3ds as part of that process. If the customer is past due and we then automatically try to pay the latest unpaid invoice, is there a chance that the customer will need to go through the 3ds process again?

#

I'm guessing that too is just up to the bank?

bold orchid
#

that would bet a SetupIntent + a PaymentIntent? if so, yes it could be two 3DS. but in this case you could try directly paying the PaymentIntent with setup_future_usage, to make sure there would be maximum one 3DS.

lusty vigil
#

Ok great, thank you