#macintoshpie
dapper kraken
hot valve
Hello! Can you clarify which billing address information you'd want / how you were hoping to use it in radar?
vapid vale
Howdy, I think the goal would be to follow the "gold standard" recommendations (https://stripe.com/guides/radar-rules-101#other-best-practices), but I'd be hesitant to make changes too drastic at once (we have a fair amount of international customers and I'm not sure what the impact might be). So maybe billing zip at first (again following common radar rules: https://stripe.com/guides/radar-rules-101#commonly-used-radar-rules)
hot valve
gotcha - so going back to your original question, were you collecting any billing information at all for the existing payment methods/customer you have? Were you not collecting the zip/postal code rpeviously?
As a general recommendation, I'd say that it would be better to do Block if :address_zip_check: = 'fail' instead of Block if :address_zip_check: != 'pass'. Blocking all payments that do not specifically pass the zip check is likely too restrictive (since some issuers choose to not check the zip even when it's provided to them, and the value for address_zip_check in that case would be unchecked)
vapid vale
were you collecting any billing information at all for the existing payment methods/customer you have? Were you not collecting the zip/postal code rpeviously?
correct, we have not been collecting billing information when users check out.
hot valve
Gotcha - I think the suggestion I made of using Block if :address_zip_check: = 'fail' is the best in that case. Payments made with your paymentmethods that did not provide a zip code will have address_zip_check: null and not fail, so they wouldn't be blocked by that rule
vapid vale
ahh nice! We'll give that a shot, thanks!