Dashboard
Manage cards, ledger accounts, and payouts from the Mono Dashboard.
The Mono Dashboard is the web interface where non-developer roles — operations, finance, customer support, compliance — interact with Core. Everything that the API exposes can be inspected from the Dashboard, and many actions (creating spending controls, freezing a card, triggering a manual payout) can be performed without touching code.
This page describes what each section of the Dashboard does and which role typically uses it. It is the right starting point for someone joining the team who needs to operate Core but does not write the integration.
This page is a dashboard scaffold. The full version will include screenshots of every section, role-based access notes, and end-to-end examples (e.g., "how to issue an emergency card replacement").
Sections
| Section | What it shows | Who uses it |
|---|---|---|
| Ledger | Per-account balances, transaction history, holds, settlements. | Finance, ops |
| Cards | Active and inactive cards, freeze/unfreeze, replacement requests. | Customer support, ops |
| Spending controls | Limits and rules attached to cards. | Ops, compliance |
| Payouts | Scheduled and ad-hoc payouts, status, failures. | Finance, ops |
| Webhooks | Endpoint configuration, recent deliveries, retry attempts. | Engineering |
| API keys | Key management, scopes, rotation. | Engineering, security |
Common operations
Specific walkthroughs (issuing a card, freezing a card, manually triggering a payout, investigating a failed authorization) will be documented here.
Webhook configuration
Creating a webhook
Webhook creation is done through the user interface:
- Go to settings.
- Click on Personal.
- Click on API.
- Click new webhook.
- Insert the HTTPS/HTTP URL that you had configured to listen the events.
- Click on save.
If everything is working as expected, there will be an alert indicating that we successfully created your webhook, and you should be able to see the URL listed on the page.
Webhook URLs are unique — you can only create one webhook per URL. To reuse a URL, delete the existing webhook first and create a new one. A new secret will be generated.
Always verify that your endpoint is receiving events correctly.
Viewing webhook details
Click the arrow at the end of the row where your URL is displayed to open the detail view. The detail view contains the webhook secret, which is hidden by default. Click the show/hide eyeball to reveal it.
Next steps
- Webhook conventions — signature verification, retry policy, and money fields.
- Architecture
- Best practices