You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2019. It is now read-only.
@dgoldman-ebay @josharian
Regarding issue #50, I was wondering if the Python library and scripts needed to generate/modify models were ever going to documented and released in the future. Given that more cards with non-embossed digits and various digit patterns are cropping up, it would great if developers were allowed to make the models more inclusive of those changes.
The text was updated successfully, but these errors were encountered:
Unfortunately, I'm afraid that I (who am no longer working for PayPal) am not able to devote any time to dealing with this. 😿
There's a rather big collection of somewhat idiosyncratic scripts (especially idiosyncratic after I took them over from the much neater @josharian), which would need to be cleaned up, refactored, and heavily documented.
(They're also closely tied to a database of images of actual credit cards, which cannot be shared publicly.)
Thanks Dave. I think folks in the open source world can figure out and clean up those scripts, that's the beauty of open source. Of course, the card images should remain closed. Who at PayPal or former card.io folks do you think might be able to help? Maybe Tom Whipple or Brent Fitzgerald?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@dgoldman-ebay @josharian
Regarding issue #50, I was wondering if the Python library and scripts needed to generate/modify models were ever going to documented and released in the future. Given that more cards with non-embossed digits and various digit patterns are cropping up, it would great if developers were allowed to make the models more inclusive of those changes.
The text was updated successfully, but these errors were encountered: