#eliasao_terminal-disconnect-callback

1 messages · Page 1 of 1 (latest)

elfin cragBOT
#

👋 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/1273703191330033715

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

full orbit
#

Hi 👋

  1. We strongly recommend against the JS integration
  2. Unexpected reader disconnects happen all the time due to network connection issues. They can occur for < 1s wifi connection drops. Most devices that use WiFi have au automatic reconnection behavior built into them and that is what we are recommending too.
balmy ivy
#

Thanks for the quick answer. What is the alternative for web? The server side integration? What are the advantages over the JS integration?

full orbit
#

The server side integration is the recommended approach.

  • The JS integration requires the reader and the POS device (computer, tablet, etc.) be on the same local network and be able to resolve using local DNS records. This is very hard to troubleshoot, especially if you don't control the local network and WiFi router
  • The server driven integration only requires that both the POS and Reader have access to the Internet. Because communication goes through the Stripe API, it's much easier to debug on our end too.
balmy ivy
#

Thank you for the details. So can I say that onUnexpectedReaderDisconnect is called only for errors related with the network, is that a true statement?

full orbit
#

Yes, it's a callback to handle reader disconnections that occur due to network outages. As opposed to expected disconnects like when you power down the reader

balmy ivy
#

Thank you

full orbit
#

FWIW the same callback exists on all our Terminal integrations

elfin cragBOT