#sandy.nozaki
low wadi
clear jackal
Hi there, you can learn more about liability shift here https://stripe.com/docs/payments/3d-secure#disputed-payments
weak pewter
this area "..complete the payment," means capture right?
like we can't auth and authenticate with 3DS at check out then later when we are ready to capture do it on the merchant side?
clear jackal
If the 3DS authentication isn't successful, the PaymentIntent won't be in requires_capture state and you can't capture it.
weak pewter
does 3DS have to occur at the time of capture?
like what if we have 3DS authenticate at the time of check out and then have our merchants/connected accounts auth or auth/capture when they are ready to ship the goods (which would also change the final amount)
clear jackal
No, 3DS happens after you confirm the PaymentIntent (the PaymentIntent status will become requires_action), that happens before you capture it.
weak pewter
so currently, our customers/cardholders check out but they dont really go thru the process of authorization and/or capture at the time of check out.
once they check out, our merchants confirm the order where they auth/capture when they are ready to ship the goods at which they update the amount due to shipping fees.
clear jackal
Is the amount that you hold < the amount that you capture (include the shipping fees)?
weak pewter
we dont hold anything
when customers check out they just place an order
but no auth is made
clear jackal
Hmm? I thought you are doing manual capture? https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
weak pewter
no we dont
so in our case, i guess if we wanted to use 3DS we would have to notify the customer to return to us to go thru the authentication once the final amount is confirmed?
in which would qualify for liability shift?
hello
clear jackal
Thanks for waiting.