#k3davis

1 messages ยท Page 1 of 1 (latest)

stark cedarBOT
meager nexus
#

Hi karbi! This is related to req_BMNE95bvxG1GsV

crisp frost
#

Hello! Let me take a look

meager nexus
#

thank you ๐Ÿ™‚

crisp frost
#

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

meager nexus
#

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?

crisp frost
#

Hmmm.... maybe i'm looking at the wrong thing - give me a few more minutes

meager nexus
#

no hurry, thank you

crisp frost
#

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?

meager nexus
#

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

crisp frost
#

Yeah it looks like this feature is only meant to be supported with card payments - not generally for other payment method types

meager nexus
#

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?

crisp frost
#

Yup, that's my understanding as well

meager nexus
#

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.

crisp frost
#

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

meager nexus
#

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

crisp frost
#

๐Ÿ‘ happy to help!