This feels like something that would get me to abort a signup flow. Unless it's something that has a really good use for the information (a bank, maybe?), this would raise identity theft warnings. Even if there was a good use, it would still be something I'd have to think about.
I'm sure you've already looked into this before, but signing up for N26 involved a very awkward, stressful video chat that lasted 30 minutes to verify the authenticity of my passport.
Seeing as how you process data in Frankfurt, perhaps they would be interested. I'm sure users would appreciate it - I'd be happy never to have another one of those calls again.
You hit the nail on the head - this type of problems is exactly what we try to solve. Someone like N26 would ofc be a dream customer. If there are any N26 employees here, hit us up ;)
> N26 (known as Number 26 until July 2016) is a German neobank headquartered in Berlin, Germany. N26 currently operates in various member states of the Single Euro Payments Area (SEPA) and in the United States.
It worked after 2 tries on my iPhone with a Canadian passport (initially, the RFID step didn't read anything).
Interestingly, I think that you may have the rgb channels wrong during the photo extraction -- the photo was "correct" but the colors were wrong (maybe b and r are flipped?)
I tried another app [0] just to double check and it decoded the photo correctly.
I also found/read a bit of info from the Canadian government about epassports [1]. One interesting tidbit that was news to me: "For the chip [...] to be read, [...] the date of the individual’s birth, the date of expiration of the passport and the passport number must also first be provided to the reader". i.e. the RFID chip does an exchange/check first rather than spit out everything to any nearby RFID reader.
I suppose it's not feasible to brute force all of those pieces of data (passport expiration, etc.) fast enough to read passports in RFID vicinity.
Do you verify that the document is signed by a country's CA, and if so, do you have a list of countries and document types that you are able to validate against (since procuring the CAs is probably the more annoying bits for this type of service).
Yes (we keep a CA list). We are familiar with ReadID, but as far as I know they can only provide chip reading. Our solution on the other hand includes MRZ reading + chip reading + face verification + liveness verification
How did you get the German Personalausweis to comply? It is supposed to require a complex dance involving a remote server and certificates as well as a PIN before divulging the data.
From what I can tell, they aren't using the eID functionality, but a combination of OCR and the same functionality that passports have. That was added to new documents last month I believe?
Allow users to sign up (or similar) by tapping their ID/Passport. Integrate by using our apps, or iOS/Android SDK if you have an app on your own, or even C++ for embedded solutions
Almost. It may simplify verification, but only for people who present passport books; you don't legally get to choose which documents to accept for I-9[1]. US Passport cards are RFID-enabled, but not NFC-enabled, for example.
[+] [-] trothamel|4 years ago|reply
[+] [-] vertical-ally|4 years ago|reply
[+] [-] hammyhavoc|4 years ago|reply
[+] [-] junon|4 years ago|reply
Seeing as how you process data in Frankfurt, perhaps they would be interested. I'm sure users would appreciate it - I'd be happy never to have another one of those calls again.
[+] [-] vertical-ally|4 years ago|reply
[+] [-] mschuster91|4 years ago|reply
[+] [-] moreati|4 years ago|reply
> N26 (known as Number 26 until July 2016) is a German neobank headquartered in Berlin, Germany. N26 currently operates in various member states of the Single Euro Payments Area (SEPA) and in the United States.
[+] [-] sturza|4 years ago|reply
[+] [-] gregsadetsky|4 years ago|reply
It worked after 2 tries on my iPhone with a Canadian passport (initially, the RFID step didn't read anything).
Interestingly, I think that you may have the rgb channels wrong during the photo extraction -- the photo was "correct" but the colors were wrong (maybe b and r are flipped?)
I tried another app [0] just to double check and it decoded the photo correctly.
I also found/read a bit of info from the Canadian government about epassports [1]. One interesting tidbit that was news to me: "For the chip [...] to be read, [...] the date of the individual’s birth, the date of expiration of the passport and the passport number must also first be provided to the reader". i.e. the RFID chip does an exchange/check first rather than spit out everything to any nearby RFID reader.
I suppose it's not feasible to brute force all of those pieces of data (passport expiration, etc.) fast enough to read passports in RFID vicinity.
[0] https://www.readid.com/demo-app
[1] https://www.canada.ca/en/news/archive/2014/05/technical-info...
[+] [-] vertical-ally|4 years ago|reply
[+] [-] Deathmax|4 years ago|reply
An existing company in this space would be ReadID (https://www.readid.com/).
[+] [-] vertical-ally|4 years ago|reply
[+] [-] OJFord|4 years ago|reply
Seems to me with many things it's relatively easy to get say 100k sign-ups, compared to 100k active profitable users. Could be pretty costly.
[+] [-] jpalomaki|4 years ago|reply
If the alternative option is for example something that requires human, then this is likely quite much cheaper.
[+] [-] vertical-ally|4 years ago|reply
[+] [-] mschuster91|4 years ago|reply
[+] [-] mschuster91|4 years ago|reply
[+] [-] zeeZ|4 years ago|reply
[+] [-] vertical-ally|4 years ago|reply
[+] [-] amluto|4 years ago|reply
There’s a chip that uses NFC. It may well be a secure element, but calling it “biometric” seems like a stretch.
[+] [-] vertical-ally|4 years ago|reply
[+] [-] black3r|4 years ago|reply
[+] [-] ZeroCool2u|4 years ago|reply
[+] [-] Denatonium|4 years ago|reply
[1]https://www.uscis.gov/i-9-central/handbook-for-employers-m-2...
[+] [-] toomuchtodo|4 years ago|reply