#aeo_unexpected

1 messages · Page 1 of 1 (latest)

umbral tartanBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

lime cradle
#

i'll just add that, testing the terminal workflows with the simulated reader is "challenging"... i bought a physical device to test with, ignorant of the fact that I couldn't actually test with them..

sick current
#

👋
Happy to help

lime cradle
#

my guess, is that my code will work just fine in prod... but i don't like making guesses 🙂

sick current
#

Have you had the chance to test on real readers ? You can do test action on real readers

lime cradle
#

oh?

sick current
#

in Sandbox before going to prod

lime cradle
#

please tell me how

sick current
#

You use the secret and publishable key of your Sandbox Stripe account

#

and remove the simulated property when creating the terminal SDK

#

then the terminal SDK will look for real readers

#

What integration are you using ? mobile, server driven or web?

lime cradle
#

i'm testing with the server based workflow... not an sdk.. this is for a web app

sick current
#

You can test on you real devices too with the server driven integration

lime cradle
#

i can register the real device in a sanbox?

sick current
#

Yes of course

lime cradle
#

oh my... the ai on your page has led me astray

sick current
#

Sorry yeah, it's helpful but not 100% accurate, don't hesitate to reach out to us here in order to confirm

lime cradle
#

i'm a platform account, so the devices need to be created under a connected account, is that still fine?

sick current
#

Yes that's ok too

#

You can have a Sanbox platform with Sanboxes connected accounts

lime cradle
#

so, in my sandbox, i can just call create terminal or whatever the endpoint was, and pass the device id on my real physical device?

sick current
#

yes

sick current
lime cradle
#

"registrationcode" or whatever?

sick current
#

yes

#

Just follow the guide above step by step

lime cradle
#

what if its already registered in my platform account? i probably need to unregister?

sick current
#

If you are stuck in any step, don't hesitate to follow up here

sick current
lime cradle
#

well... this is great news

#

i'm assuming the status issue, that i asked about will go away with a real device? and it was just a symptom of the simulated device?

#

i'll find out i guess 🙂

sick current
#

You have two options, wait untill the reader finish the current action or cancel it

lime cradle
#

well, i queryed the status of the reader, and it told me it was "online" instead of "processing"

#

i'm basicily trying to ask it, "hey are you busy", before i cancel

sick current
#

Yeah that's a good approach

#

try do some tests with the physical readers and let me know

lime cradle
#

i want to, but its also 12:45am... so... my bed is more interested in my company, than this reader is..

#

tomorrow...

sick current
#

Make sense 😅

lime cradle
#

or, i guess, later today

#

thanks for the insights

sick current
#

Don't hesitate to come back here any way if you face any issue

sick current
sick current