#chromacore_error

1 messages ¡ Page 1 of 1 (latest)

sage smeltBOT
#

👋 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/1344759872033394750

📝 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.

dusty hare
#

Hello, what kind of reader are you working with? Seeing what I can see from our logs

#

Do you have the ID of your account (acct_1234) or of this terminal (tmr_1234) I am not seeing that serial number registered

modern dove
#

Having my front desk send me this info as I am working from home today and didn't realize my inquiry would be closed almost immediately after trying to get the answers yesterday. I realize you guys track progress that way but having to start from the top every time is super frustrating. I'll be back as soon as I have the info.

dusty hare
#

Gotcha, feel you on the frustration but unfortunately that policy is needed to keep this server functional. This server is for real time conversation and we get so many questions here that it would quickly become unmanageable if we didn't close them after ~15 mins of inactivity. Tickets do persist, so if you want to keep something with persistent state over a longer period of time you can open a case on our support site:
https://support.stripe.com/?contact=true

modern dove
modern dove
# dusty hare Gotcha, feel you on the frustration but unfortunately that policy is needed to ...

I appreciate that info... this is the only place I could find any help at all on the entire stripe website. Otherwise it told me I needed to pay so the whole experience of trying to get help for this has been a weeks long endeavor while trying to focus on every day stuff at work that I need to get done. I know these policies and this set up is not your decision and appreciate that info. If you think that's the best way to move forward, I can go that route but this is the info I was able to get from the desk. Not sure where the info is you're asking for as it doesn't seem to live in the terminal.

dusty hare
#

Thanks, that gives me the serial number that I was looking for, looking in to our logs again.
Re: our site, we should have a contact form on the page that I linked to that lets you open a support case with us. I am not aware of us requiring payment to create a case, though if you don't have full dashboard access (which is an account type thing not a payment thing) that form may not be there. This server is actually more for coding questions but again I'm happy to at least try to

#

Not seeing that one registered either actually. Do you know if even the registration process is not working? Or potentially was this reader just set up on your side right before creating that thread yesterday?

#

Nevermind, now I am seeing something. Now I can look at those logs

#

I think I'm seeing a pretty consistent connection on our side, with disconnects only happening on restarts largely. Can you tell me more about the behavior that you are seeing with the disconnects? Like what exactly says it is disconnected, is there an error message shown, and is it showing at a specific part of the payment process?

dusty hare
#

@modern dove Just checking if you are still around. Our logs show a consistent connection from the reader to Stripe, so the disconnects are likely not coming from that connection. To debug further it would be helpful to know more about how these issues present themselves