Merchant Console 3.0: one dashboard for growth, risk, and settlement

Merchant Console 3.0 is now live for all MiSPay merchants, replacing the growth report, the settlement export, and the risk summary with a single workspace.

The rebuild started from a simple complaint heard in almost every merchant review: the numbers were available, but they lived in three places that never quite agreed with each other.

What changed

One source of truth

Orders, approvals, refunds, disputes, and settlement now read from the same ledger. A finance team can open a settlement line, click through to the originating order, and see the approval decision and any dispute attached to it without leaving the page.

Plans a merchant can configure

Instalment plans are now configurable per category and per price band, directly in the console. A furniture retailer can offer longer plans on bedroom sets and shorter plans on accessories without opening a support ticket or waiting for a release.

Reconciliation that finishes

Every settlement batch exports with a stable reference, a per-order breakdown, and fee lines itemised by type. Reconciliation is designed to close to the riyal, and the export format is stable across versions.

Measured in the beta

• 62% fewer support tickets about settlement discrepancies

• Median reconciliation time down from 3 days to under 4 hours

• 4 in 5 beta merchants changed at least one plan configuration in week one

• Dispute response time down 37% with the inline evidence upload

Access and permissions

1. Role-based access with separate finance, marketing, and operations views

2. Read-only accounts for external accountants and auditors

3. A full activity log for every configuration change, with actor and timestamp

4. API parity, so anything visible in the console is available programmatically

"The first thing our finance lead said was that she stopped keeping a parallel spreadsheet. That spreadsheet had existed for two years."

What we removed

Half of the work was deletion. The old console carried four separate exports, two overlapping performance charts, and a settings page that had grown to thirty-one options, most of which no merchant had ever changed. Anything used by fewer than five percent of merchants was either removed or moved behind the API, where the merchants who genuinely needed it were already working.

The design was reviewed with nineteen merchants across the three markets, including three finance teams who agreed to reconcile a full month in the beta before their existing process. Every screen in the release was rejected at least once by that group before it shipped.

Migration

All merchants have been migrated automatically, with the legacy reports available in read-only mode until the end of the quarter. Historical data goes back to a merchant's first order — nothing was truncated in the move.

Documentation, the export schema, and a walkthrough for finance teams are available in the merchant help centre.

About MiSPay

MiSPay is a regional payments company that lets shoppers split purchases into predictable instalments and helps merchants convert more of the demand they already have.

For press enquiries, contact press@mispay.co.