#anthony_api
oak cometBOT
đ 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/1272632868597792778
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
plush gyro
Hello, is there a specific token creation error that you are looking to replicate? Typing in an invalid credit card number would trigger an error on the client, but that feels like it may not be the kind of error you are looking for
swift gyro
we have a flaky payment flow where the form is not being shown as valid, and we suspect one possible explanation is that the user is typing in a valid card, but the stripe cc element maybe isn't reading it as such. in other words, is there a way for the token creation to fail, but for it to not display to the user in the client that it failed?
plush gyro
Not that I'm immediately aware of. When you call create token with the card element, we should do a Luhn check to see that the card could be valid and if so pass the data back to Stripe to be tokenized. That kind of bug where the token creation succeeds but the client reports and error is possible, but I've never seen that kind of bug happen with Stripe.js outside of a connection timeout. We don't have any times where we would intentionally have a discrepancy like that.
Do you have any further details like error messages on what exactly is happening when this breaks?
swift gyro
this is helpful, and i think we can probably rule out this scenario. thank you