#lslavuj
crystal cypress
winter skiff
Do you have an example pi_xx?
foggy canyon
yes, just a sec
winter skiff
Are you aware of SCA regulations?
foggy canyon
pi_3MFRJIEDp185F5gg1s20Yq8u
yes, our app is for USA market
i dont understand why when we used charges Api and the previous version it never asked us for the 3d secure confirmation
winter skiff
SCA can still apply and be enforced in the US, this is becoming more and more common
winter skiff
i dont understand why when we used charges Api and the previous version it never...
Because those APIs were build years along, long before SCA regulations and 3DS. Continuing to use them now would result in failed payments and declines
foggy canyon
yes we know, we will try to changes this in couple of weeks, just ned to do q auick solution for now
winter skiff
pi_3MFRJIEDp185F5gg1s20Yq8u
In the case of this payment, the issuer/bank requested authentication. You need your customer on-session to complete the required auth flow and confirm the payment: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment
foggy canyon
but what are then this rules?
i disabled the 3ds if required?
this is a screenshot from the stripe dashboard
winter skiff
Those rules are irrelevant in cases where the bank/issuer explicitly requests or requires 3DS. Those Radar rules allow you to force 3DS in certain scenarios, regardless of whether the bank requested it.
foggy canyon
so there is now way to forcibly skip the 3ds authentication?
winter skiff
Not if requested by the customer's bank/issuer no
foggy canyon
what if i setup the payment intent like this: setup_future_usage='off_session', is it possible to skip the 3ds?
ok
winter skiff
what if i setup the payment intent like this: setup_future_usage='off_session', ...
That would likely help reduce 3DS/auth requests for any future off-session payments, but the initial payment would likely still require 3DS from customer
foggy canyon
hmmm i check it now, before we switched to the newest version we used charges api with stripe version '2019-12-03'. And we never got a request to confirm 3D secure. How is that possible?
dim abyss
Hello 👋
ynnoj had to step away
Give me a moment to catch up
3DS is mostly enforced by banks/issuers. I don't think change in the API version should affect it. I see that you have the radar rule disabled as well. So unlikely that these are triggered/enforced by Stripe. If the bank/issuers tell us to authenticate, we have to authenticate 😅
foggy canyon
yup i just don't know how our charges api version '2019-12-03' di not have the problem with that
and latest version with payment intents is forcing us 3ds
dim abyss
that's highly unlikely 😅
However, if you feel strongly about that then you can write into our support to see if there's a way to downgrade the API version on your account. They might be able to help you with that.
foggy canyon
ok tnx
all of the time we were using charges api and '2019-12-03' version we did not have any 3D secure request. After we upgraded to the latest version and started using payment intents we have at least 10 3d secure requests
dim abyss
I understand but like I mentioned above this isn't something Stripe enforces (so API versions shouldn't affect these). We purely follow the instructions provided by the issuers/banks! I'd recommend talking to our Support team as they can also look into your auth rate and if they find anything concerning, they'll be able to raise it internally.