Settlements
The canonical finality boundary for affiliate rewards: how qualified attributed events move from pending state into settled value, when adjustments remain possible, and when balance may become eligible for withdrawal.
Overview
Settlements define when affiliate reward leaves the provisional zone and becomes economically recognized under the PVERSE Affiliate Program. This page exists because attribution alone is not enough. A partner may have traffic, a valid code, and even a commission calculation, yet still have no settled value if the underlying event never reaches finality.
The settlement model protects the program from premature payout logic. It creates a clean distinction between candidate reward, pending reward, settled reward, and later withdrawal eligibility. This keeps referral activity, downstream transaction state, and payout validity aligned to the same system reality.
Scope
This page defines the settlement layer of the affiliate system rather than the full partner lifecycle.
- The role of settlement as the finality boundary for commission.
- How attributed eligible events move from pending into settled state.
- How reversals, expiry, invalidation, or review may block settlement.
- The distinction between settled reward and withdrawable reward.
Core Model
PVERSE treats settlement as a stateful economic confirmation rather than a cosmetic label. An attributed qualifying event may create provisional commission, but only settlement converts that provisional amount into settled balance inside the affiliate ledger.
- Event-dependent: settlement depends on the underlying economic event reaching valid finality under current program rules.
- State-dependent: pending, settled, adjusted, reversed, and withdrawn balances are separate states with separate meaning.
- Review-compatible: settlement may still interact with operational review and anti-abuse posture before becoming withdrawable.
- Forward-consistent: historical settlement records should remain auditable even when later adjustments occur.
Operational Behavior
In normal operation, an attributed downstream event enters the system as commission-relevant only after it satisfies qualification rules. At that point, a provisional reward amount may be recorded in pending state. Pending state means the system recognizes a possible partner entitlement, but has not yet accepted that entitlement as finally valid.
Once the underlying event reaches settlement, the corresponding pending commission may transition into settled balance. That state indicates economic finality under the affiliate model, but not necessarily immediate payout. Subsequent review, minimum threshold logic, payout scheduling, or anti-abuse holds may still affect whether and when the balance becomes withdrawable. Expired, reversed, invalid, underqualified, or abusive activity may prevent transition to settled state or may produce later negative adjustments.
Constraints
- Attribution alone does not create settled reward.
- Pending commission is not the same as settled commission.
- Settled balance is not automatically identical to immediately withdrawable balance.
- This page does not define the exact withdrawal thresholds, payout assets, or full abuse-detection methodology.
Integrity Considerations
Settlement is where the affiliate system becomes economically serious. Without a strong settlement boundary, referral programs drift into emotional accounting where traffic feels like money before the system has verified anything durable. PVERSE keeps settlement separate so rewards remain auditable, reversible when necessary, and resistant to premature payout logic.
- Finality clarity: settlement marks economic validity, not mere attribution visibility.
- Ledger clarity: pending, settled, adjusted, and withdrawn states must remain distinct for auditability.
- Boundary clarity: settlement is downstream from qualification and upstream from withdrawal.
Future Expansion
As the affiliate system matures, settlements may expand into more granular state reporting, longer audit windows, richer adjustment records, and campaign-specific finality logic. Any expansion should preserve the same core discipline: attributed activity becomes provisionally rewardable first, reaches settlement second, and only then may become eligible for withdrawal under bounded policy.
Summary
- Settlement is the finality boundary that turns provisional reward into economically recognized reward.
- Pending, settled, adjusted, and withdrawn balances are distinct states with different meaning.
- Invalid, reversed, expired, or abusive events may stop reward before or after provisional recording.
- Withdrawal eligibility remains downstream from settlement, not equivalent to it.