#abrahamcepedao_unexpected
fringe crestBOT
đ 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/1317217080776462377
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
red nexus
Hello
I've not heard of this sort of issue before. There's should really be NO correlation between a login on your own application to triggering link authentication.
Is your firebase logic somewhat tied to any of the Stripe code/logic in your application?
sonic thorn
I reviewed it and its not tied to any stripe related code. Our theory is that in some component we initialize Stripe and this triggers a resend of the verification code for some reason
red nexus
Yeah you'd want to look into exactly what happens when a customer is logging in. Are you using some a link authentication element or something?
sonic thorn
I don't think so, we are using the normal firebase auth functions to authenticate users with email and password.
Could it be that for some reason the client did not finish the phone verifcation process when they tried to setup stripe with Link?
red nexus
Not sure to be honest. I fail to grasp how link verification is triggered by a login to your own integration.
I'd recommend trying to record a video demo of the behavior you're seeing with a test account and sharing the video along with a test account to our Support team via
https://support.stripe.com/?contact=true
That way we can try to reproduce the behavior you're seeing and try to investigate
fringe crestBOT