Payouts

Pass. Get funded.
Get paid in crypto.

80% from the first dollar. First request from day 5, then on demand. $50 minimum, USDT or USDC, settled in 24 hours or we add +2%. If the rulebook is met, the request is approved — there is no discretionary review after you ask.

How a payout will work

How a payout works

The same terms that will govern the first request — published in the rulebook, not invented at the payout gate.

First request
from day 5
After that
on demand
Minimum
$50
Split
80% from the first dollar
Monthly cap
2% of simulated size, full carryover
Settlement target
24 hours
Miss the target
+2% to the trader
Rule 10 review cap
72 hours, then a decision
Approval
rules-based, not discretionary
Rails
USDT / USDC, no fee added by us

Approval is arithmetic, not judgement

A request is checked against the same published rules that are visible on the account screen the whole time. There is no discretionary review step between the rules and the money, because a discretionary step is where a week goes and where an argument starts. If the conditions in the rulebook are met, the request is approved.

The 24-hour rule carries a penalty

If a request is not settled within 24 hours of approval, the system adds 2% to the amount by itself. No ticket, no chasing, no goodwill gesture.

One thing pauses the clock rather than missing it: an active review under rule 10, capped at 72 hours. At the cap a decision is mandatory: settle, with the +2% added, or refuse, citing the published clause. “Under review” is a state with a deadline, never an outcome.

Rails

USDT and USDC. No fee added by us. Where the network charges, the charge is shown before the request is submitted rather than discovered in the amount that arrives. Bank rails later, if we add them — payouts launch on crypto.

What can cause a refusal

5 grounds, listed in advance

A reason that is not on this list cannot be used, and adding one is a rulebook change with a version number attached. The fifth was added exactly that way, at rulebook v0.10, and its review mechanics were revised the same way at v0.11 — dated, with the version number moved, both times.

Refusal ground 01

Copying another funded account

Established on execution timestamps across accounts linked to one identity, not on a view about strategy. The evaluation fee is returned.

Refusal ground 02

Account holder is not the payout beneficiary

The name on the account and the name on the destination must match. Refused pending correction rather than permanently, and payable once they do.

Refusal ground 03

Identity verification not completed

Refused pending completion, not forfeited. The amount stays payable indefinitely and is paid the day verification clears.

Refusal ground 04

The request exceeds the accrued balance

An arithmetic refusal. The payable part is paid; the remainder is not created by asking.

Refusal ground 05

Account multiplication under rule 10

Opposite positions netting to roughly zero across linked accounts, an account transferred or traded by a third party, or the same trades duplicated across a cluster to multiply payouts. Established on the trade-correlation review that runs through the whole evaluation, not invented at the payout gate; the refusal row cites rule 10. A request under review is marked so in the ledger, with the review’s start time, and the review is capped at 72 hours — at the cap it either settles with the +2% penalty or is refused under this clause.

One ground that appears in this industry is deliberately absent here: a “risk management review” with no stated criteria. It is not in the rulebook, so it cannot be used. upme does hold a consistency cap — no single day and no single trade above 40% of total profit — but it is published as a number in advance, not a score applied after the fact.

These five are the only grounds on which a payout is refused. Separately, and earlier in the process, the v1.2 conduct rules in the rulebook (feed integrity, execution realism, single-position exposure and the probability-pass ban, rules 12–18) can withhold a pass or void an evaluation at the trading stage — rule 18 extends the same rule 10 basis listed above. They are published now and enforced once the platform is wired, and none of them adds a new reason to refuse a payout on a result that clears the rules.

Questions

Questions

If a request is not settled within 24 hours of approval, 2% is added to the amount automatically, with no ticket required from the trader, and the late row stays in the public ledger permanently with its elapsed time. The one thing that pauses the clock is an active rule 10 review, which is shown publicly in the ledger with its start time and capped at 72 hours; at the cap the request either settles with the 2% added or is refused citing the specific violation.
No. A request is checked against the same published rules visible on the account the whole time, with no discretionary review step inserted between the rules and the money.

Reserve a seat. Get paid when you pass.

Free, dated seat in the queue. Sales open at rulebook v1.2.

Take a seat →