Launch HN: Didit (YC W26) – Stripe for Identity Verification
21–30 of 76 posts
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#22Earlier quoted context omitted.
Isn't it useful to pair identity with common reasons to identify? Why else would you ask? Are you saying your fraud detection and speed beats Stripe, or just your price?
Yes, we mog on speed, onboarding rate, fraud detection, and price.
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#23Who would you say is your primary competitor (besides Stripe) and how are you better than them today?
In general I believe we just built a better product:
- Fastest verification on the market (inference time 30 s, ours is less - Optimized onboarding rate worldwide, global coverage, any country, low connectivity and every device accepted, and optimized (different models loading in the client depending on the speed ..etc, and many more tricks)
- Fraud detection (we analize > 200 signals, to detect fraud in real time, from IP analysis, device fingerprinting, replay attacks, deepfakes ...) we got experts on that, and we act quickly if we see new attack vectors appear.
- Developer experience (self-service, pay per usage, API first). You can start doing verifications without needed to use the UI (everything programatic), and integrate in few minutes.
- Flexible, you can create any identity flow with your own rules. You can enable features with just 1 click, no need to reintegrate.
- Pricing model (pay per usage, no monthly minimums, no enterprise gated, and low prices)
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#24Suerte! Unrelated, growing up in Spain it always baffled me that identification was based on a photo on your DNI. Stories of siblings or even friends that had a passing resemblance to each other sharing DNIs was a common story.
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#25Earlier quoted context omitted.
Yes, we mog on speed, onboarding rate, fraud detection, and price.
> Yes, we mog English please
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#26Great to see innovation in this space! If I could make one giant request, it's around giving (properly authorized) humans the ability to override the system when needed. When you make a simple API, it's all too common for a company integrating the solution to rely entirely on the identity service's yes-no outcome. But all too commonly, there's no way to override a decision, or bypass the need for identification. In t…
We also built a case management system so support teams can manually review cases, approve/decline them, or override decisions when needed. Automation handles most cases, but humans can step in for the edge cases.
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#27I certainly didn't do it.
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#28Who would you say is your primary competitor (besides Stripe) and how are you better than them today?
There is many direct competitors in the space, the main ones are Persona, Jumio, Incode, Sumsub, and even orchestrators like Alloy. In general I believe we just built a better product: - Fastest verification on the market (inference time 30 s, ours is less - Optimized onboarding rate worldwide, global coverage, any country, low connectivity and every device accepted, and optimized (different models loading in the cli…
Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#29Re: Launch HN: Didit (YC W26) – Stripe for Identity Verification
#30with all this talk about persona/discord sending identities to the dhs and everything, what steps do you guys take to keep identity information private?
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.
Second, and more importantly, we provide granular data control. Our customers can select exactly which fields they need to keep (e.g., just Name, DOB, and Country) and set the system to automatically purge sensitive assets like ID photos immediately after verification. It’s about ensuring that only the absolute minimum amount of data necessary ever exists in the system.