#cris-moshtix_api
slate 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/1366739076065132624
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
true cliff
Which field on the Payment Intent object/event are you referencing?
vast iron
3DS
true cliff
Sorry, can you link me to the exact field in the API reference
vast iron
In theory, it would be this:
var options = new PaymentIntentCreateOptions
{
Amount = 1000,
Currency = "usd",
PaymentMethodOptions = new PaymentIntentPaymentMethodOptionsOptions
{
Card = new PaymentIntentPaymentMethodOptionsCardOptions
{
RequestThreeDSecure = "any",
},
},
};
But in our integration, is on by default.
We only disable it explicitly if we want to, with this:
Card = new PaymentIntentPaymentMethodOptionsCardOptions
{
Moto = true,
}
true cliff
You're comparing different fields:
request_three_d_securedenotes your 3DS preference: https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-three-ds
It's unclear to me what it is exactly you're trying to do
vast iron
The question is about chargeback liability
true cliff
You can't 'disable' 3DS, if that is what you're asking
true cliff
OK, so if you want to force 3DS for the liability shift then use the parameter I linked above
request_three_d_secure: 'any'
slate vigilBOT
true cliff
We don't really know anything about chargeback/liability shifts here at all really. Other than what is documented here: https://docs.stripe.com/payments/3d-secure/authentication-flow#disputed-payments
vast iron
Please DO NOT consider any API field.
I'm not mentioning anything about it. I want to know about legality issues.
The process we have implemented is the following:
Create SetupIntent
The user goes through 3DS
We correctly save the user CC in Stripe
A few days later...
We run a scheduled task to capture funds
3DS is not processed at this stage, but it was when creating SetupIntent
Are we liable for any chargeback?
true cliff
As I said, we know nothing about liability/chargebacks. We can only help with API/integration Qs. I recommend speaking with support
vast iron
Are u saying NOT Dev Support but Customer Support?
true cliff
Chargeback/liabiltiy shift is not a developer topic. So yeah, you need to speak to support