Wrote 20 replies for Reddit threads about tools like Stile in r/fintech, r/saas and r/startups.
- 1 found this week
- 20 replies ready
- 3 communities
Best identity verification service right now?
It depends less on the brand and more on three things, so test those before you commit. 1. Pricing mechanics. Per-check is easy to compare, but find out what counts as billable. Do retries count? Do failed liveness attempts count? Are there monthly minimums once you leave the free tier? 2. Coverage in your regions. Ignore the "190 countries" line. Ask for the document types supported in the specific countries you serve, and run real IDs from those places through a sandbox. Also test liveness on cheap Android phones, since that's where it usually breaks. 3. False rejects. Ask what reason codes you get back, whether there's a manual review fallback, and how retries work. Push 50 to 100 genuine samples through and count how many good users get bounced. Since this is a privacy sub, also ask what they keep. Some vendors hand you raw ID images, others return only a result. The less you store, the less you have to protect. Stile (disclosure: I work on it) is $0.25 per full check with 1,000 free a month and returns a signed result without raw files, so it's one to put in the comparison. Whatever you pick, run the same test set through each.
Are deepfake checks becoming a separate requirement ...
Short answer: yes, it's becoming its own line item, because selfie-to-ID face match and liveness solve different problems. Face match asks whether the selfie looks like the ID photo. Liveness asks whether a real person is in front of the camera right now. Deepfakes and virtual cameras attack a third thing, the capture channel itself, so you need injection detection as well. What I'd do before buying anything new: 1. Test your current flow. Replay a recorded video, feed a face-swap through a virtual camera, and try a screen-held photo. See what passes. Most teams skip this and just trust the vendor's marketing. 2. Ask your vendor specifically about injection attacks (virtual cameras, emulators, hooked SDKs), not just presentation attacks like masks and printed photos. Check whether they have independent test results, e.g. iBeta PAD levels or CEN/TS 18099 for injection. 3. Look at signals outside the selfie: device integrity, session behavior, and whether the document image itself is a fresh capture or a screenshot. 4. Add step-up checks only on risky events like payout changes, account recovery and high-value limits, not on every signup. Regulators haven't set one standard yet, so document your threat model and test results. That's what auditors will ask for.
Is building identity verification in house realistic for a seed ...
I'd split it by which parts get worse over time versus which parts are yours by nature. Buy these: 1. Document reading. The long tail of formats is the problem, and local IDs vary by issue year. Where possible, don't rely on OCR alone. Read the MRZ, barcode or chip, and check against the issuing source (NIN or BVN lookups, for example). 2. Liveness. A selfie held to a laptop screen is a presentation attack. Ask any vendor for independent ISO 30107-3 test results, not a marketing claim. 3. Sanctions and PEP data. Lists change daily and you need fuzzy matching across transliterated names. Licence a feed rather than scraping lists. Build these: 1. Decision logic: thresholds, when to escalate, when to reject. 2. The audit trail. Log the decision, timestamp, list version screened against, reviewer and rationale. That is your regulatory record. 3. Alert review workflow for screening hits. Outsourcing the checks doesn't outsource accountability, so own the decision layer and keep components swappable.
Which KYC API is actually good for a small fintech?
Most providers make the same claims, so compare them on what the marketing pages skip. 1. Separate identity verification from KYC. Document, liveness and face match confirm the person is real and matches the ID. Sanctions, PEP and adverse media screening is usually a different product, and so is ongoing monitoring. Check what your regulator requires before assuming one vendor covers both. 2. Build your own test set. Use real IDs from the countries you'll serve, worn documents, bad lighting, older phones. "Supported" on a coverage list says little. Pass and false-reject rates on your own set say a lot. 3. Read how retries are billed. Per-check versus per-attempt pricing matters when some users need three tries. 4. Ask what comes back. If you get raw ID images, you now store and secure them. A signed result plus an audit trail is less liability (disclosure: I work on Stile, which works that way, though it's aimed at identity checks, not sanctions screening). 5. Check the manual review fallback and whether webhooks are signed.
How long did your identity verification vendor take to go live?
Real numbers will be hard to get from sales, so ask for a go-live checklist and make them fill it in before you sign. Four things I'd pin down: 1. Security review scope. Ask for their standard questionnaire answers and SOC 2 report up front, and send yours at the same time. Data residency and retention clauses were what stretched Persona in the comment above, so get your legal team reading the DPA during the demo phase, not after signature. 2. Webhooks. Give them 5 or 6 of your real case shapes (resubmission, manual review, expired session, partial fail) and ask them to show the exact payload for each. If your case model doesn't map, you find out in week 1, not week 6. 3. Sandbox. Ask directly: can I force a decline, a retry and a review outcome with test inputs? If the answer is no, price in extra time for testing in prod with a small cohort. 4. Ramp. Agree a shadow mode or a 5% traffic cutover in writing, so the date that counts is real traffic, not the contract date. Anyone who balks at putting a date next to each item is telling you something.