The dashboard

Overview is the page you land on after signing in — “your last n days, compared with the n before, and what is due to settle.”

It needs the dashboard.read permission. A role without it lands on the first page it can open instead.

Three words, defined once

Every figure on the page is built from these, so they are worth knowing exactly:

Word	Means
Landed	A collection that succeeded. It stays landed even if it is refunded later — the refund shows separately, under Money.
Failed	A collection that failed, expired or was cancelled.
In flight	A collection still pending or waiting for the customer. It counts as neither landed nor failed until it finishes.

Success rate is landed ÷ (landed + failed). Payments still in flight are left out rather than counted as failures, so a busy last hour does not drag the rate down. When nothing finished in the period, the rate is blank rather than 0%.

The period, and the comparison

Period switches between the last 7, 30 and 90 days, ending now. Every tile is compared with the same number of days immediately before: an arrow and a percentage change for amounts and counts, and a change in points for the success rate — 92% to 89% is −3 points, not −3.3%.

Dates and times across the whole portal are rendered in Africa/Accra, whatever your computer’s clock says. A settlement date read in your own zone can land a payout on the wrong day, and the mistake is invisible because the date looks perfectly plausible.

One currency at a time

Everything shows your settlement currency — the one in Settings → Business → Settlement currency. If you collect in more than one currency, the others are not here and are not added in. There is no exchange rate the ledger has committed to, so a combined figure would not be any amount of money you actually have. Use Balances for the rest.

The four tiles

Tile	What it is	Sub-line
Collected	What landed in the period, before fees — with a small line of each day.	How much of it was credited to you, after fees.
Success rate	Landed ÷ (landed + failed).	“n landed, m failed”.
Paying customers	Distinct customers who paid in the period.	How many are new — first seen in the period; the rest are returning — and the average sale (collected ÷ landed).
Available balance	What you could withdraw right now.	How much is awaiting settlement, in how many batches, and when the next payout is expected — e.g. “GH₵ 3,446.00 awaiting settlement in 2 batches · next payout 17 Oct”. It counts every batch not yet paid.

A success rate drifting down is the most useful early warning on the page. Look at Where payments come from before anything else: it usually means one network is failing.

Volume

“What landed each day. Hover a day for its figures.” A bar per day, with the best day and the daily average.

Where payments come from

“By channel and network. A network with a falling success rate is usually that network, not you.”

Your volume split by channel and by network or bank — MTN, Telecel, AirtelTigo, card, each bank — with each one’s share and its own success rate. One network well below the others, while the rest are normal, is a problem on that network; tell customers to try another way to pay, and tell us if it lasts.

Why payments fail

“Collections that failed, expired or were cancelled, by reason.” Each reason is in plain words, with its share of all failures and what to do about it:

Reason	What to do
Not enough in the wallet	The customer can top up and pay again.
Declined by the customer or bank	Often a mistyped PIN or a prompt dismissed by accident.
Prompt not approved in time	Remind customers to watch for the prompt before they leave the checkout.
Wrong number or account	Check the number and network the customer entered.
Over a wallet or account limit	The customer’s provider caps what they can send in a day.
Stopped by fraud checks	Contact us if these look like genuine customers.
Network unavailable	On our side or the network’s; we fail over where we can.
Duplicate request	The same payment was sent twice.
Account setup	Contact us: something needs configuring.
Our error	We are alerted to these.
Cancelled or other	—

Prompt not approved in time is the reason you can most influence: a checkout that tells the customer to keep their phone in hand loses fewer payments to it.

Money

“What the window cost and what came back.”

Line	What it is
Landed	Collections that landed, before fees.
PaySigna fees	Our fee and tax on them, with the effective rate — fees as a share of what landed.
Partner commission	A fee you accepted for a company that referred you. Shown only when there is one.
Credited to you	What reached your balance for them.
Refunded	Refunds in the period, and how many payments.
Disputed	The amount customers disputed, and how many cases.
Paid out	Payouts that succeeded.

Two warnings appear here when they apply:

Disputes at 1% of payments or more — “card schemes review accounts above 1%.” Read Disputes now rather than later.
Refunds more than doubled on the period before.

Top customers

“By what they paid in the window.” The five customers who paid most, with their email or masked phone. Payments with no identified customer are not ranked.

Subscriptions

Shown when the account bills subscriptions — see Billing.

Figure	What it is
Monthly recurring	Active and past-due subscriptions, each plan’s price turned into a monthly figure.
Active / In trial / Past due	Subscriptions in each state now.
New / Ended	Created, and ended by anyone, in the period.
Renewing in 7d	Renewals due in the next seven days.

Latest transactions

“The five most recent, whichever way the money went.” Needs transaction.read.

Controls

Control	What it does
Period	7, 30 or 90 days.
Refresh	Re-reads the figures. Nothing on the page updates by itself.
Environment switch (top bar)	Test and live have entirely separate dashboards. A zeroed dashboard is nearly always the test environment.

From the API

The same figures are at GET /v1/dashboard/insights?days=7|30|90 on the portal API, for the environment you are viewing. It is not part of the payment API.