#newtreyes
1 messages · Page 1 of 1 (latest)
Hello! Let me take a look at that Payment Intent...
Thank you, Sir
The only thing I can see on our end is the Payment Intent being created. Doesn't look like any other operations were performed on it, so it seems the failure is localized to the device.
The error message indicates the tap to pay process was canceled.
Yeah
Can you adjust your code to log details for the entire error object, not just the localizedDescription?
Mmmmm
It looks as if there is very little extra information
is there a recommended way of generating a string from the error object?
One containing all the information from the error?
I was just looking through the SDK code... this is an SCPErrorCanceled and when that happens there's not much detail, yeah. It just indicates the operation was canceled.
This is an issue you can reproduce on demand?
I don't think so because it looks as if it only happens the very first time you try to Tap to Pay using a specific Apple Id
There are no other details logged? No other errors thrown? What happens on the device display when this happens?
What about what happens on the display?
It seems like something is canceling it... I wonder if there's some kind of system dialog or prompt that's canceling the flow, maybe something to do with the Apple ID being new. Any way you can get a video of what happens on the device when this issue occurs?
I will try
but it's hard because it only happens on the initial Tap to Pay initialization process
right after that, the payment just works
Is there any way to remove the Tap to Pay Authorization for a specific Apple Id?
something that could help me force the authorization process to happen again?
Not that I know of, but I'm not intimately familiar with that side of things.
That would be a good question to email support about: https://support.stripe.com/contact/email
You may want to do that regardless to get a longer running support interaction going, it's doubtful we'll be able to solve this in realtime here unfortunately.