Sessions

Every checkout session that ever started — successful, failed, expired — is in the Sessions table. Use it to investigate specific orders, debug payment issues, and confirm tracking is firing.

The table

Columns:

Column	What
Status	Coloured badge: complete (green), pending (amber), payment (blue), expired (grey), failed (red), refunded (purple)
Customer	Email; click to see all sessions for that email
Country	Flag emoji based on billing country
Amount	Order total in the cart currency
Payment method	Card / PayPal / Klyme / NomuPay / etc
Radar score	Stripe Radar risk score, colour-coded (see Fraud)
Started	Time the session was created
TTFB	Time-to-first-byte for the checkout page (Swft tracks this for perf)
Actions	Copy session ID, view detail, view in WooCommerce

Filtering

• Status — filter to one state.
• Search — by customer email, session ID, or order reference.
• Date range — last 24h / 7d / 30d / 90d / custom.
• Country — pick a single country.
• Payment method — pick a single gateway.
• Radar level — normal / elevated / highest.

Filters are AND-combined.

Session detail

Click any row to open the full session detail:

• Customer — email, name, phone, addresses.
• Cart — every line item with quantity and price; subtotal, tax, shipping, discount, total.
• Payment — gateway, payment intent ID, amount, status, any captured / refunded splits.
• Fraud — Stripe Radar score, level, rule (if any).
• Custom fields — values for any merchant-defined custom fields.
• Extensions — flags from active modules (gift card applied, donation included, KYC verified, etc).
• Timeline — events in order: created, details submitted, payment started, payment succeeded, WC order created.
• Raw payload — JSON dump of the full session record, for debugging.

The View in WooCommerce button deep-links to the resulting WC order (if it was created — failed and expired sessions don’t have one).

Debugging specific orders

Customer says they paid but you see no order:

1. Find their session.
2. Check the status. If payment and not complete, the payment failed at the last step.
3. Check the timeline for the failure reason.
4. Check Radar score — was it blocked for fraud?

Customer says they were charged twice:

1. Search their email.
2. Look for two complete sessions or two payment sessions with similar timestamps.
3. If duplicate, refund one via Stripe / PayPal / WC and apologise.

Order amount looks wrong:

1. Open the session detail.
2. Cross-check cart subtotal, shipping, tax, discount.
3. The most common cause: a coupon code applied that you weren’t expecting, or a gift card applied silently.

Gotchas

• Sessions live forever. We don’t auto-purge. The table can get large after months of trading; use filters.
• Failed payment intents aren’t the same as failed sessions. A shopper can attempt payment 3 times on one session before giving up — the session is still one row but the payment intent history is in the detail view.
• Expired sessions are sessions that were created but never completed within the timeout (30 minutes by default). They’re not failures — most expired sessions are just shoppers who got distracted.
• Customer email isn’t unique. A repeat customer has many sessions. Filter by email to find them all.