Skip to content
This repository has been archived by the owner on Jan 12, 2019. It is now read-only.

Card holder name and expiry date fetch #136

Open
bkmalkoc opened this issue May 10, 2017 · 2 comments
Open

Card holder name and expiry date fetch #136

bkmalkoc opened this issue May 10, 2017 · 2 comments

Comments

@bkmalkoc
Copy link

1- Camera scanner sometimes fetch the expiry date sometimes doesn't.
2- Camera doesn't fetch card holder name.

@phileo
Copy link

phileo commented Sep 27, 2017

does anyone know any of the history and background of the problem with scanning the expiry date?
Scanning expiry date was added in V5.0.0, which was over 2.5 years ago. It was acknowledged at the time that there were issues with scanning expiry date, but with no further detail. If anyone could shed some visibility as to what the nature of the failure is, perhaps I can assist to find a solution.

  • What is causing expiry date scanning to fail so much?
  • Does anyone know which files might be potentially causing the problem ?
  • Is it related to the version of OpenCV being used?

@dgoldman-pdx
Copy link
Member

@phileo you can find some technical background here.

However, the basic problem was that we had a limited set of images of card expiry dates on which to train our deep-learning neural model. Because these cards were from a limited range of years, we had a huge number of example images of 0s and 1s, but very few images of other digits such as 5s. The resulting model is therefore biased to believe that it is seeing, e.g., a 0 or a 1 even when that isn't actually true.

Unfortunately for all involved, by the time we completed the initial expiry scanner, the card.io project was no longer being actively supported by its acquirer. And so the considerable effort that would have been needed to obtain many more card images (under varying lighting conditions) was not possible.

Even more unfortunately, our software infrastructure for obtaining and processing card images for training our deep-learning models involves a lot of code that had not yet been cleaned up and open-sourced. So that code is still proprietary -- and the individuals who created and used it are no longer employed by the proprietor.

So unless the current corporate owner of card.io decides to re-prioritize the project, it's unlikely that expiry scanning will ever be improved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants