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
We're trying to use GooglePayPaymentMethodLauncher to prompt the Google Pay sheet and collect payment methods for future usage. However, displaying pricing information on it is not convenient for us since we apply a fee based on the payment method type (credit or debit). Our plan is to show the fee information in our UI after the user selects a card from their wallet, allowing us to display accurate pricing.
Since the totalPriceStatus field (see code) is set by default to Estimated, usage of GooglePayPaymentMethodLauncher implies providing a price via the totalPrice field (see code), otherwise, a 0 value will get displayed. We definitely don't want this behavior.
We discovered there's a NotCurrentlyKnown value (see code) for TotalPriceStatus. We experimented with it in a sample Google Pay integration project from Google and it has the effect we want, see this picture:
hjdealba96
changed the title
[QUESTION] Is it possible to make totalPriceStatus parametrizable in GooglePayPaymentMethodLauncherContractV2.Args?
[QUESTION] Make totalPriceStatus customizable in GooglePayPaymentMethodLauncherContractV2.Args
Feb 19, 2025
Summary
We're trying to use
GooglePayPaymentMethodLauncher
to prompt the Google Pay sheet and collect payment methods for future usage. However, displaying pricing information on it is not convenient for us since we apply a fee based on the payment method type (credit or debit). Our plan is to show the fee information in our UI after the user selects a card from their wallet, allowing us to display accurate pricing.Since the
totalPriceStatus
field (see code) is set by default toEstimated
, usage ofGooglePayPaymentMethodLauncher
implies providing a price via thetotalPrice
field (see code), otherwise, a 0 value will get displayed. We definitely don't want this behavior.We discovered there's a
NotCurrentlyKnown
value (see code) forTotalPriceStatus
. We experimented with it in a sample Google Pay integration project from Google and it has the effect we want, see this picture:Here's the sample code used:
We want to know if there's a chance to make this field parametrizable to support use cases like ours.
The text was updated successfully, but these errors were encountered: