#b33fb0n3_unexpected
spark helmBOT
👋 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/1408482309358882947
📝 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.
- b33fb0n3_api, 1 hour ago, 39 messages
- b33fb0n3_best-practices, 1 day ago, 30 messages
gleaming bone
👋 Hi, we having some high volume at a moment, trying to get caught up. I'll be with you asap, appreciate your patience 🙂
gaunt sage
Alright, waiting for your patiently
gleaming bone
Double checking but I'm fairly certain a terminal can only be setup for one at a time not both.
gaunt sage
Oh fr? My team might be a little bigger, so while my client is using the terminal (production) we as the dev team want to test new integrations. The solution can’t be to have 2 terminals, right?
The dev team might be able to use „simulated“ terminals, but how to test the stuff when using a physical card?
gleaming bone
After checking with the team a second reader would be required for that.
gaunt sage
Oh ok. Thanks 🙂