#Alex Rodriguez

1 messages · Page 1 of 1 (latest)

regal crowBOT
minor prism
#

Hi 👋

Unfortunately that is not an API that we have or are planning on building. I would recommend signing up for the notification emails we show here to keep informed about which countries Stripe operates and with what capabilities:
https://stripe.com/global

fervent moss
#

ok thanks so no plans at all for that

minor prism
#

Not that I am aware of

fervent moss
#

ok thanks I have another question, should I open new thread?

minor prism
#

No, please ask your next question here

fervent moss
#

ok so this is about WisePad 3 updates

#

some of our customers are really frustrated with the updates happening when the terminal is connecting

#

which happens right before a payment

#

in some cases our customers end up not making the payment, and just using other terminal solution they might have too

#

we would like to implement some kind of notification to at least warn them that they need to connect the terminal, so that the update goes trough

#

at a more convenient time, not at the exact moment they are with a guest and want to accept a payment

minor prism
#

Wise POS E readers need to update & reboot every 24 hours

fervent moss
#

do you have some sort of API or a way for us to get notified of any upcoming or recent updates?

#

WisePad 3, not WisePOS E

#

I'm talking about the bluetooth reader

minor prism
#

Oh sorry, this is true for all readers

fervent moss
#

We also integrate WIFI readers, and it updates by itself, no problem there

minor prism
#

But unfortunately we do not have an API that indicates the update status of a reader prior to connecting to a POS

fervent moss
#

But for the WisePad 3, it needs to connect in order to update, as it does this by Bluetooth

#

I would like to fetch the history of updates for a specific reader model and country, or for us to have notifications

#

otherwise we can't really warn them in advance of their work day that they should update their device before accepting payments

minor prism
#

I do not think so, and as I said this needs to occur every 24 hours.

fervent moss
#

what I read is that
If there are immediately required updates for the reader, they will be installed when connecting to it. The connection process will not complete until the required update has been installed.

#

so what is the recommended approach for this? do we have to tell our customers to connect their terminal at least once a day, even if they don't need to make payments?

#

The thing we want to avoid is for this to happen before they need to make a payment

#

how do we achieve that? if a mandatory update can potentially happen before any connection, and we don't have any way to predict or at least notify that an update is happening soon/today, what is the recommended approach to work around that?

minor prism
#

Then I would recommend they connect to their BT terminal device before they start collecting payments each day

fervent moss
#

ok thanks, final question, we'd like to deal with both Android and iOS Terminal SDK errors in an uniform way, as we are sending those errors home to log them and alert if necessary

#

for the error code, in Android we have strings (enum), for iOS we have an error code as an integer

#

is there a way we can deal with those in an uniform way on our server?

#

without having to map them?

minor prism
#

That is something that would be entirely up to your integration. Unfortunately Apple and Google like to differ in how they implement their software frameworks.