Dashboard guide
Run your business from the Wajub dashboard, one task at a time. Who can do what, Sandbox and Live, and the security code.
This guide is for the people who work in the dashboard at dashboard.wajub.com without writing code: owners, finance, support and accounting teams. Each page walks through one task, step by step, with what the screen shows next. If you connect Wajub to your own site or app, start with Get started.
To begin, Get your first payout follows the whole path, from signing up to the first transfer to your own account.
How each page reads
Before the steps, every page says who can do the task, which plan it needs when not every plan has it, whether it only works in Live, and whether the dashboard asks for a security code. The rules below apply everywhere, so a page only repeats them when it differs.
Sandbox and Live
The switch at the top right of the dashboard moves between Sandbox, where payments are simulated, and Live, where real money moves. The two hold separate data: a customer or a payment created in Sandbox never shows up in Live. Environments explains what the sandbox simulates.
A new organisation stays in Sandbox until Wajub has approved its account activation. After that, the owner, an Administrator, a Developer, or a custom role with Manage settings or Manage developer settings can switch. A Sandbox user always stays in Sandbox.
Six modules only exist in Live and leave the menu in Sandbox: Invoices, Payment links, Revenue, Tax, Shield and Orchestration. Their keyboard shortcut tells you they are only available in live mode.
Some actions need Live too: sending a transfer, editing, archiving or deleting a beneficiary, merging two customers, and every export apart from the Konsole exports and the export of your own data. In Settings, the Payment links, Invoices, Transfers and Customer merges sections stay in the list in Sandbox, marked Live only.
Roles
An organisation has one owner, the person who created it, and the members the owner invites. The owner can do everything, and is the only one who can close the organisation, hand it over to someone else, or read the conversations members had with the assistant. Each member holds one of seven roles.
| Role | What it covers |
|---|---|
| Administrator | Everything the owner can do, apart from the three actions above. |
| Developer | API keys, webhooks and Konsole, technical settings, and the switch between Sandbox and Live. Reads payments, customers, invoices and settings, and manages payment links. |
| Finance | Payments, without refunds or disputes. Transfers and beneficiaries, invoices, payment links, subscriptions, reports, revenue and tax. Reads customers. |
| Analyst | Reads payments, customers, transfers, invoices, payment links, subscriptions, reports, revenue and tax. Changes nothing, apart from opening support tickets. |
| Support specialist | Payments, refunds, disputes and customers. Reads invoices. |
| Viewer | Reads what an Analyst reads, plus the settings. Changes nothing, apart from opening support tickets. |
| Sandbox user | Sandbox only: test payments, API keys and webhooks. Reads customers. |
Shield is open to the owner, Administrators, and custom roles that include it. When none of the seven roles fits, the owner, an Administrator or a custom role with Manage members can build one in Settings › Members › Custom roles. A custom role can only hold permissions its creator holds.
The security code
Sensitive changes ask you to prove it is you first: refunding a payment, sending a transfer, deleting a payment link, creating an API key, accepting a dispute or editing a custom role, among others. The dashboard opens Security verification and asks for a Verification code. You get it by email, by SMS if SMS is your two-factor method and your phone number is saved, or from your authenticator app if you turned one on.
Once you have typed the code, the dashboard does not ask again for the next 30 minutes. Your password never replaces it.
Modules outside your plan
When your plan does not include a module, its menu entry stays, marked Not in your plan. Opening it shows Upgrade required, with the add-on that unlocks the module when one exists, otherwise a higher plan.