For Crypto Brokers
Money in and money out, with the controls where they belong
Which funding routes a client sees is resolved from their group and jurisdiction. Withdrawals pass through the approval queue, allow-lists and limits you configure, and every step is recorded.
Withdrawal queue
3What funding operations require
This is where most operational load sits, so it is where the tooling has to be good
Routes per group
Available deposit and withdrawal methods are resolved from the client group and jurisdiction, so a regional rail only appears where it applies.
Live confirmation state
Digital asset deposits show confirmations accumulating in real time rather than appearing only once complete.
Approval queue
Withdrawals arrive in a queue with the full account context — balance history, recent activity, verification state — beside each request.
Limits and thresholds
Per-transaction and rolling-period limits by group, with automatic approval below a threshold and manual review above it.
Safeguards
Address allow-lists, second-factor confirmation and cooling periods after sensitive account changes, all configured per group.
See it live
A deposit flow a client finishes in seconds
The amount and payment method are picked on one screen, resolved from the routes their group and jurisdiction make available.
A withdrawal from request to execution
The most operationally sensitive path in the platform, step by step
- RequestAvailable
Checked before it is accepted
The destination is validated against the allow-list, the amount against the applicable limits, and any active cooling period is enforced before the request is created.
- ReservationReserved
The balance is held immediately
The amount moves from available to reserved as soon as the request exists, so a pending withdrawal cannot be spent on a trade.
- ApprovalReserved
Reviewed with the context beside it
Requests above the automatic threshold enter the queue, where an operator sees the account history and verification state without opening another screen.
- ExecutionDebited
Debited only on completion
The balance is debited when the transfer executes, not when it is requested, and the provider or transaction reference is written to the ledger entry.
What good funding tooling saves
Funding is usually the largest single source of support tickets and operational risk.
Faster approvals
Context beside the request means an operator decides in seconds instead of gathering information first.
Fewer fraud losses
Allow-lists and cooling periods remove most of the value of a compromised session.
Fewer status enquiries
Live confirmation state answers the most common support question before it is asked.
Clean audit trail
Every request, approval and execution is attributable, which is what a regulator or an auditor examines first.
FAQ
Deposits and withdrawals: common questions
5 short answers to what teams ask before a demo.
They are resolved from the client group and jurisdiction, so a method that only applies in one region is offered only to clients in the groups covering that region.
Yes. A threshold per client group determines which requests are executed automatically and which enter the manual approval queue. Rolling-period limits apply alongside per-transaction ones.
On execution. The amount is reserved when the request is created, which prevents it being spent on a trade, and debited only once the transfer has been carried out.
Address allow-lists with a delay before a new destination becomes usable, second-factor confirmation on the request, and a cooling period after a password or two-factor change during which withdrawals are held.
Yes. Digital asset deposits show confirmations accumulating in real time, and other methods show their current processing state, which removes most status enquiries from your support queue.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistWalk the funding flows with us
We will process a deposit and a withdrawal end to end, including the approval queue, during the call.