#castle-payment-3DS
1 messages · Page 1 of 1 (latest)
Correct!
Yeah, off_session: true would be a good way to do this
If off_session is true, that won't cause non secured cards to be declined would it?
It could still cause non-3DS cards to decline, but they'd likely decline anyways (like they probably would've declined on-session as well)
Gotchya, thank you. And you wouldn't think there are any other concerns to worry about using off_session=true
@upbeat robin we would really strongly recommend just supporting 3DS honestly. In this industry and all the rules around theworld, you're going to lose real revenue just to save some dev time early on and regret it later
castle-payment-3DS
Also passing off_session: true is only allowed if you are telling us the truth: your customer is not on your website/app trying to pay. You are not allowed to pass off_session: true just to try and skip 3DS
Well my concern is, we went from Stripe::Charge -> Stripe::PaymentIntent and previously 3D secure payments were automatically returned as card_declined, now we have renawals coming with 3D Secure cards and they're going into an incomplete pending staus, I'm really just trying to match parody from what we had with Stripe::Charge to Stripe::PaymentIntents, I can defintely add it so that off_session=true is only applying to the renewals where the customer isn't present. Also open to other alternatives.
what does that mean "we have renewal coming" exactly? Renewals usually imply some kind of recurring monthly payment in which case those would be off session right?
We manage our reoccurring subscriptions manually and just use stripe as a payment method.
I also saw in the documentation:
off_session
Use off_session if your customer may or may not be present in your checkout flow. So I was under the impression this was an acceptable option
@prime umbra
If there's an option you'd recommend just in the mean time to match parody to reject 3DS I'd love your recommendation. I'm happy to make a ticket for the team to implement it later, it's just for the time being I want to match the existing functionality.
If your customer is on your app paying -> on session, handle 3DS
If this is a renewal your own system trigger like a cron job monthly -> customer is not on the app -> off session, it will skip 3DS (and might say "sorry but the bank asked for 3DS get your customer back on your app to pay")
Can do, thank you.
is anything else unclear that I could help with?
I think I'm good, appreciate your help