#Alex EFL
1 messages · Page 1 of 1 (latest)
Hey there
So it sounds like the "Payments" app is controlling your integration with the Reader here, correct?
There are many things that can cause a Reader to get disconnected and potentially not reconnect.
So it is really hard to say. This first step would be to look at the logs in the integration for what is going on.
But it sounds like that integration is controlled via "Payments"?
Yes, Payment for Stripe
Okay so then the best course of action here will be to reach out to that third party and ask them what they see on their end.
If they aren't sure, they will need to contact us and provide us the details of the integration, their logs, and the Reader Serial Numbers so we can take a look as well.
We are the same party, this is used to collect physical orders from a bar that we have in the company. It has always worked correctly and the button to connect with bluetooth reader tried to perform the action of connecting, now you press and does nothing.
What add info do you need?
Oh okay, thought you meant you were working with a third party
Then I need the above... what SDK are you using? What do your logs indicate from that time period? Any error messages? What are the Serial Numbers of the Readers?
Okay, you can open a private conversation for this private data?
No this is a public server. The Serial Number isn't really sensitive though. But if you prefer a private conversation then you need to email our Support team (https://support.stripe.com/contact/login) with this information and we will work with you over email.
I can provide you with this information, but let me doubt that the error does not come precisely from the physical terminals. The error is in the application, it is the application that does not try to establish any connection with the terminals. Moreover, this error was generated after an update of the app.
Okay those are all good details. If you can give me the specifics that would be great. What version did you just update to?
I don't have the terminal right now, but it asked me to update, so it would be the last one. I understand that more than one will have happened if it is an app software issue.
Okay, there is really not much I can look into from my end without the Serial Number for the Reader. This could be an issue due to the update or there could be a variety of other things going on. With the current info I can't say for sure
Considering that the error came from the last update, is there any way to revert this one or just wait for the new one?
I don't think there is a way to revert but let me check
Are you not aware of any other incidents on the same subject?