Callback Url Error Does Not Match Any Expected Callback Urls

Questions
1

Hello all,

Having a very weird issue at the moment. Building an application which accepts POS Bluetooth readers, sending a link to be opened on the device, to create a payment for the reader. The OAUTH flow is fine, opening the link on the device, upon reaching the square app we are getting the expected callback URL does not match.

In debugging we have verified the exact request getting sent and the URL matches exactly, it does use query params but per the docs this shouldnt be an issue. Tried sending the URL both non encoded and encoded as per the docs but absolutely no luck still the same error.

Confirmed using the correct app (only have on registered).

Any help appreciated, thank you.

4

Hi @moscovium - I want to make sure that I’m understanding your question properly.

Can you provide more details on the reader you are trying to connect?

Are you working in POS API? (if not, which API are you using?)

What is the expected behavior, and how is that different from the result you are getting?

6

Hi, sorry for the lack of info.
I am trying to connect to the square reader 2nd generation via my saas app. This is done through the POS api, by sending a crafted payment link. The behaviour and sending part is working fine, it fails at the last hurdle which is when the square app opens, it then displays the message, expected callback url does not match, but the URL is exactly the same.

7

I can send the request payload if required, but at his point seriously do not know what to do. I have tried sending the call-back URL not encoded, encoded as per the docs but still the same result