MyFundedPerps Lifetime Payout Cap + Coupon Code AUDIT

MyFundedPerps' dedicated payout documentation now states a $100,000 lifetime limit on the net amount received across every account and model. Buying another challenge or resetting an account does not restart that limit. Some other official pages still say there is no lifetime cap, so obtain an account-specific written answer before planning around unlimited withdrawals.

Checked: 9 October 2026. Verified code: AUDIT, 30% off eligible base challenge fees. Coupon Verified on 12 October 2026.

Read the lifetime limit separately from allocation

The dedicated payout documentation describes a single user-level ceiling covering Select, Prime, Signature and Elite. It counts the payout received after the profit split. The gross account deduction is a different number, and active funded allocation measures something else again. The PFA allocation guide covers that separate account-capacity calculation.

A useful personal record therefore has three separate totals: nominal active accounts, gross profit deducted for approved payouts, and cumulative net payouts received. Combining them in one column makes it difficult to answer even a basic question about remaining lifetime room.

For example, holding $100,000 of nominal account capacity does not itself mean $100,000 has been paid to you. Conversely, closing an account does not erase money previously received. Keep closed accounts in the payout history even when they no longer appear among active trading accounts.

The public wording still conflicts

The main FAQ has a dedicated lifetime-cap answer matching the $100,000 net, per-user limit. Its general payout-eligibility answer still describes Select, Prime and Signature as having no lifetime cap. The September payout guide also retains uncapped wording.

This guide gives priority to the specific current payout-documentation section for the working interpretation, while leaving the inconsistency visible. It does not claim that support has confirmed how every older purchase is treated. Save the terms issued for your account and ask whether any purchase-date exception exists, rather than assuming one.

Build a ledger that survives account changes

Use one row per completed payment, with account identifier, model, decision date, payment date, gross deduction, split, net received and delivery method. Keep requested and pending amounts separate from completed receipts. A submitted request has not necessarily become a received payout.

The following is an invented arithmetic example, not a trader's result or a forecast:

Using the stated net-cap interpretation, the arithmetic remainder is $100,000 minus $8,300, or $91,700. That is a recordkeeping figure, not approved payout eligibility. The account must still satisfy its own request conditions and review.

For store credit, mixed payments, credit boosts or a reversed transfer, ask how the firm's lifetime counter records the event. Do not silently classify a credit balance as cash received or subtract a reversed payment without confirmation. Reconcile the ledger with the account's displayed history and any written support response.

A near-cap request needs a different check

Suppose a hypothetical trader's confirmed lifetime receipts total $99,200. The simple remaining amount is $800. At an 80% share, an $800 net request corresponds to $1,000 gross; at a 90% share it corresponds to about $888.89 before the platform's cent handling.

The example demonstrates why the requested share and account deduction need different columns. It does not establish whether the platform automatically trims a larger request, rejects it or imposes another step near the ceiling. Read the actual request preview and obtain clarification rather than experimenting with repeated submissions.

Also check whether pending requests from another account affect the amount the form currently permits. Multiple accounts should be reconciled together before treating an unprocessed payment as additional lifetime capacity.

Rejected requests have a separate documentation conflict

The dedicated payout documentation says a rejection restores that day's allowance once other eligibility conditions are satisfied. The main FAQ and September blog still say a rejection consumes the day. This conflict concerns request timing, not the lifetime total.

Use the current account panel and ask support to resolve a disagreement. A restored request window does not prove that a rejected claim has become payable. Keep the rejection reason and updated eligibility status with the request record. For the distinct gross-deduction and retained-buffer issue, read the first-payout buffer guide.

Entry fees with AUDIT

These standard-share examples use regular USD fees from the official pricing matrix. The calculations apply the site's verified AUDIT offer once; they do not reuse that older article's September promotional rate.

Final base fee equals regular fee multiplied by 0.70, conditional on acceptance for the selected order. The optional 90/10 upgrade, payment charges and tax need separate checks. Elite prices and code coverage are not established by these rows. No fixed code expiry is asserted.

Choose the exact challenge on the official website, review the applicable payout terms, enter AUDIT before payment and verify the full order summary. The FAQ says an eligible code replaces an automatic offer rather than stacking with it. A cheaper new account does not create fresh lifetime payout capacity under the dedicated documentation.

Read the current PFA coupon terms and MyFundedPerps review for broader coverage, while checking the specific current payout sources above for this conflict.

Affiliate disclosure: PFA may receive commission from qualifying referrals or code use. This is document-based educational analysis. Accounts are simulated, fees can be lost, and neither a coupon nor an arithmetic ledger guarantees approval or payment.