#peter-l_code
wise flumeBOT
đ 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/1349032721011314771
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
high canyon
I don't think we have code that connects to multiple readers like this but I will double check. It sounds like we want you to discover and connect to them one at a time, have you been able to connect when doing that?
flat scroll
no im not sure whats the best practice is in general. in your documentation its mentioned that we should discover the readers during app initialization, so its faster after when the payment starts
but we want to use the ttpa reader first but then switch (fast) to the usb or bluetooth reader in case a PIN entry is needed
and it seems its not possible to connect 2 readers at the same time?
so im not sure whats the best practice is here?
high canyon
Looking into what guidance we have here
Hello, one thing my colleague flagged is that TTP suports PIN entry. Are you experiencing some issues or errors when PIN entry is required in your tests?
flat scroll
hm, we are using Sunmi V3 Mix devices (which are supported in general according to your ttpa supported reader list). There is no pin popup coming, we only get the return callback that a payment method is required and usually transfer then to the usb reader
or is this possible on the sunmi v3 mix? what do we have to do in case? shouldnt pop up the pin entry form without interaction from us?
high canyon
Asking my colleague and will get back with what we can find
flat scroll
ok thank you
high canyon
Ah it looks like TTP doesn't support PIN entry on Android by default. That feature is still in preview, so if you are comfortable working with preview features our support team may be able to enable this for you
https://docs.corp.stripe.com/terminal/payments/setup-reader/tap-to-pay?platform=android#fallback
Otherwise I think you would need to cache the reader objects when you see them in the discover callback and then make the connect call on each when you want to use them. We do still recommend only connecting in discovery because readers can go offline, so there may be a speed/reliability tradeoff that you are making here
flat scroll
hm i see.. so the recommended approach would be:
- disover ttpa reader
1a) cancel discovery of TTPA - discover usb reader
2a) cancel discovery of USB - conntect to ttpa reader
- in case of pin entry, connect to cached usb reader?
wise flumeBOT
high canyon
Yes, I believe that that would work