Creator Program
A revenue system built like accounting, not like points.
WinkMe records creator and referral earnings in Diamond, settles them through maturity windows, and gates withdrawals with ledger-backed controls.
1 Diamond = 1 USDT
Fixed V1 settlement unit, not a floating reward score.
100 Credit = 1 Diamond
Credit conversion uses a fixed settlement rate for booked events.
3 wallet buckets
Pending, available, and frozen balances are separated.
Refund-aware
Reversals claw back the original earning amount instead of recalculating.
Fixed settlement model
Diamond is the settlement unit in V1. The platform fixes 1 Diamond = 1 USDT and 100 Credit = 1 Diamond.
Maturity before withdrawal
Creator earnings mature after 7 days. Referral earnings mature after 14 days before they become withdrawable.
Truncate to 6 decimals
All Diamond, USDT, fee, and net payout calculations are truncated down to 6 decimal places before booking.
Refund-safe accounting
Refunds and chargebacks reverse the original earning amount and can place the wallet into withdraw-hold when needed.
Settlement flow
Revenue moves through explicit states before it can ever be withdrawn.
1
A paid event or unlock completes successfully.
2
The platform records pending revenue into the Diamond ledger.
3
After the maturity window, pending revenue becomes available.
4
A withdrawal request moves available funds into frozen.
5
Completion removes frozen funds from the wallet; failure releases them back.
What creators and inviters should expect
The program uses a conservative payout model to reduce rework and financial drift.
Creator earnings
7 days
Gift and paid unlock revenue enters pending first, then becomes available after the creator maturity window.
Referral earnings
14 days
Subscription and credit-pack referral revenue settles more slowly to cover refund and abuse windows.
Withdrawal fees
rate + fixed
Each payout preview shows both the percentage fee and the fixed network fee before submission.
Precision
truncate(6)
Amounts are always truncated down to 6 decimals before they hit the ledger or payout preview.
Invite binding rules
Invite links are for first-account binding only and are validated server-side.
`/r/[code]` stores the invite code locally and passes it into first registration or first OAuth signup.
Existing accounts are not rebound later, and invite bindings are isolated by app.
Self-invites are rejected, and referral earnings can still reverse if the underlying payment is refunded.
Safeguards
These controls are designed to keep balances auditable and withdrawals defensible.
Every earning event uses a stable biz key for idempotency.
Wallet balances are ledger-driven rather than edited directly.
Self-invites and self-reward creator actions are blocked.
Negative available balance after reversal enables withdraw hold.