-
Notifications
You must be signed in to change notification settings - Fork 984
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
[Feature] StripeCardScan ScanCard only has the card number and no expiration date #2875
Comments
Hi @littlematt . Can you share with us more about the problem that you are facing? Any relevant code snippet, screenshots or screen recordings, as well as the version of the SDK will be helpful here. |
Hi,When the SDK recognizes the bank card, it only recognizes the bank card number, but it does not recognize the expiration date |
Hi, the model ScanCard has only one field "pan" |
Hi @littlematt are you referring to the ScannedCard structure? I've added your request to our internal backlog. |
+1 on this one, as this is something we are also interested in :) |
+1 on this one. The bummer is that internal classes do recognize whole card information. But unfortunately |
hey @seanzhang-stripe do you know a timeline for this? |
This is an issue for us too. We're not sure why those other values are blocked. |
This is also a duplicate of #2484 |
) ## Summary Remove `@_spi` for `ScannedCard` properties. Fixes #2484 and #2875 ## Motivation In order to autofill our card entry form we need the scanned details, but for some reason they're blocked from being publicly visible. ## Testing N/A ## Changelog [Changed] `ScannedCard` to allow access for `expiryMonth`, `expiryYear` and `name`.
This was fixed in #3539. |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: