Skip to content
guideNovember 9, 2026 · 9 min read

Crypto exchange admin panel: what the operations console must do (KYC queue, approvals, audit log)

What a crypto exchange admin panel must do: KYC queue, withdrawal approvals, ledger and stuck funds, markets, reports, system health, roles and an audit log.

BitPolaris Engineering

A crypto exchange admin panel, or operations console, is the software the exchange’s own staff use to run the venue. They review KYC applications, approve withdrawals, find stuck deposits, list markets, set fees, answer customers and produce reports for the regulator. Customers never see it. The compliance officer, the finance team, support and the engineer on call work in it all day. If it is missing or thin, those jobs move into spreadsheets, direct database queries and chat messages. Nothing of that is logged, and a licence review asks to see the log.

This guide covers what the console must do, how its roles and approvals should work, what the audit log needs to record, and how to test a vendor’s console before you buy. Our examples come from the 53-screen admin we build and run at the reference exchange, and we say where our design is one choice among several.

Why the admin panel matters more than buyers expect

RFPs for exchange software tend to spend pages on the matching engine and one line on “admin panel”. In daily operation, and in a licence application, the weight is the other way round. Regulators write console functions into their rules:

  • Georgia’s NBG requires every operation to be recorded, with a log of each action on that data, and retrievable quickly from the head office (our Georgia guide).
  • El Salvador’s DASP regulation requires an exact, auditable record of each transaction, the ability to suspend and close accounts, and controls that detect anomalous employee behaviour (our El Salvador guide).
  • Technical files in other regimes usually include an exportable audit log of every money action and settings change. What regulators ask for collects the common items.

None of these rules names a screen. They are met through screens, though: an approval nobody can see in a queue did not happen as far as an auditor is concerned, and a balance correction made in SQL leaves no stated reason.

The eight jobs a crypto exchange admin panel must do

Job What the console must do Who uses it
Users and KYC Search users; filter by KYC level and status; work a manual review queue; record account actions (freeze, unfreeze, close) with a reason; show sign-ins, devices and failed attempts Compliance, support (read-only)
Money movements Deposit and withdrawal queues with chain, transaction hash, confirmations and status; approve and reject with real state changes; fiat rail entries with their own accounting Finance, compliance
Ledger and stuck funds Double-entry ledger view; one list of transfers that were paid on chain but look wrong in the records, or that are waiting for an approval nobody gave; balance adjustments that require a reason Finance
Markets and fees Market definitions, precision and status; asset and chain mapping; trading and transfer fees, maker and taker tiers Operations
Liquidity A console for the market-making engine: books, spreads, hedging venue balances, alerts; market-maker volume kept apart from customer volume Treasury, operations
Reports Financial and money-flow series, user growth, volume split by organic and market-maker, exports for regulator returns Management, compliance
System health Per-service status, host metrics, queue depths, and scanner heights compared with real chain heights so a lagging chain never shows green Engineering on call
Support Live chat and tickets next to the customer’s history, with handoff between operators Support

Behind all eight sit roles, approvals and the audit log, which the next sections cover.

Two of the jobs are where in-house builds and open-source kits usually fall short.

Stuck funds. Deposits and withdrawals get stuck for ordinary reasons: a chain scanner lags, a fee spikes, a node returns stale data, or an approval waits for someone on holiday. If the console has no single list of every suspended transfer, each case is a support ticket that an engineer researches by hand. Why crypto withdrawals get stuck explains the causes; the console’s job is to show them in one place with the next action.

Market-maker volume. If the venue runs its own market making, the reports must show organic customer volume and market-maker volume separately. A single volume number mixes the two, which misleads management and can mislead a regulator, so it should not reach a report.

Roles: start from no access

A console role model has one rule: every role starts with no permissions, and each permission is granted for a reason. The common mistakes are the reverse. Teams begin with an admin role that sees everything and remove screens later, or they share one login across the team.

A workable minimum has three levels plus a custody officer group:

Role Sees Can change Cannot touch
Support Customer list, KYC status read-only, tickets and chat Ticket status, chat handoff Finance screens, approvals, settings
Admin (compliance, finance, operations) Their own area of the eight jobs Approvals and configuration within limits Role assignment, platform-wide settings
Superadmin Everything Roles, platform settings Nothing alone that moves money above a threshold
Custody officer (separate console) Approval queue, vault and node health Signs withdrawals within the quorum Exchange settings

The support row matters more than it looks. Support staff talk to the public all day, which makes them the most exposed to social engineering. In our console a support login can read a customer’s KYC status but sees no finance screen at all.

The second rule is a second person for sensitive actions: role changes, fee changes, large manual adjustments and policy changes. This is the four-eyes principle most auditors ask about. Make the console enforce it, so it does not depend on a written procedure that staff can skip under pressure.

How withdrawal approvals should work

A withdrawal passes through two kinds of control. The exchange console decides whether the withdrawal should go: KYC level, limits, sanctions and KYT results, address whitelist. The custody layer decides how it is signed. An exchange that holds client assets needs both, and the console must show where each withdrawal is waiting.

A policy that auditors can read sets requirements by asset and amount band. Our custody policy engine, as an example of the structure:

  • 1-of-3 approvals below a floor, 2-of-3 for the middle band, 3-of-5 with a delay above it;
  • every approval is a TOTP event by a named officer;
  • address whitelisting with a 24-hour delay on new addresses, on by default;
  • daily caps per asset and per customer tier;
  • a documented break-glass procedure that leaves a record and pages the whole officer group.

The numbers are a starting point, not a standard; your risk assessment sets the bands. The console requirement is that the policy is versioned, that a change to it is itself an approved action, and that a rejected withdrawal returns funds to the customer’s balance with a recorded reason. MPC vs multisig covers the signing side.

What the audit log must record

“Audit log” can mean anything from a web server access log to a tamper-evident record of business actions. For an exchange, the useful definition is this: every settings change and every money action, with enough context to reconstruct the decision without asking anyone.

Field Why it is needed
Who (named user, role, session) Shared accounts make the log useless
What (action and object, e.g. “withdrawal 81723 approved”) The auditor searches by object
When (server time, UTC) Ordering across services
Before and after values A fee change without the old fee cannot be reviewed
Reason (free text or a code, required for adjustments and account actions) The question every regulator asks
Result (success, rejected, failed) A failed attempt is a security signal
Source (IP, device) Ties the action to a session

Three properties matter as much as the fields. Operators must not be able to edit or delete entries; an append-only store or a regular export to storage they cannot write to is enough. The log must export by date range, user and object without an engineer running a query. Security events (failed sign-ins, new devices, 2FA resets) belong next to business actions, because an incident review needs both on one timeline.

How to evaluate a vendor’s admin panel

Screenshots show layout, not behaviour. Ask for a session with write access on a dedicated environment and do these ten things yourself:

  1. Create a support user and confirm it cannot open a finance screen.
  2. Work one KYC application from the queue to a decision.
  3. Freeze an account with a reason, then unfreeze it.
  4. Approve one withdrawal and reject another; check the rejected funds return to the balance.
  5. Make a balance adjustment and confirm the console demands a reason.
  6. Change a trading fee and see whether a second approver is required.
  7. List a new market with its precision and fees.
  8. Open the stuck-funds list and ask how an entry gets there.
  9. Look at system health while the vendor stops one chain scanner on the test environment.
  10. Export the audit log for the session and find steps 2 to 7 in it.

A vendor that cannot run this session is selling a console that does not exist yet. The RFP checklist puts the same tests into a scoring table, and choosing a KYC provider covers whether manual review should sit in the provider’s dashboard or in your console.

What it costs to build or buy

An admin panel is not usually priced on its own. Vendors include it in the exchange licence, and in-house teams spread it across every sprint. If you build it yourself, treat it as a product with its own backlog. It changes with every new chain, module and regulatory request, and it needs the same release discipline as the trading engine.

In BitPolaris pricing the console is part of the Exchange block, not a separate line: €24,500 one-time for the self-hosted licence plus €4,900 a year for updates and support, €58,100 for the source-code licence, or €7,700 setup plus €1,600 a month on the white-label cloud. Optional modules such as Earn or Token Launch bring their own consoles and are priced separately on the pricing page.

Crypto exchange admin panel FAQ

What is a crypto exchange admin panel?

It is the internal operations console where the exchange’s staff review KYC, approve withdrawals, manage markets and fees, reconcile the ledger, answer customers and produce reports. Customers never see it; the regulator sees its records.

What features should a crypto exchange back office have?

At least eight areas: users and KYC, deposit and withdrawal queues with approvals, the ledger with a stuck-funds list and reasoned adjustments, markets and fees, liquidity, reports, system health, and support. Behind them it needs roles that start from no access, a second approver for sensitive actions and an exportable audit log.

Who should have access to the admin panel?

Named staff only, each with the narrowest role that does the job. Support reads customer and KYC status but has no finance access; finance and compliance approve within limits; very few people assign roles. Shared logins defeat the audit log.

Is the custody approval the same as the withdrawal approval?

No. The exchange console decides whether a withdrawal is allowed (limits, KYC, screening, whitelist). The custody layer decides how it is signed (quorum, delays, hardware keys). Both need logs, and the console should show which one a withdrawal is waiting for.

Can I use the KYC provider’s dashboard instead of my own console?

You can, but then reviews live in a second system with its own logins and its own log. Feeding the provider’s results into a queue in your console keeps one role model and one audit trail. Either way, the provider’s fees stay on your contract with the provider.

BitPolaris exchange software includes a 53-screen operations console plus Mirror, Earn and custody officer consoles: roles that start from no access, a second approver for sensitive actions, a stuck-funds list and an audit log on every money action. You can try it in a guided session with write access.

See the operations console · Build a year-one estimate

Exchange software already in production

Spot trading, liquidity mirroring and the operations console. Cloud from €1,600/month, self-hosted from €24,500 one-time.