#aneeb_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1424760560230334476
đ 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.
- aneeb_code, 3 days ago, 29 messages
Hi, what does 'Can we restrict' mean here exactly?
means when a user connects one card reader from kiosk device using bluetooth pairing, can we restrict that card reader from connecting to other devices
Let me look
sure
From looking at https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=ios&reader-type=bluetooth#automatic-reconnection-on-application-start, it sounds like we do not automatically reconnect to a reader when your application starts. I also see https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=ios&reader-type=bluetooth#bluetooth-pairing
Stripe uses the numeric comparison Bluetooth pairing process for WisePad 3 card readers. The numeric comparison process requires you to verify a passkey on both your card reader and the POS device when pairing.
It sounds like as long as you have not already pared them it should not connect automatically. Are you seeing this behave differently?
i am not talking about connecting automatically, I am saying that any other application will not connect our card reader which we have paired and connected already
Terminals have a serial number that will be part of the reader object that is returned by discoverReaders, so your app can store the serial number of the terminal it connects to and make sure to only connect to that Terminal going forward
can we restrict card reader to not to connect to any other applications?
The reader can't initiate a connection, only the application can, so you'll only need to implement this on your application side. I will double check but because of that I don't think there is any way to restrict this on the reader side
are you sure about it??