#streetfeels
1 messages · Page 1 of 1 (latest)
Hi there
So you are passing requestPayerEmail when you create your paymentRequest (https://stripe.com/docs/js/payment_request/create#stripe_payment_request-options-requestPayerEmail )?
I did pass that in yes
But you aren't seeing email stored for the Billing Details on the PaymentMethod?
Interesting, can you give me an example PaymentMethod I can look at?
And is this happening in both live/testmode or just one or the other?
just testmode
Can you provide me the PaymentMethod ID from your Google Pay test?
pm_1N1BOiFfzadd3IOMD68vNiyA
Ah this is Payment Element
Not PaymentRequestButton
There is no way to force email collection for wallets when using Payment Element
so I have the PaymentRequestButton that loads
and am clicking the PaymentRequestButton and not the PaymentElement
Hmm well that PaymentMethod was created via https://dashboard.stripe.com/test/logs/req_Fe1FINg60YSi34 where you can see the payment_user_agent specifies it came from Payment Element
ok, we're using both technically, we're trying to have the user ONLY use the PaymentElement when they choose to enter the CC and the PaymentRequestButtonElement when it's available
(for google and apple pay)
Sure okay so when you create your PaymentElement set wallets to never then: https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-wallets
And then can you run another test?
ah okay - now I understand
I have ApplePay enabled on the paymentElement, when it is the chosen element, instead of a confirm button I show the PaymentRequestButtonElement
Would that still process via the PaymentElement flow?
Hi there 👋 taking over, as my colleague needs to step away
I don't understand the question. Bismarck had you disable G-Pay and Apple Pay on the Payment Element, but then you come back and say "I have ApplePay enabled on the paymentElement, when it is the chosen element". What are you actually trying to do here?
Ok I think I'm a bit confused about how to implement the PaymentButtonRequestElement essentially.
Does it need an onClick handlesubmit function, what function do I need to call upon clicking it?
The Element itself should have an .on() method. This step here illustrates a way to do that: https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-complete-payment
Ahh okay, so that's what was happening
Ok, and through that the contact and email can be passed thru to the webhook?
I don't understand. What contact and email are you referring to?
Are you talking about address?
ultimately we just want to ensure that the email name fields populate when the user uses the PB Request Element
without having to ask for it explicitly
we were hoping it would be possible to access it via the webhook, and Stripe would be able to get it from Apple or Google Pay
I believe they're stored on the Customer object, which you can access via the payment_intent.succeeded webhook. You have to explicitly request them during this step though: https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-create-payment-request-instance
ah okay!
let me check it real quick
ok, so ONLY name is showing up in that intent.succeeded object - - but that's because of the way I have payment request button set up right now which I believe is incorrect.
Ok, thanks for your help now, I will revert after making paymentRequest.on change