Live data from Hacker News

Radar – A new set of integrated tools to help prevent fraud

stripe.com

21–30 of 120 posts

Re: Radar – A new set of integrated tools to help prevent fraud

#21
post #12

I like the rotating 3D model in the landing page very much. Are they using some sort of pre-baked library which lets you create such an visualization with 30 lines of Javascript, or is it 100% custom? Maybe someone can point me to a good resource for such elegant WebGL renderings.

They're using Three.js, but it looks like the spinning icosahedron is custom-made with about 300 lines of code. That includes calculating the vertices of the icosahedron, loading the model from a 3D model file, setting up the surface material characteristics, setting up the lights, animation, moving HTML nodes with the labels along with the vertices, and mouse dragging.

Re: Radar – A new set of integrated tools to help prevent fraud

#22

This looks very promising. Stripe seems to have sometimes let surprising payments through up to now, even with all the card details security checks they provided activated, and they've never supported 3-D Secure. They've also suffered from surprisingly high rates of unexpected declined charges in our experience. Hopefully if they're now rolling out more comprehensive fraud protection, that will go some way to address…

(I work on Radar at Stripe) thank you, and do let me know if there's anything we can do to help you get set up on Radar. Additionally, we actually do support 3Dsecure in private beta -- mind emailing me (tara@stripe.com) for access?

Please please please promise that it will always stay optional?

Re: Radar – A new set of integrated tools to help prevent fraud

#25
post #20

I work at a company with a fairly large number of transactions and we don't really have a problem with fraud. I don't know anyone else who's really battled it either. Is it much more prevalent for certain industries and products?

Of course. I sell business software, never had a fraudulent transaction ever. But the video game and porn industries, for example? Tons of fraud.

You can prevent a lot of fraud by simply requiring both a postal code and the CVV on the card. It's unlikely that a card thief has both pieces of data. (If you steal the physical card, you won't have the postal code, if you buy a database of cards, unlikely that they will have CVV's)

Re: Radar – A new set of integrated tools to help prevent fraud

#26

Always gotta hand it to Stripe to build a killer looking landing page

Seriously, the absolute best. Every single time this gets commented:

- Bitcoin: https://news.ycombinator.com/item?id=9077293

- Open Source: https://news.ycombinator.com/item?id=10167198

- Atlas: https://news.ycombinator.com/item?id=11167513

Re: Radar – A new set of integrated tools to help prevent fraud

#27
Just checked our Stripe dashboard and it looks like this has quietly been doing good work for us for many months now blocking suspicious charges. It took me a few clicks to find https://dashboard.stripe.com/search/rules?rule_token=block_i... and after going through a few of them, the per-charge risk factor descriptions are really helpful too. The high-risk reasons are messages like: "This card has been used from an unusually large number of IP addresses across the Stripe network over the last 24 hours." and "This email has been linked to an unusually large number of cards across the Stripe network over the last hour."

Thanks to Stripe for making it not-a-black-box! I hope others who build machine learning systems also find a way to make its decisions understandable by humans (when possible).

Re: Radar – A new set of integrated tools to help prevent fraud

#28
post #13

It's a bit unclear to me; these rules appear to be automated but then they show a rule builder interface? How would I ever know if the rule I've built is too constraining, or too loose in accepting payments? Payment is not exactly an area of my business that I want to do a lot of trial and error..

(I work at Stripe) Stripe's already actioning charges based on the feedback from the machine learning models. We hope that they'll take care of most fraud for you.

If you do want to write custom rules on top of what the models are doing, we've actually built in a testing interface to the rule creation process. When you test a rule, we'll actually simulate what the rule would have done had it been active for the past 6 months. Using that information, you'd be able to tell the # of legitimate, fraudulent, or already blocked payments that would have matched the rule & make a decision on what's best for your business.

That said, we're looking to make our opinion on a given rule more clear (rules are still in beta) and would love more feedback on how we can make this better. Feel free to drop me a line (tara@stripe.com) if you have feedback!

Re: Radar – A new set of integrated tools to help prevent fraud

#29
post #7

What is the advantage of this vs SiftScience or other tools?

The data is from Stripe's handling of 100,000+ businesses' transactions, probably a better dataset than SiftScience. That's a big probably .

doubtful that stripe has 100,000+ business customers. Kount is another good one, that's what Braintree uses apparently.

Re: Radar – A new set of integrated tools to help prevent fraud

#30
post #12

I like the rotating 3D model in the landing page very much. Are they using some sort of pre-baked library which lets you create such an visualization with 30 lines of Javascript, or is it 100% custom? Maybe someone can point me to a good resource for such elegant WebGL renderings.

Glad you like it! We used Three.js (https://threejs.org) to handle rendering the icosahedron itself. Three.js actually includes an icosahedron as one of its built-in primitives, however we also wanted to add some subtle details to the model such as rounded edges. So, we created a rounded version in Cinema 4D, and then rendered both that model as well as an invisible copy of the object using the Three.js primitive. The primitive gives us easy access to things like the vertex coordinates, that are then used to position the labels, which are plain DIVs and not rendered with WebGL.
Post reply on HN