#maayanvia
1 messages · Page 1 of 1 (latest)
What exactly do you mean? You can't control whether 3DS is requested on card payments no
Let me clarify my question . Can i enforce 3DS with create-checkout-session?
https://stripe.com/docs/payments/paypal/set-up-future-payments?webhook-or-success-url=success-url
as far as i understand when creating a setupIntent object i can choose weather to control the 3DS by myself (manually) https://stripe.com/docs/payments/3d-secure#manual-three-ds
Thanks !
No, that parameter is not available via Checkout. The only way you can 'force' 3DS with Checkout would be via a Radar rule.
ok. if we are using stripe connect . will we be able to define a different Radar rule for each account ?
Depends if it's Direct or Destination charges I think
if the charge will be from Paypal, for example?
not sure I follow, the payment method type is orthogonal to the Connect charge model(https://stripe.com/docs/connect/charges#types) you use.
ok thanks for the documentation i'll read it.
We are using Destination charges . is it possible to define different Radar rule?
not directly I think. Depends specifically what you're trying to do; you could for example add metadata to your payment objects, and then create rules that reference specific values of metadata to enforce blocks or actions https://stripe.com/docs/radar/rules/reference#metadata-attributes