Skip to main content

Overview

The Merchant Dashboard is a hosted web application that gives merchants a single place to run their acquiring operations.

What you can do here

At a high level, the dashboard supports four kinds of work:

  1. Take and track payments. Create one-off payments, accept invoice payments, view the running list of transactions, and inspect any single transaction in detail.
  2. Send invoices. Issue invoices to your customers and watch them move from pending to paid.
  3. Run your team. Owners invite teammates, assign roles, and control who can do what.
  4. Connect your systems. Generate API keys, register webhooks, and pull dashboard data into your own backend.

Who's it for

AudienceWhat they do hereWhere to start
Merchants (cashiers, ops, finance)Daily payment and transaction workFor Merchants
Admins / OwnersTeam management, account setupFor Admins
DevelopersAPI integration, webhooksFor Developers

A single user account can wear more than one hat — for example, an owner is also a merchant.

How permissions work

The dashboard is multi-user. Each merchant account has one or more owners plus any number of additional users in roles with limited permissions.

Confirm role taxonomy

The exact role names and the permissions matrix need to be confirmed. Send the list and I'll fill in Team & Roles.

Environments

The dashboard runs in at least two environments:

  • Production — your live account, where real money moves.
  • Development (https://dashboard.dev.pomelopay.com) — a sandbox for testing.
Are there other environments (staging, sandbox, regional URLs)?
warning

Always confirm which environment you're in before creating payments. Test transactions in production move real money.

What this dashboard does not do

To set expectations, here are things that live elsewhere:

{/* TODO: Confirm/extend this list with the team. */}

  • Onboarding & KYC. New-merchant signup happens outside the dashboard.
  • Customer-facing checkout pages. The dashboard manages payments — your customers pay through other surfaces.
  • Underlying processor configuration. Acquiring rails are configured at the platform level, not by individual merchants.
Confirm the boundaries above with product before publishing.