Funds & safeguards
Where the money sits, how it gets in, how it gets out, what stops it, and what to do when something does.
When a platform custodies other people's money, the useful thing to write down is not "we are safe" but the rules: every threshold, ceiling and fee, who decides, and what happens when they decide wrong.
Where the money actually sits
This is not segregated custody. Your balance is a row in the platform's ledger, not an account in your name; on-chain USDT is consolidated into platform wallets rather than held per user. Two checkable things hold it up:
- Double-entry. Every movement writes both sides.
- A full reconciliation every hour. Total debits against total credits, and each account's entries against the balance it displays — a mismatch freezes that wallet and raises an alert rather than being absorbed. See Security.
There is no third-party custodian and no proof of reserves. You are entitled to know that before you deposit.
Deposits
| Minimum | Fee | Credited | |
|---|---|---|---|
| USDT (TRON) | 10 USDT | 3 USDT | On chain confirmation |
| USDT (Solana) | 2 USDT | Free | On finality (32 confirmations) |
| Card | 5 USDT | 5% + 0.4 USDT | On payment success |
The fee is not a margin, it is the sweep cost: moving funds off a deposit address into the main wallet costs gas — about 2.24 USDT on TRON. A Solana sweep is near-free, so that rail carries no fee.
The card rail runs through Dodo Payments as merchant of record and is deposit-only.
When sell-side income becomes spendable
The moment a request settles, the seller's income lands in the wallet's payable column, and a release job moves it into the spendable balance 24 hours later.
Those 24 hours exist for disputes: while the income is still in payable, a refund claws it back from a column the seller cannot spend from. Past that window a refund still works, it just stops being guaranteed to find the money.
Disputes
A buyer can dispute their own settled tasks within 72 hours of the task ending. An upheld dispute refunds by reversing entries — the original settlement is never deleted, an opposing one is written next to it.
Disputes feed the seller's reputation, so filing them in bad faith damages someone — which puts the filing itself inside the risk system's view.
Withdrawals
| Minimum | Fee | Per-transaction cap | |
|---|---|---|---|
| USDT (TRON) | 20 USDT | Live chain quote, 5–10 USDT | 500 USDT |
| USDT (Solana) | 10 USDT | 1 USDT | 500 USDT |
Two frequency gates on top: at most 4 per hour, and at most 20,000 USDT in any trailing 24 hours.
Fee convention: the amount you enter is what leaves your balance, and amount − fee is what lands on chain. The fee is quoted from the chain cost at submission and locked onto that withdrawal.
There is no manual approval queue
Worth stating on its own, because "under review" is this industry's favourite way to stall.
A normal withdrawal never touches a human. The risk rules run on submission; pass them and it goes straight into the broadcast queue, where on-chain confirmation decides the timing. The one case that reaches a person is repeated broadcast failure (5 attempts) — a node or address-level fault, not a review of you.
Every reason a withdrawal can be refused
These are all of them. There is no catch-all "other".
| Reason | How it is judged |
|---|---|
| Malformed address | Validated in the destination chain's own encoding. A TRON address pasted into a Solana withdrawal is unrecoverable, so this one has to be a hard stop. |
| Below the minimum | See the table above |
| Over the per-transaction cap | 500 USDT |
| Over the frequency limit | 4 already in the trailing hour |
| Over the daily limit | Trailing 24h total + this one > 20,000 USDT |
| Insufficient balance | Spendable balance (excluding payable) is under the amount |
| Address not whitelisted | Only when the account is in whitelist-only mode |
Every refusal writes an audit record carrying the reason and the figures it was judged on. When you ask why a withdrawal did not go through, that record is what we read.
What happens to your balance if the account is terminated
Section 9 of the terms says a confirmed withdrawable balance can still be taken out on termination, unless the balance itself came from conduct found to be in breach. That "unless" points only at the five items in section 6, and the burden of proof is ours:
- We have to produce the specific task IDs, timestamps and figures showing where the money came from.
- Only that portion is withheld, not the whole balance.
- The notice has to name which clause and which records.
- You have 30 days to appeal, reviewed by someone outside the original decision.
Put plainly: we cannot keep your money because something "looked off" — only because we can point at which requests, and only those.
The parts we are not dressing up
- No segregated custody, no proof of reserves.
- Withdrawals depend on the hot wallet. A large payout can drain it, and what follows queues behind a sweep — tens of minutes. You see "broadcasting", not a failure.
- There are no published payout-time statistics yet. The sample is not large enough for a median and a P95 that mean anything; they go here when it is.
If any of the above does not match what you actually hit, write to support@asale.ai with the withdrawal ID.