Merchant Dashboard

Overview

What it means

A merchant dashboard is an interface that summarizes sales, invoices, payment statuses, balances, payouts and exceptions so a business can act on financial activity. Its accuracy depends on the underlying payment and reconciliation systems.

How it works

A dashboard typically aggregates data from checkout, wallet monitoring, provider APIs, treasury, settlement and customer orders. It should display definitions for pending, confirmed, paid, settled and available; show filters for networks and time zones; and preserve links to transaction and invoice evidence.

Understanding the technical details

Dashboard design should make statuses comparable across providers and networks without hiding underlying differences. Show the merchant the relationship among invoiced, detected, paid, settled and available values, with filters for asset, chain and reporting period. A drill-down path to the source invoice or transaction prevents disputes from becoming spreadsheet guesswork. Administrative actions such as refund approval and payout-key rotation need separate permissions and audit trails from read-only reporting.

Additional protocol context

The dashboard is a presentation and control layer, not automatically the authoritative accounting record. Data can be delayed, aggregated, filtered, or formatted differently from APIs, ledgers, and bank settlements. Compromised sessions or excessive roles can expose customer data and enable high-impact changes.

Merchants should use strong authentication, least privilege, session controls, change confirmation, and audit logs. Metrics need clear definitions and freshness indicators. Critical balances and settlements should be reconciled with underlying records, while sensitive actions such as payout changes or credential creation should receive additional verification and notification.

Common failures and limitations

Stale caches and mixed currencies can mislead. Dollar-equivalent values need valuation timestamps and rates. Sensitive actions such as changing payout addresses should require stronger authorization than viewing analytics.

Related concepts

Crypto Checkout, Crypto Refund, Payment-to-Order Reconciliation.

Further reading

OxaPay — Developer documentation.