Finance -> Payouts

Every payout request your traders have made, as a queue. Nothing is paid by the platform itself: you send the money the way you always do, and the screen keeps track of what was decided, by whom and when.

The queue

The list opens on the requests that wait for a decision, the one that has waited longest on top, across the whole width of the screen. Nothing is opened until you pick a request. Then the list folds to a column on the left and the request slides in beside it. Esc or the cross folds it back out.

Above the list sit the counters: how many requests there are, how many wait to be reviewed, and how many are approved and wait for the money, with what you still owe your traders for those beside it. What the pending ones ask for is in the tooltip. Click either count to show only those. Then how long the oldest pending request has waited, and on a wide screen what went out in the last 30 days. Amounts are never added up across currencies, because accounts are not all in dollars.

Each row shows the trader, the payout number and account, the amount and what goes to the trader, when it was asked for and how long it has waited, the method, your tags and the status. A shield marks a trader with open fraud flags, for those who may see them, and a speech bubble a request that is discussed in a ticket. The list reads itself again every minute, so a request a colleague just decided or a trader just made shows up without a reload.

J and K walk the list and Enter opens the lit row. Once a request is open, resting on another row with J or K opens that one beside it.

Each request has its own address, so a link from a notification, a ticket or a colleague opens straight on it, with the tab it was on.

Search matches the trader's name and email, the payout number, the account number and the reference you gave a payment when you marked it paid. Several words narrow further: every one of them has to match. Start a word with # to look only at payout and account numbers. A full payout, trader or account ID finds exactly that one. Press / anywhere to jump to the search box.

The filter menu holds the sort order and the filters:

Filter	What it narrows to
Status	To review, to pay, both, paid, rejected, or everything
Method	Bank transfer, crypto or PayPal
Requested	The last 7, 30 or 90 days, or the last year
Tag	Requests carrying one of your tags
Fraud flags	Traders with open fraud flags, for those who may see them

The queue order puts what waits for a decision first, then what waits for the money, each oldest first, and everything settled after it, newest first. The other orders are newest, oldest, largest amount and trader. On a wide screen the column heads sort the same way.

Filters and the page live in the address bar, so a filtered view can be bookmarked or sent to a colleague and opens exactly as you left it.

A request

The head of a request names it by its payout number, which copies with a click, and its status. Under it are the amount, the method and the day it was asked for, then the trader with their email, and anything worth knowing about them: a deleted trader, one who cannot sign in, somebody on your own team, payouts held by fraud detection, open fraud flags and the linked ticket. Your tags follow on a line of their own. Click a tag to show only the requests carrying it.

The decision a request waits for sits beside it: Approve and Reject while it is pending, Mark as paid once it is approved. The menu behind ... opens the trader, the account or the ticket, narrows the list to this trader, copies the number, ID, email or a link, and holds Withdraw approval for an approved request. Notes a colleague pinned show under the head, whichever tab is open.

Below that are the facts asked first: the amount and the split, what goes to the trader and what you keep, the account balance, what was paid before from the same account, and how long it has waited or when and by whom it was decided.

Request

What stands in the way, read again from the account as it is the moment you open it. A warning names the problem in a line: the account is no longer funded, the balance is below the amount, the consistency rule fails, trading days are missing, the amount is above the profit or outside the payout limits, identity verification is missing where your firm asks for it, a trading rule holds the payout, positions are still open, or the trader has open fraud flags or held payouts. A consistency rule that passes says so too. Only the consistency rule and the balance stop the server: the rest is for your judgement.

Then where the money goes, as the trader gave it, each detail copied with a click. What happened so far, with who decided, the note they left and the reason the trader was given. And the team's notes.

Account

The account the money comes from: its status, balance, profit, high water mark and size, the payout rules of its phase (split, how often, the first one, the minimum and maximum and the trading days needed), and how it traded over its whole life: win rate, profit factor, the result per trade, average win and loss, best and worst day, trading days, how long a trade is held and the longest streaks. Then how far it fell: the deepest drawdown from its high, the drawdown and equity right now, the best and worst single trade, the volume in lots and the commission and swap it paid. Under it the trader's latest twenty other payouts, on any account, with what was paid to them so far. Click one to open it in place.

Trades

Every trade of the account, open positions first, then what closed, fifty to a page. Closing a position is done from Live Monitoring, not here.

Fraud

The trader as fraud detection sees them: what is held back from them right now, the flags they are in, and the detectors they are held to differently. With Manage Fraud a restriction can be lifted from here.

Ticket

The ticket the request is discussed in, with its status, who has it and its last messages, and a link to answer it under Tickets. Without one:

Link a ticket picks one of the trader's tickets, open ones first.
Open a ticket starts a new one with the trader from the payout itself. You write the subject and the first message, and the trader gets a notification, and an email when they are offline.

A ticket opened this way starts with the assistant blocked, so the trader cannot hand the conversation to the AI. Someone on your team can switch it back on from the ticket. A trader has one open ticket at a time, so when they already have one the tab offers to link that one instead. Unlinking leaves the ticket as it is.

Activity

Every decision, the payment and the notes, newest first, with a link to the full activity log.

Deciding

Every decision asks first, in a dialog that says what happens to the money and who is told. It is also in the menu of a row, so a request that needs no reading is decided from the list. When a decision takes the open request out of what the list shows, the next one opens in its place, so a morning's queue is worked through without going back.

Approve takes an optional note for your team and tells the trader the request was approved. Nothing leaves the account yet. It is refused while the account's consistency rule fails, and the dialog says why.

Reject asks for a reason, which the trader reads in their notification and on their payouts page, and an optional note for your team. Nothing is taken off the account.

Withdraw approval rejects a request that was approved but not paid yet, for when something turns up between approving and sending the money. It asks for a reason the same way, and the trader is told it was declined after all. A request somebody is marking paid at that same moment cannot be withdrawn as well: one of the two is refused.

Mark as paid is for after you have sent the money. It takes an optional reference, such as the transfer reference or a transaction hash, that only your team sees and that search finds. When the trader gave a payment reference, put it in the description of the transfer yourself: the platform does not send the money, so it cannot add it for you. Marking it paid takes the requested amount off the account balance, tells the trader the money is on its way, and issues a payout certificate from your default payout template. It is refused when the balance is lower than the amount.

Every decision is written to the activity log with who made it.

Notes

The team's notes on a request sit at the bottom of the Request tab. Write one, edit or remove your own, and pin one so it shows above every tab for whoever opens the request next. Notes are saved with the save bar at the bottom, the same as everywhere else, and leaving with unsaved notes asks first. The trader never sees them.

Who can do what

Reading the screen needs View Payouts, and that includes the account and its trades. Approving, rejecting, marking paid, tags and notes need Manage Payouts: without it those buttons and entries are not there. The Fraud tab needs View Fraud, the Ticket tab a ticket permission, and the Activity tab View Activity Logs. Linking a ticket needs Manage Payouts and a ticket permission. Opening one needs Manage Payouts and Manage Tickets.

In the older designs

A firm on the OG or Tactical design keeps the screen it had: a list with a side panel and a separate full page per request. Approving, rejecting, marking paid, tags and the linked ticket work the same there. Notes, the checks for every payout rule, the Account, Trades, Fraud and Activity tabs, withdrawing an approval and the payment reference are only in the new Default. The notification a trader gets when a request is rejected comes from every design.

Payouts