#viliamkopecky
1 messages ยท Page 1 of 1 (latest)
๐ Thanks for reaching out
Could you please share more details about your integration? what guide are you following ?
Using @stripe/terminal-js which uses that non-open-sourced https://js.stripe.com/terminal/v1
Are you using a simulated reader or physical one? if you are using a physical one, which one ?
physical bbpos_wisepos_e
if you'd like to see typescript+react code. But it depends on server-side code... usage then is like
<TerminalBugReport
locationId={TERMINAL_LOCATION_ID}
loadPaymentIntentClientSecret={loadPaymentIntentClientSecret}
loadTerminalToken={loadTerminalToken}
/>
Between, for BBPOS WisePOS E readers, we recommend using the server-driven integration:
https://stripe.com/docs/terminal/payments/setup-integration#:~:text=For BBPOS WisePOS E readers%2C we recommend the server-driven integration%2C which uses the Stripe API instead of a Terminal SDK to collect payments.
You are trying to connect to the reader via internet or bluetooth?
via internet
I would like to use the server-driven integration, but it is generally available only in the US, we are located in the Czech Republic... I sent an email as instructed to stripe-terminal-betas@stripe.com 2 days ago, but noone reached out yet, so we are trying to use the JS api
Ok are you following this guide then ?
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=js&reader-type=internet
yes... all of that works... but I would like to have an updated dashboard of available readers, so user could switch between them... but the discover functionality is not working while a reader is connected
it is not a serious issue - user can disconnect before switching a reader... just it would be nice if it could work even with currently connected reader.
๐ taking over for my colleague. Let me know if there's any follow-up Qs I can answer!
Hi... in the end this is problably just a bug report. But i could ask: Is the server-driven integration ready even for non-US regions? How long should I wait for the reply with request to access the server-driven integration for our account? (It has been 2 days and Stripe usually responds very fast ๐ )
I'm sorry about that delay, but you should hear from us asap, I don't have a real time frame on this but it shouldn't be long
The question is - do you recommend we stop the current work using js api and just wait for the server-driven api? Is it stable for real usage outside of US region?
I'm not really familiar with your integration and hasn't been able to catch up yet on the thread I'm terribly sorry about that, but discord suddenly got really busy
I would suggest, writing back to support (if you already have a ticket, you could reply to the email you received), someone would pick up the ticket and will get back to you