#mojuba_best-practices

1 messages ยท Page 1 of 1 (latest)

terse lynxBOT
#

๐Ÿ‘‹ 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/1215691333868457994

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

fierce daggerBOT
orchid comet
#

Hi ๐Ÿ‘‹ which BBPOS reader are you referring to using?

keen lichen
#

BBPOS WisePad 3

orchid comet
#

Thank you for that clarification! For that, it depends on the type of update that is available. If it's a required update, that update will automatically be initiated when your app connects to your reader.

If the available update is optional, then you can defer it for a certain period of time. However, the update will eventually become required and be performed automatically.

Discussed more here:
https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=ios&reader-type=bluetooth#update-reader

#

If you want to minimize how frequently the forced updates occur, I'd recommend checking for optional updates and providing your users with a flow to trigger those when it won't be disruptive to them.

keen lichen
#

Thanks! I'm aware of optional vs. required updates. The problem in our case is that the terminal is supposed to be a self-service one, i.e. it would be the paying end users and not the merchants who will be facing this situation. This means, once they see there's a slow process they didn't ask for, they will likely just won't pay and leave. Ideally, we would like to avoid this

orchid comet
#

You should speak with our Support team about your use case to ensure it isn't violating our terms and policies. It's my understanding that you aren't permitted to allow customers to solely operate readers, and that you're expected to have someone running those readers, but admittedly that isn't my area of expertise. I'd strongly recommend confirming that with our Support team:
https://support.stripe.com/?contact=true