Inspector

The Inspector is the "what is this thing?" tool. Hand it any XPay ID and it loads the resource, the resources around it, the events that fired against it, and the request logs that touched it, in one pane.

You'll reach for it when a payment looks weird in the dashboard, when you're tracing a webhook back to its source, or when an order ID on your side has a pi_* and you want to see where the money is.

For the drawer mechanics (open, drag, full-screen), see Workbench introduction.

Open the Inspector

Two ways:

• The dock icon in the bottom-right (a binoculars). The icon is context-aware: when the page you're on contains an inspectable ID in its URL, the icon picks it up and shows the ID truncated next to the binoculars. Clicking opens the Inspector pre-loaded with that resource.
• From any Workbench tab, click Inspector in the tab bar.

If you open the Inspector with no ID detected, you land on an empty search screen titled Peek under the hood with Inspector. Type or paste any inspectable ID into the search and the panel populates.

Auto-inspect: follow the page

By default, the Inspector follows the dashboard as you navigate. Open the Workbench once on a transaction page, click into a refund detail or a customer profile, and the Inspector updates to that new resource without you typing anything.

The behavior is controlled by a switch labeled Auto-inspect in the bottom of the Inspector sidebar. The description reads: "Inspector will automatically update based on the resource displayed in the dashboard." Toggle it off to pin the Inspector to one resource while you click around the rest of the dashboard.

The dock icon's ID detection is independent of this switch. The icon always shows the current page's ID when one is present, regardless of whether Auto-inspect is on or off.

Inspectable IDs

The Inspector recognizes every prefixed ID XPay issues. The most common ones:

Pasting an ID with a prefix the Inspector doesn't recognize returns "No object was found matching the ID provided."

The Data map

The left sidebar of the Inspector is the Data map: a tree of the inspected entity and the resources connected to it. For a Checkout Session, the tree expands to show its Payment Intent, its Charges, its Refunds, its Balance Transactions, and the Customer attached to the session, all clickable.

The label at the top reads Inspecting, with a search box that lets you swap to a different ID without leaving the Inspector. Below the tree label (Data map), the resource graph renders. Click any node to switch the inspection target to that resource. The right pane updates immediately.

The sidebar collapses to an icon strip on desktop (use the toggle in its header) and slides over as a sheet on mobile.

Sub-tabs

The right pane has three tabs across the top, all scoped to the resource you currently have selected.

The header above the tabs shows the resource type (PAYMENT INTENT, CHARGE, etc.) and the matching API path so you can confirm at a glance which resource you're looking at.

A typical use

Three patterns merchants reach for the Inspector:

1. A webhook fired and you don't know what it's about. Copy the evt_* from your handler logs, paste it into the Inspector search, expand the Data map, and see the resource the event was about and what was around it at the time.
2. A customer disputes a charge. Open the transaction in the dashboard. The dock icon picks up the pi_*. Open the Workbench and the Inspector lands on the Payment Intent. Click the Refund node in the Data map to confirm whether you've already issued one.
3. You're debugging a Payment Link that suddenly stopped working. Paste the plink_* into the Inspector. The Data map shows the Checkout Sessions created from the link, each clickable. Drill into the most recent failed session, switch to Events to see why.

Where to next