#dev24444444444_unexpected
1 messages ¡ Page 1 of 1 (latest)
đ 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/1235317894800212080
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
What is the exact error message that you see?
checking
"An error occurred while processing your payment. Try again in a little bit or try a different payment method"
Do you have the PaymentIntent ID that you tested with?
I do not currently have it available. Do you know if using more than 3 unique accounts on a particular tap to pay device in a rolling window can cause an issue in collectPaymentMethod? I do see it is documented that it can cause connection issues
Hmm I'm not sure what the exact limitations are but yeah I do think this could lead to issues.
Did you see any sort of disconnect error?
On a couple accounts, we ran into the following: https://github.com/stripe/stripe-terminal-ios/issues/299
Other accounts can connect and get all the way to the collectPayment stage, but then throw the error mentioned
Ah yeah okay that does specify 3 in a 24 hour window
But that should lead to a different error really
Not a 1920
Ok, yeah that is where we are confused. The accounts that fail at connection make sense
1920 indicates a missing required parameter...
9020 is the error
Oh oh
not 1920
Gotcha my bad
Hmm would be really helpful to have the associated PaymentIntent
So I could look at that and the logs
That would be the next step here really
Generally a 9020 indicates an underlying API error