Educational worksheet · spottradehub.online · Updated 23 October 2026

Prop Firm Payouts: Trace the Request Through to Receipt

A payout review should identify the event that actually happened. A profit display, an internal wallet transfer, an approved request and a confirmed external receipt represent different states. Keeping them separate makes a payment record useful without treating an early status as a completed transaction.

Explore this site’s existing research resource

Read the product’s sequence and conditions

HashHedge’s payout guide describes a Trader/Wallet workflow, withdrawal requests and later statuses. It also describes a further-request interval measured from a previous completed request. These published descriptions are not proof that an individual account or transfer has satisfied its conditions.

Section 3 of the Commercial Terms describes an eligible Live Account cycle ending on a user-selected payout day between 14 and 60 calendar days from that cycle’s first trade, subject to suspensions and other conditions. Keep this cycle reference separate from the guide’s previous-completion reference. The accepted plan and applicable documents must be checked; an apparent difference needs clarification rather than a promised automatic fortnightly payment.

Build a fictional request timeline

Use separate fictional dates: an earlier request completed on 5 October, the first trade of a new cycle occurred on 8 October, and a payout day was selected for 29 October. That chosen day is 21 days after the new first trade, within the illustrative 14–60-day range. A separate 14-day point after the previous completion would be 19 October; it does not replace the selected cycle day.

A selected day, submitted request, approval and external receipt remain different records. Processing provisions also have validity, completeness, Hold and verification conditions. A general reference to 72 hours should not be presented as an unconditional bank-arrival deadline. The example establishes calendar arithmetic only, not eligibility, a payment entitlement or the outcome of a real request.

Separate fictional references; no actual payout or eligibility established
RecordExample dateMeaning
Previous request completed5 OctoberGuide-style reference for a later-request interval
New cycle first trade8 OctoberSeparate cycle-start reference
User-selected cycle day29 October21 days after the new start; not an automatic fortnightly receipt
Actual request and receiptNot suppliedConditions and operational outcome remain unknown

Keep amounts and reporting currency independent

Retain the amount and currency of each event, any supplied charges and the observed receiving amount. A CAD estimate can help a Canadian journal, but the estimate must not overwrite the original units or the actual credit. The article does not determine a tax treatment or confirm access for Canadian residents.

This site’s existing date ledger distinguishes trade and settlement dates. Extend that discipline to payout records: use the date of the actual event being described, with its timezone where supplied. A date copied from a different stage can create a false delay or a false on-time result.

Use documentation without triggering a transaction

The worksheet needs no wallet address, password, personal document or live withdrawal. Complete it from a fictional example or your own retained records. A payment address and network would require separate checks before any real irreversible transfer.

The optional HashHedge link is for reviewing current programme information. Neither the example nor the affiliate invitation establishes a withdrawal entitlement or a future payment.

Sources and rule dates