.ishkanan

[sick goblet]

Hello! Feel free to drop more details

[frank locust]

Howdy! Details incoming..

We've integrated with the Payment Intents API and are testing some Google Pay transactions in sandbox. We're listening to the "paymentmethod" event and noticed sometimes there'll be some fields missing from the billing details.

I managed to track it down to Google Pay sometimes not enforcing customers to complete their billing details (so seems like it's not a Stripe issue). BUT I was wondering Stripe was aware that could be the case sometimes and if so what advice you might have?

We're deciding between 1) silently substituting billing with the shipping details (which are always complete) OR 2) advising the customer to complete their GPay setup (which hurts conversion)

[sick goblet]

Give me a few minutes to dig in

[frank locust]

Thank you 🙂 sorry for the wall of text

[sick goblet]

Just to make sure - you're definitely passing in requestPayerName: true, right? Or are you not using the PaymentRequestButton and doing somethign else?

[frank locust]

We're using the PaymentRequestButtonElement component from the @stripe/react-stripe-js npm package. Doesn't seem we're passing requestPayerName: true to it though. But we have definitely received all billing details once I corrected the missing information in my GPay account.

[sick goblet]

Ah, looks like Google Pay collects it by default (Apple Pay strictly required you to pass in requestPayerName: true to collect billing details)

[frank locust]

My apologies, we are indeed passing the flags for payer name, email, phone and shipping!

[sick goblet]

Yeah I don't think there's any way around this right now - even for us, we require shipping address to be collected to use Applepay/google pay with our automatic tax feature on checkout so that we have a guaranteed address we can tie back to the payment

[frank locust]

Thought that was the case! All good, thanks for your help. We'll probably go with option #2.

[sick goblet]

👍