---
title: "Deposits & withdrawals"
description: "The cashier queues — approving withdrawals, reviewing wire and large deposits, and handling returns and refunds."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.callistocrm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Deposits & withdrawals

The cashier area holds the queues where money movement needs a human:
withdrawal review, wire-transfer deposits, and large deposits held for proof
of funds. Ordinary PSP deposits clear automatically on provider confirmation
and never appear in a queue.

## Withdrawal review

Every client withdrawal waits for manager review. The queue has **Pending /
Approved / Rejected** tabs with filters for user, amount, currency, payment
method, and date.

From a pending withdrawal: **"Accept Withdrawal"** or **"Decline"** (reason
required). Withdrawals routed to the Pakistan Local Bank Transfer rail
additionally offer **"Approve & send to LD Portal"** alongside a plain
accept.

Approval is **final** — once approved, a withdrawal never returns to pending,
and managers cannot un-approve. What can still change is the payout outcome:
if the payment rail later refuses the payout, the transaction surfaces as
**Rejected** or **Returned** (see below), never as un-approved.

The approve/decline buttons disable themselves when acting would be unsafe:
the trader is KYC-suspended, the destination details fail validation, the
trader has an open compliance case, or a payout is already in flight on the
rail.

### First-time payout accounts

A destination account being used for the first time is flagged **"New
account — first use"** — check the uploaded proof of bank account matches the
name and account number before approving. The Pakistan Local Bank Transfer
rail is exempt: no proof is required there because the payee name is set from
the client's verified profile.

### When a payout is refused

If the payout rail declines or the push cannot be delivered, the withdrawal
detail page offers two resolutions:

- **"Return funds"** — credits the debited amount back to the client's
  wallet and marks the withdrawal **Returned**. When the rail's state is
  ambiguous, you must first confirm you checked the provider portal and the
  order will not be paid. Irreversible.
- **"Re-send to LD Portal"** — re-queues the same payout. Safe to repeat; the
  provider de-duplicates by order id.

## Wire-transfer deposits

Manual (bank wire) deposits are reviewed in the deposits queue under **"Wire
transfers"**, bucketed into **Action required / Awaiting trader / Approved /
Rejected**. Actions on a submission: **"Accept & credit"**, **"Change amount
& accept"** (when the received amount differs), **"Request info"**, and
**"Reject"**. Rejecting a wire deposit does not trigger any refund — in the
usual case the wire never arrived.

## Large deposits (proof of funds)

Deposits over your configured thresholds settle at the provider but are held
un-credited pending review, under the **"Large deposits"** tab. Two
thresholds (set in Configure → Payment Providers, with per-region overrides):

- **Proof of funds threshold** — the trader must supply documents; an
  accepted document clears their further deposits for a configurable number
  of days.
- **Always-review threshold** — held for manager approval every time,
  documents or not.

Actions: **"Accept & credit"**, **"Request info"**, or **"Reject"**.

### Refunding a declined large deposit

Because the money already settled at the provider, declining opens a refund:

- **Crypto deposits** — the trader confirms a return address, and the refund
  pays out automatically for the settled amount (**Awaiting address →
  Dispatched → Refunded**).
- **Other methods** — you return the funds via the provider outside Callisto,
  then click **"Mark refunded"** and confirm. This records the return and
  closes the deposit; it cannot be undone.

Source: https://docs.callistocrm.io/deposits-and-withdrawals/index.mdx