Funded Futures Family Payout Calendar + Discount Code COMPARE

Funded Futures Family's payout-request date is not a qualifying day for the next minimum-day count. Its current payment guide starts that count on the following day, while separately describing end-of-day approval, Rise onboarding and payment delivery. Keep those dates distinct when planning a second payout or estimating when the first one might arrive.

Verified on 12 October 2026.

Coupon summary: COMPARE offers 80% off Velocity, 40% off Premier for the first five uses and 30% later, and 30% off Prime. The offer concerns eligible initial monthly base payments. Yash R. personally verified it on 12 October 2026. Sources and regular fees were checked on 11 October 2026; the coupon terms remain the scope reference.

Start with a dated request record

The official payout-methods guide says trading and profits on the request date remain in the account but do not count toward the next minimum trading-day requirement. It describes approvals at EOD, then Rise onboarding and verification. Its delivery estimates are one to three business days for bank transfer and same day to 24 hours for crypto, with provider-determined fees.

A personal record should therefore have separate fields for submission, approval, provider invitation, onboarding completion and receipt. Record actual statuses rather than filling every field with the date you hope payment will arrive.

This distinction matters even for someone who has requested before. A repeat request may have a different review question or provider status. Treat the previous payment as a useful example of what happened, not as a contractual deadline for every future payment.

A Prime calendar example

Assume a hypothetical Prime trader submits an eligible payout request on Monday. That trader then records a positive session on the same Monday. The money stays part of the account record, but Monday should not be marked as day one of the next minimum-day count under the payment guide.

The Prime payout requirements require at least three trading days between requests, qualifying profit of at least $200 per trading day, the size-specific new-profit requirement, consistency and the retained buffer. The conditions reset after an approved payout.

If Tuesday, Wednesday and Thursday each meet the applicable day qualification, they can be recorded as candidate days one, two and three. This does not promise a Thursday payout. The other conditions and the dashboard must also be satisfied, and a holiday, nonqualifying day or delayed status can change the result.

For example, a Tuesday session of $150 should not be relabeled as a qualifying $200 day just because it is profitable. Likewise, three qualifying days alone do not prove that the account retains enough balance above its required buffer. Keep the day count and the account-level money tests in different fields.

Do not force every counter onto one reset date

The payment policy discusses day counting from after submission, while the plan rule discusses conditions resetting after approval. These statements refer to different parts of the process. If a request and approval fall on different dates, do not automatically assume the profit-cycle ledger and the minimum-day counter share the same starting timestamp.

Record both events and compare the dashboard's counters with the trade history. Where the result is unclear, ask FFF how the intervening activity is assigned. A useful question identifies the account, request reference and exact dates. It does not ask for an exception or assume that a spreadsheet overrides the platform.

A simple worksheet can retain:

Follow the Rise sequence through to completion

The payment guide describes an invitation after the payout-approved email, followed by Rise onboarding and a Funded Futures Family contract. It also describes dispatch after the required provider approval. Do not interpret a completed form as proof that verification is approved or that a bank has credited the funds.

Open the provider invitation through the process linked to the real payout request, and check the registered details carefully. If a message is unexpected, verify it through official support before submitting personal information. Keep identity documents out of ordinary trading spreadsheets; a status such as “verification approved” is usually sufficient for a private checklist.

If the expected invitation is missing, report the specific missing step with the request reference. Repeatedly submitting new payout requests or creating extra provider profiles can make the record more confusing. The relevant next action is to establish the existing request's status through the supported process.

Separate an estimate from usable cash

A bank-transfer estimate expressed in business days should not be turned into an unconditional next-calendar-day promise. The record may also show approval, dispatch and receipt as separate milestones. Keep the payment out of committed spending until it is actually available.

For arithmetic only, if an explicitly confirmed $900 trader payment incurs a separately quoted $15 provider fee, the estimated receipt is $885 before any other disclosed conversion. This is not an FFF fee quotation. Use the actual provider breakdown and do not apply a profit split again to a figure already labeled as the trader's net portion.

Initial Prime fees after COMPARE

The official Prime page lists Included and Max configurations separately. These examples use Included regular monthly fees and the verified 30% initial-payment offer.

Select the exact plan and options, apply COMPARE before paying and inspect both today's charge and the renewal terms. The code's Velocity and Premier rates must not be substituted for Prime. No continuing renewal discount, reset reduction, add-on coverage, stacking or fixed expiry is inferred.

The Prime buffer guide covers the money-side eligibility calculation. Prop Firm Audit may earn affiliate compensation. Accounts in these stages are simulated, fees can be lost and payout approval or receipt is not guaranteed.