Finding your Square sandbox transactions

Updated Oct 14, 2026 Payments

You finished a Square sandbox test in TitanCart, the order reads Processing, and yet the Square sandbox seller dashboard shows nothing. This is the most common Square setup papercut, and it almost always means you are looking at the wrong sandbox dashboard, not that the payment failed.

Why a sandbox dashboard looks empty

Each Square developer app can have several sandbox test accounts, and each test account is a separate seller with its own Location ID, its own access token and its own transactions list. They share nothing. A payment made against test account A never appears in test account B’s dashboard, even though both belong to the same app.

The Open seller dashboard button you reach for first usually opens the first test account in the list, which is rarely the one whose Location ID you pasted into TitanCart. The dashboard you opened really is empty; your payment landed safely in another one.

First, confirm the payment worked

The order status. In Sales → Orders the test order reads Processing with the Square gateway’s name as its payment method. TitanCart only moves an order there after Square confirms the charge, so Processing means the money moved in the sandbox. (A declined test card leaves no order at all.) TitanCart does not show Square’s payment ID on the order; the order number is what you search by on Square’s side.
Test Connection. Open the Square gateway in Settings → Payment Gateways and click Test Connection. It lists how many locations the saved access token can see and, if the saved Location ID is not one of them, adds “Warning: The configured Location ID was not found in your Square account.” That warning is this article’s mistake caught in one click: the token belongs to one test account and the Location ID to another.

Finding the dashboard that has your transaction

1. Open the sandbox test accounts list

Go to developer.squareup.com/apps and choose Sandbox test accounts in the left sidebar. Every test account ever created for your developer account is listed, each with its name, its Location ID (looks like L1A2B3C4D5E6F), its access token behind a Show toggle, and an Open seller dashboard button.

2. Match the Location ID to TitanCart

In another tab open the Square gateway’s Configure tab in TitanCart and copy its Location ID. Back on the test accounts list, find the row with that Location ID and click its Open seller dashboard. The dashboard that opens lives at squareupsandbox.com (note the sandbox), never at squareup.com.

3. Find the transaction

In that dashboard open Transactions, filter by today if the list is long, and look for the amount. Every TitanCart payment carries the note “Order TC-…” with your order number, so the order number is the quickest match.

The rule: same row, every time

The access token and the Location ID saved in TitanCart must come from the same row of the sandbox test accounts list. Mixing the token from one test account with the Location ID of another does not produce a configuration error at save time: Square accepts the call and books the payment to whichever test account owns the Location ID, so your dashboard stays empty while another account fills up. Test Connection’s Location ID warning is how you catch it. If you ever regenerate the access token, take the new one from the same row whose Location ID is configured.

Going to production

None of the sandbox dashboards has any relationship to your live Square account. When you take the gateway live (Square setup §5), you swap in the production Application ID, access token and Location ID, untick Sandbox / Test Mode, and real payments show in the normal Square Dashboard → Transactions, never in any developer-portal dashboard.