


Nope, as I already said the SDK do *not* return any field. You shared a JSON in private and it's not from us.
I guess is someone else developed the app
and you're new on it. Check with your colleagues.
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/9aac1092-39ac-416e-a9ac-06d2488251edn%40googlegroups.com.
When I try with https://www.doubango.org/webapps/kyc-documents-verif/ I see that what you're referring as being document number is returned as personal number.
For me what we're returning is correct:
Document number: AA0012890
Personal number: 5352431
You have shared the Side B, we look at the Side A (front) below the portrait you'll see "5352431" which is the personal number.
I'd say your assertion is not correct unless you can share an official document.
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/1MuUWi-1pldZE1YDS-00rWO1%40mrelayeu.kundenserver.de.
- "Paraguay - Id Card (2023).jpg" is Side A of Paraguayan newest Id card
- "Paraguay - Id Card (2023)-result.png" is the result you get when you try with https://www.doubango.org/webapps/kyc-documents-verif
- The #7-digits (0000000) below the portrait is the unique number (personal number)
- You haven't shared your Side A but if you check it you should see "5352431" which corresponds to what https://www.doubango.org/webapps/mrz returns
- "Paraguay - Passport #3-result.png" is
the result you get went you try with a Paraguayan passport. "3122656" is the personal
number (also #7-digits). Above you have "Q568928" which is the
Document/Passport number. The #7-digits number is referenced as
"cedula de identidad / Identity number".
if you think we're wrong, then switch
'DocumentNumber' and 'PersonalNumber'
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/1M1INQ-1qdm8x093i-002m1A%40mrelayeu.kundenserver.de.


Ok, let's do this: go to https://github.com/DoubangoTelecom/ultimateMRZ-SDK/tree/master/samples/c%2B%2B/recognizer, read how to run the sample recognizer and try it on your machine. You can also use the recognizer with other languages (Python, Java, C#...). Use the recognizer with your images and share the console outputs with me.
You can also check the console outputs by yourself and you'll notice that THERE IS NO "PersonalNumber" or "DocumentNumber".
We told you in public and in private several times, again and again and again... the JSON response you're getting isn't from us.
Your license was activated on 27 Oct 2021 (2 years ago), I guess the person who developed the module is no longer working there and you're new on it.
Our company is based in Paris (France) and we've many customers there. If you try the french id card (https://en.wikipedia.org/wiki/National_identity_card_(France)#/media/File:French_Identity_card_1988_-_1994.jpg) with https://www.doubango.org/webapps/mrz/ you'll see that the result is *not* correct. We know it and we don't fix it on purpose. The result is correct with https://www.doubango.org/webapps/kyc-documents-verif on purpose.
To make is simple: The SDK returns the raw
MRZ without parsing any field. It's up to you to parse the
fields.
Since version 0.1 we decided NOT to include MRZ field parsing in the SDK to avoid nightmares. The MRZ format can change depending on the card type, country, version.... and most importantly the date of release. UltimateMRZ is a one-time payment license with a very low price, we cannot afford to send too much time on maintenance without being paid. So, this is why we do not return any field when you use the SDK.
This said, we wanted to help our customers and to do it:
1/ we added documentation explaining how to parse the fields: https://www.doubango.org/SDKs/mrz/docs/MRZ_parser.html
2/ we added a standalone sample app (outside the sdk): https://github.com/DoubangoTelecom/ultimateMRZ-SDK/tree/master/samples/c++/parser
The parser at https://www.doubango.org/SDKs/mrz/docs/MRZ_parser.html strictly follow the standard and we will not change it to make it work with Paraguayan or French id cards. Because if we do so, we'll have requests from Belgians, Senegalese, Brazilians... and that's exactly what we don't want for this project. Our new product (https://www.doubango.org/webapps/kyc-documents-verif) will correctly parse and return the fields because it has monthly based support.
Quote from https://www.doubango.org/SDKs/mrz/docs/MRZ_parser.html: "If you’re dealing with non-standard formats and struggling to write the right regular expressions then, don’t hesitate to contact us via our dev-group and we’ll help you."
This is exactly your case, you're dealing
with non-standard format but the big issue is that you seem to
not know where your parser comes from. I can help you but you
MUST provide info and code from your parser. I can't help you if
I don't know where your parser comes from. Again, the SDK do
*not* return any fields and the JSON you showed us in private IS
NOT from us.
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/e0cb2031-e0fa-414d-a1ed-a3942035701fn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/c6dcd8fc-80d0-07cb-b3f2-6beac16a454b%40doubango.org.