Google Pay amount displaying 0 in confirmPlatformPaySetupIntent

[Filippo39]

In my application, setupIntent is used for payment management, where in some cases the price is known and in others it is not. In Android, the confirmPlatformPaySetupIntent function does not allow setting the displayed amount (it always shows €0.00) nor a label to provide more details to the user.
After doing some research, I noticed that a similar issue has already been resolved for Flutter.
flutter-stripe/flutter_stripe#1250

I was wondering if it would be possible to get the same modification for React Native.

• Device: Redmi Note 10
• OS: Android
• Version 11
• SDK version 0.27.2

[charliecruzan-stripe]

hi @Filippo39 ! Could you provide some more info for me to reproduce Google Pay showing 0 for the price? On my device the price isn't showing (either for payment intents or setup intents) and in Google's docs, it states "This price is not displayed to the user." so they state you should show the price in your own UI.

[Filippo39]

@charliecruzan-stripe I'm using:

const { error } = await confirmPlatformPaySetupIntent(
  res.data.clientSecret,
  getStripeConfirmParam(...)
)

where getStripConfirmParam returns for google:

  googlePay: {
    testEnv: testEnv,
    merchantName: 'Test SRL',
    merchantCountryCode: 'IT',
    currencyCode: 'EUR',
    existingPaymentMethodRequired: false,
  },

and it shows:

[charliecruzan-stripe]

thanks! It was the merchantCountryCode- I guess Google shows this for EU countries. I've asked the stripe-android team about this, but in the meantime you can use createPlatformPayPaymentMethod which does let you set an amount

[tillh-stripe]

Hi @Filippo39 👋 I’m from Stripe’s Android team. We reached out to our contacts at Google to understand whether we can just pass in a null amount for setup intents. If that’s possible, it would hide the Pay merchant line entirely. I’ll let you know once we hear back.

[Filippo39]

Hi @tillh-stripe, it would be nice to have the possibility to show a custom amount for android, in order to keep consistency with ios:

applePay: {
    cartItems: [
      ...cartItems.map(
        (item) =>
          ({
            label: item.label,
            amount: X,
            paymentType: PlatformPay.PaymentType.Immediate,
          } as PlatformPay.CartSummaryItem)
      ),
      {
        label: 'Total',
        amount: totalAmount,
        paymentType: PlatformPay.PaymentType.Immediate,
      },
    ],
    merchantCountryCode: 'IT',
    currencyCode: 'EUR',
  },

[tillh-stripe]

Makes sense. I’ll look into making that possible!

[dmengelt]

@tillh-stripe passing in a null amount is not possible. I believe what @Filippo39 suggested (aligning with Apple Pay) is the best solution going forward.

Technically, there is a way to "hide" the Pay merchant line by setting totalPriceStatus=NOT_CURRENTLY_KNOWN. However, this should not be used for EEA countries and therefore isn't a solution in this case.

[tillh-stripe]

Gotcha, thanks for confirming, @dmengelt.

@Filippo39 I’ll look into adding support for a custom amount on Android.

[tillh-stripe]

We just merged the necessary change on Android: stripe/stripe-android#7191

Once @charliecruzan-stripe adds the necessary React Native support, you’ll be able to provide a custom amount (and a custom label!) for setup intents.

[Filippo39]

Unfortunately, despite this change, I continue to see €0, perhaps there is a block on the part of Google Pay

  googlePay: {
    testEnv: testEnv,
    merchantName: 'Test SRL',
    merchantCountryCode: 'IT',
    currencyCode: 'EUR',
    existingPaymentMethodRequired: false,
    amount: 10,
    label: 'Label'
  },

[charliecruzan-stripe]

hi @Filippo39 , this is working for me on the most recent version, using the same code you shared above-

Are you sure you're on the most recent version?

[Filippo39]

Yes it works, I had to clear the node modules after updating the library, thanks

[Filippo39]

@charliecruzan-stripe
I still have two questions:

• There is a reason why on Android an amount of amount: 100 corresponds to 1€ while on iOS an amount: 100 corresponds to €100
• Also according to GooglePayBaseParams the amount and label should be two optional fields, but if I avoid settings them, a crash occurs
  

[charliecruzan-stripe]

There is a reason why on Android an amount of amount: 100 corresponds to 1€ while on iOS an amount: 100 corresponds to €100

Different behaviors of Apple Pay/Google Pay. I'll reflect that in the docs.

Also according to GooglePayBaseParams the amount and label should be two optional fields, but if I avoid settings them, a crash occurs

Fixed this, sorry about that!

[tuanlevi95]

There is a reason why on Android an amount of amount: 100 corresponds to 1€ while on iOS an amount: 100 corresponds to €100

Different behaviors of Apple Pay/Google Pay. I'll reflect that in the docs.

Also according to GooglePayBaseParams the amount and label should be two optional fields, but if I avoid settings them, a crash occurs

Fixed this, sorry about that!

what is the docs of Different behaviors of Apple Pay/Google Pay.?