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
Is your feature request related to a problem? Please describe.
We would like to be able to support custom buttons below the primary payment buttons on the WalletHeaderView of the PaymentSheet. I am attaching a screenshot of what this would look like. These buttons would just be passed and stacked, and the associated actions would be handled by the view controller that is presenting the PaymentSheet.
Describe the solution you'd like
Add a new property to the PaymentSheet.Configuration – public var additionalButtons: [UIButton] = []
Pass and store those additional buttons from the configuration in the WalletHeaderView initializer
Append the contents of the additional buttons array in the buildAndPinStackView function in the WalletHeaderView after conditionally adding the payWithLinkButton
The buttons would be completely setup and controller by the view controller that is presenting the PaymentSheet.
Alternatively this could just be an optional UIView passed from the configuration to the WalletHeaderView that would be stacked underneath those buttons.
Additional context
The text was updated successfully, but these errors were encountered:
Thank you for the feature request @virginiacook! To help us understand the use case, what would your app's additional buttons do? Are there other payment methods you'd like to support?
Thank you for your response @yuki-stripe! We would like to support additional payment methods (such as internal credits + other external payment methods that are not yet integrated with Stripe that our account manager mentioned Stripe is working on to support at some point).
We would actually prefer a generic UIView that is stacked below the top buttons on the wallet header view (vs. an array of full-width buttons) so we can have greater control of the configuration of the subview's layout and could add labels/additional images if needed.
I believe other customers will also benefit greatly from this increased flexibility within the PaymentSheet.
Please let me know if I can answer any additional questions and thank you again!
Thanks for the extra details! We don't have immediate plans to support something like that, but we are exploring other ways to make PaymentSheet more flexible. I've raised your use case with the team. We might reach out to you for more feedback or to participate in a pilot program.
In the mean time, have you looked at PaymentSheet.FlowController? It's not very well documented but may be a better fit for your use case. In this integration you'd put a button in your checkout screen (the "Payment method" row in the left-hand side of screenshot) that opens our UI (right-hand side of screenshot). Your checkout screen would also own the buy button, so you could stack other buttons with it.
Is your feature request related to a problem? Please describe.
We would like to be able to support custom buttons below the primary payment buttons on the WalletHeaderView of the PaymentSheet. I am attaching a screenshot of what this would look like. These buttons would just be passed and stacked, and the associated actions would be handled by the view controller that is presenting the PaymentSheet.
Describe the solution you'd like
PaymentSheet.Configuration
–public var additionalButtons: [UIButton] = []
WalletHeaderView
initializerbuildAndPinStackView
function in theWalletHeaderView
after conditionally adding thepayWithLinkButton
The buttons would be completely setup and controller by the view controller that is presenting the PaymentSheet.
Alternatively this could just be an optional UIView passed from the configuration to the
WalletHeaderView
that would be stacked underneath those buttons.Additional context
The text was updated successfully, but these errors were encountered: