The provider console
How it is organised
Section titled “How it is organised”The sidebar is ordered by how often a shift touches a section. Queues first, because they are work that arrives; the ledger, pricing and platform plumbing are consulted rather than worked.
| Section | Holds | Read about it |
|---|---|---|
| Queues | Approvals, KYC review, Risk alerts, Risk review, Risk rules, Limits, Disputes | Working the queues, Risk |
| Merchants | Merchants, Transactions | Merchants |
| Money | Ledger, Periods, Settlements, Withdrawals, Commissions, Reconciliation | Money, Reconciliation |
| Partners | Partners, Routing, Pricing | Partners and routing, Pricing |
| Platform | Audit, Data requests, Workers, Staff, Reference data | Platform |
Two rules govern everything here
Section titled “Two rules govern everything here”Every action requires a permission, and the console hides what you lack
Section titled “Every action requires a permission, and the console hides what you lack”267 of the 287 console operations require a named permission. The difference between what a KYC reviewer, a finance approver and a support agent can reach is most of the console.
The sidebar shows you the pages you can work and hides the ones that would answer
403. So a section you expected and cannot see means your role does not carry that
permission — not that you are in the wrong place. Ask whoever administers staff
access; see Platform.
This is also why you should not share accounts or borrow a colleague’s session to “just check something”. The permission model is the control, and the audit trail is what makes it real.
Every privileged act is audited, against you by name
Section titled “Every privileged act is audited, against you by name”Not against “the console”, and not against a service account. Approvals, KYC decisions, limit changes, routing changes, pricing changes, data exports and erasures all write an audit entry naming the staff member who did it.
That record is the reason the console can be trusted with the powers it has. Treat it as a feature rather than as surveillance: it is also what protects you when somebody asks six months later why a merchant’s limit was raised.
Dual control
Section titled “Dual control”Some actions cannot be completed by one person. A request is raised by one staff member and approved by another, and the approver may not be the requester — that is enforced, not a convention.
These land in Queues → Approvals. See Working the queues.
If you find yourself wanting to approve your own request because nobody else is around, the answer is to find somebody else, not to find a way around it. Dual control exists for exactly the situation where one person is under pressure and alone.
Test and live
Section titled “Test and live”The console shows both environments, and they are separate. A merchant’s test traffic is not their business; their live traffic is. When you are reading numbers to answer a question, check which environment you are in before you quote anything.
If you are new
Section titled “If you are new”Read Working the queues first — it is most of the job — then Risk, because the risk queue is where the judgement calls are and where a wrong call is most expensive in both directions.