Viktor Rewards — Referral Program Breakdown

In-app referral ladder (app.viktor.com/rewards, live since Jun 25) overlaid with the Dub affiliate double-pay analysis. Snapshot: · prod DB (read-only) + Dub commission ledger.

Who covers what

Our in-app referral program (credits · prod DB)

Attribution: customer signs up through a user's referral link → referral record on our side → monthly job grants lifetime credits (15–30% of every payment incl. top-ups).

Referrers
232
671 referred teams · 356 paying (53%)
Referred MRR
$109,450
live subs
June credits paid
2,812,566
≈$7,031 retail
July accruing
$51,114 rev
≈3.76M credits (est.)

Dub affiliate program (cash · Dub ledger)

Attribution: customer clicks a partner's Dub link → click-ID cookie → Dub pays the partner cash (15–20% rev-share, 12 months, 0-day hold).

Earning partners
104
of the partner program
Earning customers
508
with ≥1 commission
Commissions to date
$85,479
2,100 commission rows
Attributed sales
$514,797
all-time volume

⚠️ The overlap — the only place the two systems touch

Of 671 referred teams and 508 Dub-earning customers, 38 customers are confirmed paying out on both sides ($8,785 Dub cash all-time, table below with June cash and credits per case) and more referred teams carry a Dub click-ID but no cash commission yet. Everything else is cleanly covered by exactly one program.

How the tiers work

Tier = referred revenue in the current calendar month (resets on the 1st). Hit a threshold, and that month's rate applies to all referred revenue that month, paid as credits in the month-end batch ($0.0025/credit retail).

June tier distribution

Referrers

Referrer June
tier
July tier
(MTD)
Proj. July tier
(renewals)
To next tier
(July)
June credits
(paid)
July referred
rev (MTD)
July credits
(est.)
Referred /
paying (%)
Referred
MRR
Dub

⚠️ Dub affiliate overlap — the double-pay gap

The two programs don't dedupe. The same customer can carry a Dub click-ID (cash commission to a Dub partner, 15–20% for 12 months) and an in-app referral attribution (lifetime credits to a referrer, 15–30% of every payment incl. top-ups). Confirmed so far: customers paying out on both — cash + credits, with more July credits accruing toward the month-end batch. In most cases the in-app referrer is the same person as the Dub partner — they collect cash and credits on the same customer. A further 37 referred teams carry a Dub click-ID but no cash commission yet (cookie-only; they become double-pay the moment they convert through the link).

CustomerDub partner (cash)Dub cash (total)Dub cash (June)In-app referrer (credits)Credits (total)Credits (June)

How to bridge it (credits-first)

1) One customer = one attribution — credits win. Company preference is to pay in credits, so on overlapping customers the in-app referral keeps paying and the Dub commission stops: cancel future commissions on those 16 customers in Dub and notify the partner. Caveat: Dub terms are a contractual 12-month cash promise, so this needs partner consent or a grandfather cutoff date, not a silent switch-off. 2) One identity = one program. Where the Dub partner and the in-app referrer are the same person (11 of 16), move them fully onto the in-app program going forward and wind down their Dub link. 3) Dedupe at signup. When a new team arrives with both a referral record and a Dub click-ID, resolve once — referral record wins — so Dub never books the commission at all. 4) Add a holding period on remaining Dub groups (currently 0-day; peers 30–60d).

Tier = current-calendar-month referred revenue (resets monthly): Connector $0 · Advocate $750 · Insider $2.5k · Ambassador $7.5k · Luminary $30k · Legend $75k → 15/20/25/30/30/30% paid in credits ($0.0025/credit). "June credits (paid)" = the processed June batch. July figures accrue and pay at month-end; July credit estimate = July referred revenue × current-tier rate ÷ $0.0025. Referred MRR = active Stripe subscriptions of referred teams, normalized monthly. Dub flags from commission-ledger triangulation (Jul 7).