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

add dangerouslyGetFullCardDetails capability to PaymentSheet #1510

Open
abedolinger opened this issue Sep 19, 2023 · 1 comment
Open

add dangerouslyGetFullCardDetails capability to PaymentSheet #1510

abedolinger opened this issue Sep 19, 2023 · 1 comment

Comments

@abedolinger
Copy link

Is your feature request related to a problem? Please describe.

Hi there, we have a similar use case to these issues:

where we would like to use the user's payment details for two transactions without needing the user to re-enter them. However we currently use the PaymentSheet component, and would like to keep doing so. Is there any way to get the card details from the PaymentSheet?

Describe the solution you'd like

A param dangerouslyGetFullCardDetails could be added to PaymentSheet.SetupParams, which perhaps could only be true if customFlow is also true. Then the card details could be returned inside the PresentPaymentSheetResult.

Describe alternatives you've considered

We could migrate our payment flow to the CardForm for example, but would like to avoid that if possible.

@abedolinger
Copy link
Author

Bump on this, wondering if this is possible! Thanks @charliecruzan-stripe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant