Description
Is your feature request related to a problem? (please describe)
I am trying to develop a platform agnostic solution for shopping, but the differences between Apple and Google Pay sheets make this a very hard deal for me. Below I will explain a bit further why.
Describe the solution you'd like
I clearly understand that there was a specific flow in mind when the package was written, I believe it was to allow these options only when we invoke the platformPayCreatePaymentMethod, but my solution creates the paymentIntent through a different process in the backend, I receive the client secret in the frontend, and I only want to confirm it.
Now two problems arise:
- The apple pay params in platformPayConfirmPaymentIntent() allow for name, number and email. Those for Google allow only for email. With my app I aim to prompt the user to enter these fields in the native payment sheets instead of UI because I strongly believe this reduces friction to purchase. The ideal solution here would be to include those two parameters here too - name, phone number. If this is not possible a clear explanation why and any alternative options would be very heplful 🙏
- Dynamic sheet updating - when I was designing my app, I thought that when the user enters shipping information, the native sheet will have a callback which would call my backend and update the sheet with the new total price after shipping recalculation. Sadly, I found out that Google Pay does not support that either. Is that because the google pay sheet is static by design?
Describe alternatives you've considered
No alternatives. The pay package is not straightforward to work with at all, so I naturally used the methods provided in this package to include the native wallet options.
Thank you very much! Otherwise this is a wonderful package that works pretty well.
George