Affiliate payouts

Prepare payout runs with locks, evidence and deliberate approval.

Draft eligible commission sets, surface exclusions and keep payout execution separated from attribution intake and programme configuration.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Immutable draftsApproval locksExplicit exclusions

Built for operating reality

Clear contracts at every boundary.

01

Review before approval

A draft records the exact eligible commission set and explains exclusions before money is locked for settlement.

02

Fence concurrent changes

Approval conditions the draft, commission and payout-account versions so stale decisions fail closed.

03

Keep settlement resumable

Controller state and operation sentinels make retries observable instead of turning them into duplicate sends.

Controlled lifecycle

Separate drafting, approval and external settlement.

Each stage has its own authority and evidence. A run can be inspected before approval, and external payout execution never shares a browser credential with programme configuration.

Launch control

Publish payout claims only after operational review.

This page remains noindex until the supported payout rail, commercial claims and legal copy have completed owner review.

Questions, answered

Know where the boundaries are before you integrate.

Why is a payout draft immutable?

Approval must apply to the exact reviewed commission set. Changes create a new draft version rather than silently changing that decision.

Can a browser credential send a payout?

No. Payout approval and execution belong to protected operator and worker authority boundaries.

Is this capability publicly launched?

The page remains excluded from search until payout operations, commercial claims and legal copy complete their external launch gates.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access