The referral infrastructure behind Knight Logics partner program — QR brochure links, partner codes, Neon Postgres event logging, dashboard visibility, and Stripe webhook payouts.
Dashboard walkthrough plus the attribution UI and Command embed partners and operators actually use.
Partner attribution /ref/:partner → payout
Referral network infrastructure deploys unique partner entry paths, tracked consult forms, and partner dashboards — so credit disputes stop living in spreadsheets.
Referral network infrastructure deploys /ref/:partner entry paths, QR brochure assets, Neon Postgres event logging, referral-dashboard partner views, and Stripe webhook payout settlement.
Partners previously disputed credit when payout status lived in spreadsheets. Dashboard self-service reduced email disputes and accelerated Tampa Bay trade network onboarding.
Knight Command Referrals tab embeds referral ops on port 5050 family alongside CRM and email — single operator shell for partner support.
If you want partners to trust the program — and you want to know which QR codes actually produce consults — this is the live attribution and payout stack.
Referral networks scale when attribution is automatic — partners see leads and payouts without spreadsheet arguments.
Before this system existed, "who gets credit" was a recurring source of friction with our earliest trade partners. A handshake introduction and a QR scan looked identical in generic web analytics, so payout conversations relied on memory and trust rather than a record either side could check.
The dashboard did not remove the need for manual review before a payout — it removed the need to argue about whether a referral happened in the first place. Partners can check status themselves; admins still approve before money moves.
Supports Referral Network Systems and the public Referral Program.
Partner referrals were hard to attribute fairly. Brochure QR scans and word-of-mouth consults looked identical in generic analytics. Payout earned vs paid lived in spreadsheets and partner disputes slowed network growth.
Referral network with /ref/:partner entry paths, QR brochure assets, tracked consult forms, Neon Postgres event store, /referral-dashboard for partner visibility, and Stripe webhook-driven payout status. Embeds on port 5050 family inside Knight Command Referrals tab.
Custom referral dashboard, Neon Postgres, Stripe webhooks, tracked landing paths, and Knight Command embed. Documented in referral-network-systems flagship and api-integration-services lanes.
Cleaner partner attribution before scaling Tampa Bay trade network experiments. Partners self-serve status checks instead of email disputes. Owners see which QR campaigns and codes produce consults.
A clear path from intake to launch — scoped to what your team will actually use.
Define fees, attribution windows, and partner onboarding.
Deploy /ref/:partner routes and brochure assets.
Log scans, forms, and conversion events.
Webhook settlement and partner dashboard visibility.
What ships when we scope Referral Network System for your trade, territory, and operator workflow.
Results Referral Network System is designed to produce for owners who review queues weekly — not vanity dashboards.
Partners verify earned vs paid without owner email chains.
Codes and QR assets deploy in days.
Owners see which partners and QR campaigns produce consults.
Referral ops inside /admin — not orphan dashboard URLs.
Live workflow behind public Referral Program and partner onboarding.
The public Referral Program is the join path and terms. This case study documents the production infrastructure — codes, QR, Neon events, dashboard, and Stripe payout sync — behind that program.
Yes. referral-dashboard gives partners earned vs paid visibility within program data boundaries so disputes do not live in email threads.
Yes. QR brochure assets and /ref/:partner routes are part of the attribution path so print and digital share the same event log.
Yes. We scope partner codes, attribution windows, and payout rules to your program — then wire Stripe webhooks and a partner-facing dashboard.
No, by design. Stripe webhooks update payment status automatically, but a person still reviews each referral before an invoice or transfer goes out — that manual checkpoint is what keeps the program trustworthy at small scale.
Examples that belong to Referral Network System. Primary proof first; secondary only when it shares the same system pattern.
We can build referral tracking for your company or local trade partner network with QR paths and payout visibility.
Book a Free Consultation