You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi there, we have a similar use case to these issues:
onCardChange
callback #280CardField
whendangerouslyGetFullCardDetails=true
#903where 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.
The text was updated successfully, but these errors were encountered: