#kelurm_docs

1 messages ยท Page 1 of 1 (latest)

karmic skyBOT
#

๐Ÿ‘‹ 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/1382237154297778207

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

marble pendant
#

Hi! Looking into this!

deft pike
#

Hey, thanks Sam. I was meaning, can I pull that registration code via sdk and then call that endpoint?

#

Ideally the customer would power on their S700, our app would load on boot which they then login to.
The reader would be automatically added to their stripe account

marble pendant
#

Understood! Unfortunately, you cannot pull the registration code via SDK. The registration code must be generated directly on the reader device itself.

deft pike
#

Ah ok hmmm. Do you know what the ideal flow would be?

Customer powers on S700
They go into admin settings and write down the pairing code
Customer opens our app on the device, they then login with their user/pass + pairing code ?

Our backend would know their stripe account details and can attach the reader

marble pendant
#

Still looking into this!

deft pike
#

All good thanks ๐Ÿ™‚

marble pendant
#

Thanks for waiting! Your customer needs to power on S700 and generate the registration code. But the registration needs to be done separately, not on the device. It's only after the devices is registered then your customer will be able to update and install apps.

deft pike
#

Ohh right yes I see, it needs to be able to know where to download the app from. That makes sense, thanks.

#

Thanks for the quick responses