#savlundi
1 messages ยท Page 1 of 1 (latest)
Hello! How are you registering the reader? I assume you're using the JS library we provide?
that is correct, yes
gotcha - let me see what I can find on my end
sorry, i just realized that i LIED and we did not use the JS library
we connect the terminals via the stripe API to our app
this could be helpful it gives the console information
๐ let me take a look
If you generate a new registration code for the reader do you still see the same issue?
I'm guessing this registration code was created > 2 hours ago and has since been expired which is why it's failing
If you go to your reader settings I think you should be able to tap "Generate pairing code" to get a new one
i just regenerated and attempted again and this is what i got
i get either this message or the other message everytime i try to connect it
i have a secondary way to connect and this is what happens
It looks like what's happening is that there is a successful registration happening at first (you can see it in this request req_OFDN9ByAk1sLhx) but then somethign on your end is immediately going and deleting the reader that you just registered (req_NrOD4xcW6UwhPp). I assume htis then invalidates that registration code for future usage
Do you know what code on your end is triggering the "Serial number does not match the reader" error?
the light-buyer-dazzle one just did that when i sent this to you
That's an error on your end, not ours so it must be something on your code that's not behaving as expected
could this also be an issue with it being a staging enviroment vs production?
It's possible - where in your code are you triggering the "Serial number does not match the reader" error? If you have code on your end that's checking that serial exists in a database or somethign that could maybe explain the error
thats a really good question that i dont currently know the answer to. I am the product manager and our dev team is in CZ so i am not able to figure that out at this exact moment
Yeah I think that's the key here - you'll want to check with your dev team on why/how that error is triggered because I think something is failing there and it's causing you to delete the reader (despiate registration succeeding)
ok cool, thanks for helping me try to figure this out. I will get with them and see what we can figure out.
๐