The device code is created correctly, but the Terminal refuses to accept it.
What I did:
Created the code with CreateDeviceCode in PRODUCTION (not Sandbox), using my production access token and my production location ID.
The request used product_type TERMINAL_API and the name “Tapviva Counter”.
Listing codes right afterward in production showed the code as valid: status UNPAIRED, no device_id yet. Example code: WZVQMF.
The Terminal was signed out. On the sign-in screen I tapped “Use a device code”, and on the “Sign in with a device code” screen I typed the 6 letters in capital letters, with no spaces, within about 2 minutes of creating the code.
Result: “Incorrect device code.” This has happened with every new code, including after I turned caps lock on to be sure.
Terminal details:
Software version: 567.0105 (up to date).
On Wi-Fi and online.
Set up with its own account for this test, then signed out.
What I am asking:
Is this Terminal somehow locked to the account it was first set up with, or to a mode that blocks Terminal API pairing?
Is there a step I am missing so that the “Sign in with a device code” screen accepts a code made by the Devices API?
If a factory reset of the Terminal is needed, what are the official steps?
I cant find any reasonable answer about why this isn’t working. Could you send me your app id and a timestamp for when you tried and I’ll see if any of our logs provide any more information.
Code: GKKCPW, product_type TERMINAL_API, status returned UNPAIRED
I typed the code into the Terminal’s “Sign in with a device code” screen within about 2 minutes of creating it (between 7:12 and 7:14 PM Central, 00:12 to 00:14 UTC). The Terminal showed “Incorrect device code”.
Terminal details:
Serial: 623CS149C4004228
Software version: 567.0105 (updated to the current version using the check-for-updates button)
I already did a factory reset on the Terminal and tried several fresh codes, entered in uppercase as returned by the API. Every code has been refused.
The Dashboard-generated 12-character device code signs the Terminal in as a normal Terminal, but ListDevices returns 0 devices for the Terminal API.
My Square support case for this is #122309608.
Please let me know if you need anything else from my side. Thank you.
Yes, the Terminal ending in 4288 is the right one. It is signed in to my Tapviva account. The 6-character device codes I create through the Terminal API are rejected by the Terminal’s “Use a device code” screen, and no pairing prompt appears on the Terminal. How do I pair it as a Terminal API device so I can send checkouts to it?
Hi, I followed your steps and wanted to report back.
I signed out of the Terminal ending 4288 (Settings > Account, then Sign out).
I created a fresh device code at the Tapviva location (Point of Sale, Standard mode).
I entered the new code on the terminal keypad.
Result: the pairing worked this time. The Dashboard shows the new device code as Paired to Square Terminal 4288, login time Oct 8, 2026, 11:18 AM CDT, and the terminal went to the normal amount keypad with no error message on screen. Device ID: 623CS149C4004288
I did not send a diagnostic report, because there was no failure this time. Do you want me to run a test payment from my app against this pairing, or is there anything else you’d like me to check?
Hi, a quick follow-up. Everything is working now. The pairing issue turned out to be on my side: my app was still pointed at Square’s sandbox instead of production. After switching it to production and pairing the terminal with a Terminal API device code, a real test sale went through on Square Terminal 4288, and a refund went through as well. Thanks for the help and the troubleshooting steps.
Correction to my last message: the payment problem in my app was my sandbox setup, which is fixed. I can’t say what caused the original pairing problem on terminal 4288, since it paired fine after I signed out and used a fresh device code. Sorry for the mix-up.