Live data from Hacker News

Launch HN: Didit (YC W26) – Stripe for Identity Verification

news.ycombinator.com

51–60 of 76 posts

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#51

There are a bunch of competing companies in that space but it's true that transparent pricing and self-service is rare. Good idea to focus on that.

To me that’s a winner if I’m paying for a SaaS. If I have to go through a procurement cycle to talk to you instead of busting out my card I’m probably going to look and make sure no one else is remotely equivalent first that does self service. If someone else is giving rough feature parity and offers self service they will always win. Even if the self service is more expensive the convenience of me not having to talk to you is gonna get outweighed by that.

I don’t need to chat with you where you do a q&a where you decide what the correct amount of money to extract out of me is. Price your service accurately and accordingly instead and you’ll get my business

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#53

[flagged]

Totally agree. That low-end device gap is exactly where the most sophisticated fraud hides.

Honestly, the "fundamental" fix for the adversarial stuff is just a really tight feedback loop. We lean hard into monitoring—combining customer feedback with internal outlier signals—so we can analyze shifts in real-time. Once we identify a pattern, it’s just about speed.

Sometimes an update means a full AI model retrain, other times it’s just a quick logic or product tweak. In this space, if you can’t iterate faster than the fraudsters, you’ve already lost. (which is the problem of 99% of the companies in the space, they are not able to detect fraud, and if they detect it and they want to push a fix, is already too late)

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#55

This is really cool (especially considering that the pricing is way better than Persona/Stripe Identity)! That being said, what security measures does Didit take, and has it gone through e.g. auditing or SOC 2?

Thanks! We have ISO27001, iBeta PAD, and about to receive SOC 2. We also do bug bounty programs, and pen-testing.

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#56

[flagged]

Totally agree. That low-end device gap is exactly where the most sophisticated fraud hides. Honestly, the "fundamental" fix for the adversarial stuff is just a really tight feedback loop. We lean hard into monitoring—combining customer feedback with internal outlier signals—so we can analyze shifts in real-time. Once we identify a pattern, it’s just about speed. Sometimes an update means a full AI model retrain, othe…

Another AI slop programmed answer; is this thread just bots to hype this product up or what?

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#57

There are a bunch of competing companies in that space but it's true that transparent pricing and self-service is rare. Good idea to focus on that.

To me that’s a winner if I’m paying for a SaaS. If I have to go through a procurement cycle to talk to you instead of busting out my card I’m probably going to look and make sure no one else is remotely equivalent first that does self service. If someone else is giving rough feature parity and offers self service they will always win. Even if the self service is more expensive the convenience of me not having to talk…

agree 100%

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#58

with all this talk about persona/discord sending identities to the dhs and everything, what steps do you guys take to keep identity information private?

I don't have the full context on the Persona/Discord story yet, but our philosophy is that identity providers should be a shield, not a source of risk. We address this by building privacy-preserving architectures that minimize the data footprint. First, we offer secure, long-term retention so companies don't have to store sensitive PII on their own servers—which are often managed by teams who aren't cybersecurity spe…

> We address this by building privacy-preserving architectures that minimize the data footprint. First, we offer secure, long-term retention so companies don't have to store sensitive PII on their own servers—which are often managed by teams who aren't cybersecurity specialists.

What privacy preserving architectures are you implementing? How are you securing PII?

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#59

with all this talk about persona/discord sending identities to the dhs and everything, what steps do you guys take to keep identity information private?

I don't have the full context on the Persona/Discord story yet, but our philosophy is that identity providers should be a shield, not a source of risk. We address this by building privacy-preserving architectures that minimize the data footprint. First, we offer secure, long-term retention so companies don't have to store sensitive PII on their own servers—which are often managed by teams who aren't cybersecurity spe…

If you don't "have the full context on the Persona/Discord story" you should work on getting it.

It's literally the first thing that came to mind when I saw your post and not having a convincing/satisfying answer in direct relation to that catastrophe doesn't bode well for getting people to trust your brand. The rest of your answer is essentially the absolute minimum I'd expect from a business like this, but not sufficiently convincing.

Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification

#60
What’s your extraction layer under the hood? BlinkID? Regula? KBY? Another IDV provider? Self-hosted OCR model/extraction layer?

This is an interesting concept but the identity space is extremely crowded. It’s hard to find a specific niche and aggressively scale it unless you already have a strong end-user persona in mind, precisely because interacting with “the real world” is super nuanced and complicated at any appreciable scale.

Post reply on HN