#thomasst-checkout
1 messages · Page 1 of 1 (latest)
Thanks!
so the main thing is that the card was entered via Google Pay, so I suspect what happens is we set up the Google button to ask for a billing address but that's all that the customer had configured in their account so that's all we get. But looking if we have any docs on this.
So do we need to disable Google Pay (anything else?) or is there a way checkout can force the user to add an address after they do Google Pay and there isn't one?
I wouldn't suggest disabling Google Pay, since that would be a large drop in conversion, it's a very popular method.
This is what we told another user about this in the past :
When a customer checks out with Apple Pay or Google Pay we use the addresses stored on the customer's digital wallet. This dependency exposes us to issues with the collection of customer information on the Apple and Google side. In the vast majority of cases those address are full and correct. But, in a small number of cases the addresses stored are incorrect or incomplete. This is as a result of small issues that have occasionally surfaced in the Apple or Google UIs that collect customer information for their digital wallets. These missing address fields, and sometimes phone numbers are long-lived remnants of transient glitches with the Apple and Google collection forms.
which is basically what I thought, we ask Google for the address but we just get back whatever the customer has actually saved, we have limited control there.
So really the question is how important the address is for you and what you need it for and to balance the requirements
We need it for automatic tax collection.
yeah that's what I thought and that was the case for the case I got that comment above from
this is why in Checkout we disable Google Pay if you turn on automatic_tax by the way
Interesting. "When you enable Stripe Tax in Checkout, Apple and Google Pay are only available to customers for sessions that require collecting a shipping address. Apple Pay with Stripe Tax displays only when the customer’s browser supports Apple Pay version 12." -- so sounds like it's not an issue with Apple Pay v12 then? (https://stripe.com/docs/payments/checkout/taxes)
there's unfortunately nothing else really I can suggest. It's an extremely small number of overall transactions that are missing data, your example is extreme as it's even missing the postal code, which is extremely rare in our data
Actually, since we don't ask for shipping, Apple Pay would not display either way it sounds like.
yeah we are actively working with Apple and Google on this
which is why it's getting better on Apple but it's all WIP
Thanks
right now if you need the full address you have to collect shipping as well(which doesn't work for digital merchants so that's not great), we're trying to work with the wallets to make the billing address more complete