Skip to content
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

Card validation failing with some specific cards #2465

Closed
ghost opened this issue May 11, 2020 · 2 comments · Fixed by #2467
Closed

Card validation failing with some specific cards #2465

ghost opened this issue May 11, 2020 · 2 comments · Fixed by #2467
Assignees
Labels
triaged Issue has been reviewed by Stripe and is being tracked internally

Comments

@ghost
Copy link

ghost commented May 11, 2020

For some specific cards, Android SDK is reporting invalid card number (card number field in red in the widget, while iOS sdk says ok and adding the card manually to stripe works.

It seems that isValidCardLength in CardUtils is returning false. This seems to happen because getPossibleCardBrand is returning Unknown for these cards (they are correctly identified in iOS).

This has happened to us until now with Mastercard Maestro cards, but we don't have enough data to guarantee that the problem is related just to those. I think it would be nice if both SDK's had the same validation rules.

I could reproduce it in SDK version 14.4.1 and 13.2.0
Probably not android/device dependant.

Sadly, I cannot give the specific card nubers to reproduce because it's sensitive information.

EDIT: Here is the bin as asked: 561243

@mshafrir-stripe
Copy link
Collaborator

@hmercade thanks for filing. Can you share the BIN of the card you're testing with? This would be the first 6 numbers of your card.

@ghost
Copy link
Author

ghost commented May 11, 2020

Edited the issue with the BIN number

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged Issue has been reviewed by Stripe and is being tracked internally
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant