#steffen-paymentelement-applepay

1 messages · Page 1 of 1 (latest)

old slateBOT
fathom birch
#

@crimson knot You shouldn't see Apple Pay at all as a button if it's not set up so I don't really understand what you describe. Do you have step by step instructions on how to reproduce?

#

steffen-paymentelement-applepay

old slateBOT
crimson knot
#

ApplePay was set up on the device, so the button should be there. But the person testing said that they had a "wrong" card connected to ApplePay at first. That's the case I'm describing. In a second attempt with a different card, it actually worked and the payment went through fine.

glossy lion
#

Hi, stepping in here to further assist. I do not undertsand what "wrong" card connected to ApplePay means here. Can you explain what this means?

glossy lion
#

Are you there?

crimson knot
#

yes

#

I don't have any more detailed info on that. I just know that payment didn't work and there was no Stripe error. After using a different card on the device with Apple Pay set up, it worked. I guess I just need to know if the same confirmPayment() call is made when ApplePay is used, or if there is a different way to catch errors when using Apple Pay

glossy lion
#

I still do not understand what error you expect. The way ApplePay works is that the end customer would have to have a card added to their wallet. It that card is properly set up on thr wallet, they would see Apple Pay button. If not, they won't see this as an option.

crimson knot
#

as I said, Apple Pay was set up on the device, so the button showed up as it should. My question is how to catch any errors that may come back from the ApplePay process

#

With a regular card payment, I get errors back in response to the confirmPayment call. But that appears to be different for wallet payment methods?

glossy lion
#

After they are redirected to the Apple Pay pop-up, if the payment fails, the pop-up would say that the payment failed and they can close the window to add a new payment method to try to pay.

crimson knot
#

ok, I guess that's what I needed to know. So the error would always be in the popup for any external payment method like ApplePay, and there wouldn't be a way (or a need) to catch that error in our checkout form.