TheBro

[cyan anvil]

Hey there

[misty vortex]

hey

[cyan anvil]

Are you working with Payment Element?

[misty vortex]

yes

and using

const stripe = useStripe()
... 

stripe.confirmPayment(...)

[cyan anvil]

Gotcha what are you doing in your submit handler?

Do you call confirmPayment immediately?

Or do you do some other stuff like call your backend?

[misty vortex]

the call gets invoked on button press with the following payload

{
 elements,
 confirmParams: {
  return_url: `${HOST}/order/${orderId}`,
 },
 redirect: 'if_required',
}

no other backend calls are made

[cyan anvil]

Hmm that is very strange

Can I repro somewhere?

[misty vortex]

can i DM you a testing env is that ok?

[cyan anvil]

Yep that works

[misty vortex]

It looks like you have DMs blocked by non-friends

[cyan anvil]

I accepted your friend request

Thanks, taking a look

[misty vortex]

let me also add it sometimes works as well

[cyan anvil]

Hmm

And you aren't using Connect, right?

[cyan anvil]

Hmm yeah just worked fine for me.

[misty vortex]

pi_3N3jJBFdV4bT3T5F0nJKRuF1 looks like it did

[cyan anvil]

This is only an issue on mobile?

Like mobile web?

Or both?

[misty vortex]

happened on both

[cyan anvil]

Gotcha

[misty vortex]

just seemed to always happened on mobile web

and sometimes on desktop web

like mobile browser

[cyan anvil]

I need to step away but my colleague is going to jump in to help investigate further. Okay for me to share your test site / credentials with them?

[misty vortex]

yes

[cyan anvil]

👍

[lapis hornet]

Hi there 👋 taking over.

Give me a few minutes to get caught up.

[misty vortex]

ok

After a little more debugging on my part. The error

{
  message: "Something went wrong. Unable to show Apple Pay. Please choose a different payment method and try again."
  type: "invalid_request_error"
}

shows when the user has not cards saved to their apple wallet

at least on web

[lapis hornet]

That seems entirely expected. Is this the edge-case you're talking about? Also, we haven't been able to reproduce on our end. Is there a specific workflow or configuration that you can dependably get the behavior to happen with?

[misty vortex]

It seems to just "happen" , were you able to purchase via apple pay?

[lapis hornet]

Bismarck was able to get through the purchase flow, but obviously you can only have Apple Pay setup with a live card, so I'm not sure if they created a payment or not.

At this point I would recommend writing into support so we can have an email thread and papertrail of what has been tried. Picking up and leaving off in all these chat-threads makes debugging really difficult and this is going to take more time than we can give in realtime: https://support.stripe.com/contact

Once you write into support, DM me your email and I'll make sure my team picks up the thread and works on it with you over email.

[misty vortex]

their's worked

pi_3N3jJBFdV4bT3T5F0nJKRuF1

that current build on that env is no longer valid with the changes regarding apple either

[lapis hornet]

I don't know what that means. What "changes regarding apple" are you talking about? What env is no longer valid?

What does valid mean?

[misty vortex]

this pi_3N3jJBFdV4bT3T5F0nJKRuF1 was created by @cyan anvil working with apple pay.

The environment that I asked them to test against is no longer active.

I can submit a support ticket if that is your recommended next action

[lapis hornet]

yeah, a support thread would be the next best move. You will need to have 2 things ready to go though:

(1) A detailed step-by-step explanation of how to get the Apple Pay behavior 100% of the time
(2) A test environment (like the one you gave Bismarck) that we can use to follow your step-by-step explanation and see the behavior ourselves