#alex-several-questions
1 messages · Page 1 of 1 (latest)
Hey @full lagoon! We're happy to help. Let's just keep all questions to this thread it's fine if you change topics 🙂
We don't have a limit to the number of domains so you're all fine to add them all
ok thanks
the other question is regarding the bluetooth terminal integration with android/ios sdk
I've observed that the very first update to the bluetooth terminal takes a lot of time
(wisepad 3 model)
in the phone I've been testing this on, the connection was always cut unless I kept the device awake myself
can you say a bit more about what you see/experience?
is it recommended to keep the device awake while the terminal updates?
or during the whole terminal operation let's say
what I experience is the connection with the terminal being cut every time I was waiting for the very first bluetooth update, which really took a lot of time. It seems like, as soon as my phone screen went off, the terminal got disconnected
gotcha, yeah I think that's expected but let me ask my team if there's a way to avoid that easily
so, is it recommended that I use one of the techniques in here https://developer.android.com/training/scheduling/wakelock to keep my app awake during terminal operation?
yes it's likely the right approach. I'm asking my team so I'll let you know in a bit once they reply if they have a recommendation
Do you have other questions in the meantime?
yes thanks, I have more questions also related to the bluetooth terminal updates
what is the frequency of updates we can expect?
(both mandatory/optional)
We don't really have a set frequency, it really depends on what we need to change/fix.
we are trying to minimize the likelihood that this will impact our customers in the middle of a payment with a final client let's say
but could you more o less give me a figure of what this has been like lately?
https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#stripe-reader-software
This ensures that updates happen at midnight (in the timezone of the assigned location) to avoid interruption to sales
We do this to avoid disruption. But with BT readers if you don't keep them connected then you only know on the next reboot
the thing is that with bt readers, they update upon connecting afaik
so we would have to program discovery and connection every once and then, and that is only assuming that the reader is within range etc
ah yes you're right I was deep on the wrong doc. Let me see if we have a more specific changelog that could show the recent frequency
also about bt updates, I see you have optional as well as mandatory updates, does every mandatory update start off like a optional update?
https://stripe.com/docs/terminal/readers/bbpos-chipper2xbt#firmware-versions you can see some of the update frequency on that page
we split firmware and reader update too
and then, if not accepted, it becomes mandatory
And no it's not always optional. It's more for security fixes and related so they get released and become required
ok makes sense
So if you use the M2 you can see we haven't made many updates https://stripe.com/docs/terminal/readers/stripe-m2
I see we can expect one every 1/2 months, not that bad
yeah though it's always possible you'd get 2 updates the same week, but we aim to avoid that if we can
ok, thank you very much, nothing more on my side, just waiting now for your answer on keeping the app awake
sounds good
well, now that I'm here, my colleague from product has been waiting to be given documentation about EU SEPA transfers, which we just joined the beta, but all we have so far is https://stripe.com/docs/payments/bank-transfers/accept-a-payment which seems very specifically about Japan
don't you have something specific to SEPA transfers?
we don't really discuss betas in public since they are secret/private. But the API is quite similar to the Japan one. Not sure if we have specific docs for the EU version but they should ask their contact at Stripe who gave them access!
Okay so for iOS they recommended looking into this: https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/CoreBluetooth_concepts/CoreBluetoothBackgroundProcessingForIOSApps/PerformingTasksWhileYourAppIsInTheBackground.html#:~:text=Class Reference.-,Core Bluetooth Background Execution Modes,-If your app
https://stackoverflow.com/questions/53299770/ios-ble-device-paired-while-app-is-in-background-or-killed-or-suspend
https://punchthrough.com/android-ble-guide/ is another guide they recommended
@full lagoon Let me know if that answers your question!