-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Troy #22
Comments
If I add "Troy" 3 tests fail because of the IINRange is same as other cards. As you can see "65" falls in these other providers. What to do? [
{
"issuingNetwork": "Discover Card",
"iinRanges": "6011, 644-649, 65",
"active": "Yes",
"length": "16–19",
"validation": "Luhn algorithm"
},
{
"issuingNetwork": "RuPay",
"iinRanges": "60, 65, 81, 82, 508",
"active": "Yes",
"length": "16",
"validation": "Luhn algorithm"
},
{
"issuingNetwork": "Troy",
"iinRanges": "65, 9792",
"active": "Yes",
"length": "16",
"validation": "Luhn algorithm"
},
{
"issuingNetwork": "Verve",
"iinRanges": "506099–506198, 650002–650027",
"active": "Yes",
"length": "16, 19",
"validation": "Unknown"
},
] |
I believe it really is time to think about changing the output and the tests of cardidy. I'll work on that on friday |
Same IIN Range means it is a co branded card. They should identify as both. The order is quite arbitrary. We tried to move the most specific one above the other. Visa Electron being before Visa is a good example of that. |
Yeah, but I think we should give several cards as answers if we manage to meet several valid tests |
@torendil this is what we already do:
|
My bad 😅 @hey24sheep you can correct those tests to include Troy, I believe |
No problem. It happens to all of us. 👍 |
No worries, I have added a PR for Troy. Have a look, thanks :) |
Hello,
I would like to identify card from Troy. You can get Troy traits on Wikipedia.
If you want to solve this issue, check this how-to guide.
Cheers,
The text was updated successfully, but these errors were encountered: