-
Notifications
You must be signed in to change notification settings - Fork 272
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
Access full card number in onCardChange
callback
#280
Comments
cardNumber
onCardChange
callback
Yes, I think that's a reasonable request, I'll discuss with the team. |
Thanks @thorsten-stripe - any ideas on when this could happen? I'm happy to add a pull request if you think the above suggestion is sensible |
We're working on this now. It will be part of the v0.1.3 release later this week. |
@obates you don't need access to the CVC, correct? I don't see a usecase where you would, but do let me know if I'm wrong. |
Correct. Thanks for jumping on this so fast |
@thorsten-stripe I'm only using the I was thinking that the CVC field could be accessible when Please let me know. |
Same as @juanolmedogl. It would be nice to have access to the CVC field! |
Is your feature request related to a problem? Please describe.
We use Stripe to take card payments, and a 2nd payment provider to send money to a card. We want to use the Stripe Card component to collect card details & submit them to both Stripe and the 2nd payment provider at the same time (fully PCI compliant).
In order to do this, we require access to the full card details (number, expiry, etc) for sending.
Currently, the
stripe-react-native
library explicitly hides the full card number from theonCardChange
callback, despite this being a feature in the respective native libraries (#68).Describe the solution you'd like
Expose the full card number in the
onCardChange
callback, to align with the native iOS/Android libraries.To address the concerns in the comments in the above-linked PR (#68 (comment)), an additional prop could be added to the card component e.g.
dangerouslyGetFullCardDetails
?Many thanks,
Oli
The text was updated successfully, but these errors were encountered: