#k3davis
1 messages ยท Page 1 of 1 (latest)
Hi karbi! This is related to req_BMNE95bvxG1GsV
Hello! Let me take a look
thank you ๐
Is there a particular doc you're following? As far as I can tell payment_method_data[radar_options] is only available on PaymentIntents, not SetupIntents
i was following this doc, which doesn't actually mention setupintents. but the radar options are available on the setupintent payment method data in the .net sdk, so I made an inference that the same data could be provided. https://stripe.com/docs/radar/radar-session#create-radar-session
is the only way to use this via setup then to do a payment intent with setup_future_usage ? because I don't actually want to collect a payment now in this situation
this might be a bug in the sdk if that property really isn't supported?
Hmmm.... maybe i'm looking at the wrong thing - give me a few more minutes
no hurry, thank you
I think this is because you're using this with a us_bank_account Payment Method - is there a specific reason you're doing this?
well, as far as I understood from a chat with @cosmic stag earlier, this radar session stuff only applies to situations where you're not using stripe.js to confirm. we're using stripe.js to confirm CC's, and the only other method we accept is ACH direct debit, which we are creating server-side due to the verification method we're using.
of course it's possible I misunderstood what he said also ๐ but it does look to me like the .net sdk is creating a request that the api doesn't actually support
Yeah it looks like this feature is only meant to be supported with card payments - not generally for other payment method types
interesting
so i don't get any benefit from using it at all, since i'm doing CC via stripe.js the standard way, and it doesn't do anything for ACH?
Yup, that's my understanding as well
ok. well that's a bummer, there was a message in the dashboard that led me to pursue adding this in the first place ๐ seems to have been a rabbit trail
i still think there's an sdk bug but i guess it doesn't affect me if i can't use this anyway. thanks for looking into it.
Yeah I hear what you mean - it's not exactly a bug in the SDK, it's more of a side-effect of the way we've structured payment_method_data and we should probably be changing that error message to be something more descriptive (like mentioning you can't use radar_options with non-card payment types)
Generally our client-libraries don't have much logic that prevent you from setting combinations of params in your request - all the logic would be happening server-side
Better messaging would help if that's indeed the whole issue, since it says the radar_options parameter itself is invalid but I guess it's only invalid in concert with the type of payment method I provided
anyway - I'm content to remove it since it sounds like it doesn't give us anything, and ignore the dashboard nags. ๐ thank you
๐ happy to help!