julia-zheng

6 ms·

1.
Dyneti (YC W19) is hiring software engineers(dyneti.com)
1 points by julia-zheng 7y ago
2.
by julia-zheng 8y ago
Exactly - the effort required for this much beyond what most fraudsters would be willing to do on most platforms.
3.
by julia-zheng 8y ago
Interesting - would love to get more context if it's possible to share
4.
by julia-zheng 8y ago
Interesting - we're currently only detect credit card fraud for the segment of customers transacting with more typical credit cards (the largest chunk of the market) but this is good to know.
5.
by julia-zheng 8y ago
So actually acquiring stolen cc numbers is very easy - there's a bunch of marketplaces that sell thousands of them. Figuring out a scalable way to extract value out of them, however, is hard. More than visible or invisible barriers, wh
6.
by julia-zheng 8y ago
Hahahaha they're all cancelled or expired cards :)
7.
by julia-zheng 8y ago
Amazing - thanks for all the feedback. This is definitely on the roadmap - stay tuned!!
8.
by julia-zheng 8y ago
Currently it's only available on iOS and Android apps, with mobile web coming soon. We're still working out exactly what the experience will look like on desktop (it's a less natural flow for sure), but once we work out the k
9.
by julia-zheng 8y ago
Hope it helps - good luck!!!
10.
by julia-zheng 8y ago
For the most part the model should generalize pretty well to new formats, but we do constantly monitor and update to catch up with any holes.
11.
by julia-zheng 8y ago
Thanks!
12.
by julia-zheng 8y ago
Cool!! Until we have enough transaction volume, we are replicating methods fraudsters use to create fake cards to train our models.
13.
by julia-zheng 8y ago
Thanks!
14.
by julia-zheng 8y ago
Great question! The company that owns the app is ultimately responsible for the encryption there, but there are a few ways we can help out with that as well (sorry, I know this is a terrible answer - but it's best practice not to revea
15.
by julia-zheng 8y ago
Definitely take the below with a grain of salt - this worked for me thus far but there are probably paths other people have taken that worked equally well or better :) My recommendation would be: 1) A smaller/less established team whe
16.
by julia-zheng 8y ago
Thank you! The photos of cards aren't stored anywhere - everything is analyzed on device to ensure privacy and compliance. Re privacy policy - thanks, gotta put that up!
17.
by julia-zheng 8y ago
Thanks! Just sent you an email :)
18.
by julia-zheng 8y ago
Great question! The small proportion of cards that can't be scanned can be pushed through a higher friction fraud prevention flow. Since card scanning is low friction, this allows you to catch a ton of fraud at minimal impact to good u
19.
by julia-zheng 8y ago
Thanks for sharing that - super helpful to know. Definitely agree it's possible to make good fake cards, but it makes it difficult enough that fraudsters will usually migrate to a different platform. Since banks are probably the most a
20.
by julia-zheng 8y ago
Whoa you know a lot about Card.io! Apple does have great card scanner. Our thoughts on this (would love to hear yours) are they have little incentive to open up the card scanning tech standalone for developers, but even assuming they did, t
21.
by julia-zheng 8y ago
A stripe integration out of the gate would be REALLY nice :) Thanks so much for the feedback! Just put it on my to-dos
22.
by julia-zheng 8y ago
There's a number of ways that a fake card will look different from a real card - we aggregate these signals and form a decision on real vs fake (sorry, we know that's a terrible answer - we would disclose more, but it's best
23.
Launch HN: Dyneti (YC W19) – Helping apps stop fraud and process payments faster
60 points by julia-zheng 8y ago|58 comments