Profit Share vs Payout Cap in Prop Accounts
Profit share and payout cap answer different questions. This guide shows how to estimate a prop-firm withdrawal without confusing the two.
Yash R
· Updated

A prop firm's profit-share percentage and its payout cap measure different things. The share describes how an approved reward is divided. A cap limits how much can be requested during a stated period or account stage. Minimum requests, balance buffers, winning-day tests and review timing can reduce the cash received further.
The reliable approach is to calculate each constraint separately and use the smallest permitted amount.
The four numbers traders confuse
| Term | Question it answers |
|---|---|
| Account profit | How much the account has gained under the firm's calculation |
| Requestable profit | How much can be withdrawn without violating the balance rules |
| Payout cap | The maximum request for the applicable window or stage |
| Profit share | The portion of the approved amount assigned to the trader |
A headline such as “90% profit split” does not say that 90% of all displayed profit can be withdrawn immediately.
A general calculation framework
Start with four inputs:
- current balance;
- required post-request balance or safety buffer;
- payout cap for the current cycle;
- trader profit-share percentage.
An illustrative framework is:
Available above buffer = current balance − required retained balance
Gross request limit = smaller of available above buffer and payout cap
Estimated trader amount = gross request limit × trader share
This is not a universal contract formula. Some firms display the trader's net amount directly, while others describe caps before or after a split. Always match the order used by the firm's policy.
Worked example
Assume a hypothetical account has:
- $6,000 of displayed profit;
- $1,500 that the trader intends to retain as a cushion;
- a $3,000 cycle cap;
- a 90% trader share.
The amount above the chosen cushion is $4,500. The $3,000 cap is lower, so the illustrative gross request is $3,000. At a 90% share, the estimated trader portion would be $2,700.
The trader does not receive $5,400 merely because 90% of $6,000 is $5,400. The cap becomes the controlling constraint.
Minimums can delay a request
A minimum request sets a floor. If the amount available above the required balance is below that floor, the dashboard may not permit a withdrawal even when the account is profitable.
Alpha Futures, for example, publishes plan-specific minimums and maximums in its official Payout Policy. Those values should be read for the exact plan rather than treated as universal prop-industry standards.
The Trading Pit's Prime CFD Reward Policy illustrates another structure: a minimum request can sit alongside consistency and date-based conditions.
Balance after payout matters
A withdrawal can change the economic safety of an account even if the firm's formal drawdown threshold does not move in the same way. The remaining distance between balance and loss boundary is the post-payout cushion.
Before requesting, calculate:
Post-payout cushion = projected balance after request − applicable loss threshold
Then compare that cushion with normal daily risk. If a trader usually risks $300 per session and retains only a $300 cushion, one ordinary losing session could threaten the account.
A stronger plan sets a minimum number of losing sessions the account should be able to absorb after a request.
Timing rules add another constraint
A trader may meet the monetary requirements but still need to wait for:
- a minimum count of winning or trading days;
- a specific reward cycle;
- a consistency percentage to fall within range;
- account review;
- identity or payment checks.
“Request available” and “money delivered” are separate milestones. Personal cash-flow planning should use the later, uncertain delivery date rather than the earliest dashboard date.
Compare offers using effective cash access
When comparing prop accounts, do not rank them by profit share alone. Record:
- share percentage;
- first and later payout caps;
- minimum request;
- required buffer or threshold behavior;
- winning-day and consistency requirements;
- request frequency;
- post-request drawdown treatment.
A lower advertised split with a larger practical request or simpler timing can sometimes produce more accessible cash for a specific trading pattern. The reverse can also be true.
Our profit target-to-drawdown ratio guide helps compare the evaluation stage. The post-payout cushion calculator focuses on the risk remaining after a withdrawal.
Pre-request checklist
Verify policy inputs
- Open the current official payout page.
- Match the plan, account size and account stage.
- Confirm whether the displayed cap is gross or net of the split.
- Check minimums, dates and winning-day conditions.
- Review the loss threshold after payout.
Run the numbers
- Calculate profit available above the required balance.
- Apply the cap using the firm's stated order.
- Apply the share using the firm's stated order.
- Estimate payment fees only when the provider discloses them.
- Leave a personal trading cushion.
Save evidence
Keep the policy version, dashboard screenshot and request confirmation. This makes it easier to resolve a mismatch without relying on memory.
Bottom line
Profit share is only one step in a payout calculation. Caps, minimums, buffers and timing conditions can all control the real withdrawal. Build the estimate from the firm's current policy, use the smallest applicable limit and protect enough post-payout cushion for the trading strategy.
FAQ
Frequently Asked Questions
No. Profit share determines how an approved reward is divided, while caps, minimums, buffers and timing rules can limit the amount that may be requested.
Yes. A request cap or required balance buffer may reduce the approved gross reward before the split is applied.
Use the firm's current policy and dashboard because firms define gross request and trader share differently. Do not assume one universal calculation order.
A buffer leaves room between the remaining balance and the loss threshold, reducing the chance that ordinary volatility causes a breach after withdrawal.