#andywells-direct-3ds
1 messages · Page 1 of 1 (latest)
we're using the payment intents API
and setting the account header to our customer's account
and you goal is to have 3ds fire as much as possible?
yep
i've set the rules on our platform account's radar ruiles
but this doesn't seem to have any effect
gotcha, thats expected. with direct charges, the radar rules of the connected account are what's applied (since they "own" the payment and responsibility for it etc)
but you can influence this via each api request, too
using request_three_d_secure=any:
https://stripe.com/docs/payments/3d-secure#manual-three-ds
who's liable for Fraud: would it be the connected account?
with direct charges, yes
https://stripe.com/docs/connect/direct-charges
Direct charges are recommended for Standard accounts. The connected account is responsible for Stripe fees, refunds, and chargebacks.
gotcha
are standard connected accounts able to modify this setting and override the value we send in our request?
they could set a radar rule that was higher to request 3ds even if you did not, but they couldnt lower the bar if you request it.
@latent cipher Sorry to inject myself here, but I had some problems with exactly this paramter when creating Subscriptions. It didn't adhere to this and sent back automatic instead of any. I talked to someone on here yesterday about but I can't find the thread and I would like to follow up on this so I can be notified when this is rectified.
ok it was Pompey I see now scrolling back. But given that I didn't email in about this I have no connection to the issue.