#gonsanto_unexpected

1 messages · Page 1 of 1 (latest)

dapper etherBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1333818952198914078

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

shrewd stream
#

Hello

#

Do you have an example PaymentIntent that you could share where this occurred?

indigo drum
#

hmmmm let me try to find it

#

is there any way from the Stripe Dashboard to find this? 🤔 I think this is only visible after a payment failed or something else...

shrewd stream
#

Hmm yeah would depend on your flow actually -- this error could be occurring before you create the PaymentIntent.

#

In which case I would need a specific timestamp as well as your account ID to be able to look at our logs.

#

Also, have you seen multiple reports of this? Or is this just from one customer?

indigo drum
#

well it is the first time we heard about this but it is just a merchant who is trying to integrate us and we are just luck that their Head of Testing has an iphone 11 with ios 17 😐

shrewd stream
#

Hmm yeah in that case it very well could just be something about their card or their Apple account or something else.

#

I'm not aware of any widespread issue with iOS 17

#

Has this been reproduced on multiple different devices, with different cards in the wallet, etc?

#

Mostly the error from https://api.stripe.com/v1/apple_pay_sessions indicates that we received an error from Apple specifically.

#

That request involves our direct communication with Apple -- so it may very well be something on Apple's end with this particular user.

#

Hard to say without more specifics, and I can check our logs to see if there is any further detail I can provide if you do have an account ID and a timestamp.

#

Otherwise not much I can do without more information.

indigo drum
#

ok thank you so much for the information... let me see if i can find the payment intent from our side

#

for the account id you mean our Stripe account id?

shrewd stream
#

Yes

indigo drum
#

acct_1PQ5hiD7zNrKSHTi and the error was exactly at 9am ... I have a video of the console

shrewd stream
#

9am in what timezone? I need UTC (but can convert if you tell me timezone)

indigo drum
#

here is a video where you can see the errors showing up and the time in the computer

shrewd stream
#

Ah okay I see an error indicating that the user is trying to use an Apple Pay Sandbox card

#

You can't do that in live mode

#

Must be a live card in the wallet.

#

Really you should test in test mode with a live card in the wallet.

#

And we will replace that live card with a test card in test mode.

indigo drum
#

oh shoot... thank you so much!

#

this is what happened when users are saying "nothing is working" 😒

#

thank you so much for your help

shrewd stream
#

Sure thing