Hacker News new | ask | show | jobs
by cwillu 18 days ago
> it could also be fraught if Stripe was in the business of blocking customers from their entire network based on one vendor's complaint

“You probably don’t want a system where one annoyed merchant can get someone blocked across the whole Stripe payment system. But there’s a pretty big gap between “automatically block this person everywhere” and “thanks for the screenshots, please consider Radar”, and this is where it gets frustrating.”

1 comments

There is no gap between those things. Any fraud signal at all either causes people to get blocked, then it's a cross-merchant block, or it doesn't cause people to get blocked, then it's useless.
The gap between “block on first signal” and “ignore the signal entirely” exists, and it is not small.
The gap between "block transaction" and "don't block transaction" is nonexistent and that's the only thing that actually matters. What else are you, as a payment processor, gonna do besides block a transaction? Allow the transaction but send the user a sternly worded email?
False dichotomy is false; good day.
You repeatedly failed to describe any third option. Good day.