Konsole

Konsole is the debugging space built into the Dashboard. Where the API gives you answers, Konsole gives you context: which request was sent, which response came back, which provider was chosen and why.

Why Konsole

• Diagnose in minutes: every call is logged with its headers, body, response, and latency.
• Reproduce a bug: resend a webhook delivery exactly as it was originally sent.
• Understand orchestration: inspect the ordered candidate list and score breakdown behind any payment's provider selection.

The four sections

Getting Started with Konsole

Open Konsole from the Dashboard by clicking Konsole in the sidebar. Your first view is Overview: request-volume and error-rate KPIs, anomaly cards, a health digest, and trend charts for the selected range (24h / 7d / 30d).

From there:

1. API Logs — search your request history to find a specific call or error, then open any row for its full headers, body, and response.
2. Webhooks — inspect delivered / failed / pending deliveries, manage endpoints, resend a delivery, or send a one-off connectivity test.
3. Routing Log — for a given payment, see every candidate provider that was considered, its priority tier and tie-break score, and whether it was skipped by the circuit breaker.

Use the sandbox / live toggle in the Dashboard to switch environments — data is never mixed.

Common Debugging Workflows

Diagnose a failed payment

1. Open API Logs and filter by status (error, 5xx, 4xx) and/or search by request ID, IP, or error message.
2. Open the row to read the exact request body sent and the response/error returned.
3. Open the same payment's entry in Routing Log to see which provider(s) were attempted, in what order, and — if one was skipped — why (circuit breaker open, currency/channel mismatch, country block).

Resend a webhook

1. In Webhooks → Deliveries, find the failed delivery.
2. Click Retry (or select several and Retry bulk) to resend the exact original stored payload with a freshly-computed signature. There is no payload editor — you cannot alter the body or headers before resending.
3. To sanity-check connectivity to a newly-created endpoint, use its Test action, which sends one fixed webhook.test payload — not a real event, and not customizable.

Inspect provider routing

1. Open Routing Log and search by transaction reference.
2. Each row is a routing decision for one payment: the ordered candidate list, each candidate's priority tier and score breakdown (rule match, least-cost boost, telemetry boost), any circuit-skipped providers, and whether the country was blocked outright.
3. This is a historical record computed at the time the payment was routed and refreshed on page load — not a live stream.