#TedT
1 messages · Page 1 of 1 (latest)
Hey thanks for the help
So with metadata the right hand does need to be the value of your metadata
I think what you want here is to instead manually output the different countries using IN
Like if ::product_countries_string:: IN ('US', 'CA', etc.)
The countries are set by the product being bought, which has to be metadata
Oh sorry maybe I'm misunderstanding
Right you are dictating that metadata, right?
Oh wait I think I see what you are saying
Basically I'm trying to lock the card country to be within a given list provided by metadata (which sadly can only be strings)
You want the Radar rule to be dynamic
Yeah more or less
Yeah that's not really going to be possible with Radar.
Actually let me think a second
AHh but it's so close haha
There's that new business logic beta thing for doing custom logic before capture but I'm not sure I we should rely on that
./ how long that would take to get set up for our account. The docs are pretty scarce
Yeah I was going to recommend you tokenize prior to confirming and then check the payment method
That is a better way to go imo
You are using Payment Element?
Yeah, it's super convenient aside from not being able to check these things
We want to let users use alipay and things. I have another solution which overrides capture for the card but it's pretty hacky
Okay so this actually will be possible with Radar
And requires hard-resetting the users payment intent because the only option left is cancel. OH?
So you are going to include two different pieces in your rule in that case
You have one piece of metadata for the product
Like you are already doing
And you would have rules for each product that would say Block if ::product_string:: = 'xyz' AND if :card_country: IN ('US', 'CA', etc)
Okay thanks so much for your help
Try that out and let me know if it doesn't satisfy what you are looking for
Think I'm going to go with the cancel flow. Sadly we have too many markets for it to be set for each