#m0uka_api
silver troutBOT
👋 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/1473278522238963736
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
distant yacht
hi there 👋
there's no parameter in the API that will 100% guarantee that a payment will benefit from a liability shift, for any card/wallet type
the rules around liability shifts can get quite nuanced, and there can be exceptions where payments do not benefit from a liability shift where it would generally be expected - so it's not something that Stripe can boil down to a single parameter
lusty kite
got it, but there's nothing like the result field on the three_d_secure field on regular card payments for apple pay/google pay payments?
distant yacht
I'm afraid not - the closest thing to that is the payment_method_details.wallet.type property, which will tell you if a card was added via Google Pay/Apple Pay, but it doesn't contain details related to authentication/cryptograms
officially, we say that these payment method types "may" benefit from a liability shift