#mangell03_code
simple oreBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260349336995233843
đ Have more to share? Add details, code, screenshots, videos, etc. below.
livid dock
Hi there
celest vale
hello
livid dock
Give me a few minutes to determine whether this is expected
celest vale
Ok
livid dock
Could you share the Terminal reader ID or your account ID?
Account ID should begin with acct_...
livid dock
Hm, I'm looking at your list of readers: https://dashboard.stripe.com/test/terminal/readers
The simulated reader and the BBPOS WisePOS E have two different Terminal reader IDs
celest vale
That is really strange! It was not that way before. I had it registered in production mode, and it wouldn't let me add it to test at the same time. So I deleted it, went to test mode, genereated a new code on the device, registered it and it came back and showed the sim ID. But after a refresh- seems to now be unique, which is great.
So is the only thing I need to do in my code is change the sim ID to the new physical ID and try it out?
livid dock
Yep, I believe so. You can change the charge amounts if you need to test different charge results: https://docs.stripe.com/terminal/references/testing#physical-test-cards
celest vale
I saw that. I will give it a try. Thanks for your help and sorry I wasted your time.
livid dock
No worries, not a waste of time. Happy to help!