Withdrawals

Overview

Withdrawals define how affiliate value exits the internal reward ledger and becomes an external payout. This page exists because final settlement inside the affiliate ledger and actual payout to a partner are not the same thing. A partner may have settled value while still not being eligible to withdraw all or part of that balance under current payout policy.

The withdrawal layer protects the program against premature payout, invalid destination handling, and unresolved review conditions. It creates a distinct boundary between internal reward finality and external payout execution so the program can remain auditable, reversible where necessary, and operationally safe.

Scope

This page defines how payout requests are formed and how settled internal reward can become externally paid reward.

• The distinction between settled balance and withdrawable balance.
• The payout rails, request lifecycle, and review boundary for withdrawal requests.
• The conditions under which requests may be held, rejected, or adjusted.
• The final payout state after approved external transfer.

Core Model

The withdrawal model is built as a state transition from internal ledger ownership to external payout execution. Not every settled amount is immediately withdrawable, and not every submitted request becomes a completed payout without review and payout-path validation.

• Balance-based: only reward that has reached withdrawable status may be requested for payout.
• Request-based: payout begins with an explicit withdrawal request tied to defined payout details.
• Review-based: requests may be checked for threshold, policy, destination, and abuse constraints before approval.
• Execution-based: payout is final only after the external transfer itself reaches completed state.

Operational Behavior

In normal operation, affiliate commission first reaches settled balance through the settlement model. A portion of that settled balance may then become withdrawable once the applicable payout requirements are satisfied. The partner submits a withdrawal request specifying an approved payout destination under the currently supported withdrawal rails.

After submission, the request may enter review. Review checks can include balance sufficiency, minimum threshold compliance, payout-method validity, anti-abuse posture, operational holds, and other bounded policy conditions. Once approved, the request proceeds to payout execution. Only after the external transfer completes should the value be considered paid out and no longer part of the partner’s withdrawable balance. If a request is invalid, held, rejected, or fails execution, the value may remain in internal balance subject to current policy.

Constraints

• Settled balance is not automatically identical to withdrawable balance.
• A submitted request is not automatically an approved payout.
• Approved payout intent is not identical to completed external transfer.
• This page does not hardcode every payout asset, threshold, or processing rule forever; those remain subject to forward-only policy updates.

Integrity Considerations

Withdrawals are where internal accounting becomes externally irreversible, so the withdrawal model must remain narrower and stricter than the balance model. A weak payout system treats all settled value as instantly spendable. A strong payout system adds explicit request, review, and execution boundaries so errors and abuse do not immediately escape into irreversible payout events.

• State clarity: settled, withdrawable, requested, approved, paid, and rejected are separate payout states with separate operational meaning.
• Execution clarity: payout is only final when the external transfer itself succeeds.
• Boundary clarity: withdrawal is downstream from settlement and upstream from irreversible external payout.

Future Expansion

As the affiliate system matures, withdrawals may expand into broader payout assets, richer request history, more granular hold reasons, and stronger payout-status reporting. Any expansion should preserve the same discipline: withdrawable value remains distinct from settled value, external payout remains explicitly request-based, and irreversible transfer remains the final state rather than the starting assumption.

Summary

• Withdrawal is the payout transition from internal reward ledger to external transfer.
• Settled balance, withdrawable balance, submitted request, approved request, and paid-out balance are distinct states.
• Requests may be reviewed, held, rejected, or fail execution under current policy.
• Only completed external transfer should be treated as final payout.