Skip to content

Wajub BuildersBecome one of the 50 founding members. Apply 

Konsole

See everything your integration does.

A stuck payment nobody can explain costs a day of development. Konsole brings together every API call, every event, every webhook delivery and every routing decision, so you go from symptom to cause in a few clicks.

Create a free accountRead the docs 

Routing log

Which connection took this payment, and why?

For every production payment, Konsole keeps Wajub's decision: the connections set aside, the ranking of the ones left, then each attempt up to the result.

  • Connections set aside

    A connection that fails repeatedly is set aside, then takes its place back as soon as it works again. The log names it, so you know why it was not tried.

  • How the candidates rank

    Every eligible connection, with its rank. A badge shows what weighed in: one of your rules or the connection's recent health.

  • Every attempt

    The connection tried, the time and the result. If it fails during a mobile money payment, the next attempt goes to the next connection.

Routing decision

How the orchestrator selected a provider for this payment.

  1. trx_7Kq2mWv9XcR4tLp8BnZd

    Orange Money, FCFA 15,000

    Channel
    Orange Money
    Selected
    Campay

  2. MavianceSet aside after failures

  3. 1

    Campay

    Rule

    #1Oct 6, 14:32:07Unreachable

  4. 2

    Notch Pay

    Recent health

    #2Oct 6, 14:32:09

  5. 3

    pawaPay

Filter the payments that failed over, the ones that set a connection aside, or the ones with no eligible connection.

Production only: in sandbox, a simulated provider answers every payment, with no routing across connections.

The routing log(opens in a new tab)

Webhooks

What your endpoint received, and its answer.

Konsole follows every event on your account all the way to your server: the delivery, the code returned, the duration. A missed delivery can be resent in one click.

  • Events

    The stream of your account's events, each with its deliveries.

    payment.succeededpayment.processingpayment.failed

  • Deliveries

    The status, the code your endpoint returned, the duration and the attempt number. Resend one delivery, or retry up to 100 failed deliveries at once. Automatic retries run for 72 hours.

  • Endpoints

    The events to receive, a test send, the success rate and the average response time. The signing secret is shown once you enter your password.

  • Locally

    The CLI forwards signed events to your machine, and the session shows up in Konsole.

    wajub listen

API logs

What did you send, and what came back?

Every call to the Wajub API, with the full request and response. When a call fails, the error message shows at the top of the details.

  • Method, path, status and duration: green under 200 ms, amber under 500 ms, red above.
  • The body and headers of the request and the response.
  • The request ID, the idempotency key, the API version and the API key used.
  • Filters by period, status, method and response time, and export to CSV or JSON.
The log explorer(opens in a new tab)

Diagnosis

From symptom to cause, without guessing.

Each common problem has its own view. No more digging through your own logs or opening a ticket to understand what happened.

The Overview(opens in a new tab)

  • Is something wrong right now?

    Alerts computed from your traffic, and the state of each endpoint: healthy, struggling below 80% success, or disabled. For a first call, snippets in cURL, Node.js, PHP and Python.

    Overview

  • A call returns an error you can't make sense of

    The request sent, the response received and the error message.

    API logs

  • A payment stays pending

    Was the payment picked up, or did it fail? The events tell you.

    Eventspayment.processingpayment.failed

  • Your server received nothing

    The code your endpoint returned, or the missing delivery.

    Webhooks

  • A payment went through the wrong connection

    The candidates, their ranking, and why a connection was set aside or failed.

    Routing log

Environments and team

Sandbox and production, never mixed.

  • One environment at a time: your sandbox tests never mix with your production logs, which are kept in separate databases.
  • Two levels of access: view Konsole, or manage webhooks (resend, export, edit endpoints). The account owner has full access.
  • Webhook replays on every plan, with no monthly allowance; exports included depending on your plan.
See pricing 

Frequently asked questions

Another question? Talk to the team

Can I test webhooks locally?
Yes. wajub listen forwards your account's real events to a local URL, signed as in production, with no tunnel to set up.
Are sandbox and production mixed in Konsole?
No. Konsole shows one environment at a time: your sandbox tests never clutter your production logs.
Where is the routing log?
In Konsole, for every production payment. In sandbox, payments are resolved by a simulated provider, with no routing across connections.
Are exports and webhook replays unlimited?
Webhook replays are not counted on any plan: the same event can be resent to the same endpoint once every 5 minutes. Exports are unlimited from Growth, and the Pay as you go plan includes 10 per month. Details are on the Pricing page.

Review your first payment.

Create an account, make a call in sandbox and open Konsole: everything is already there.

Create a free accountRead the docs