Internal System · Live Workflow

Referral Codes, QR Brochures & Partner Attribution

The referral infrastructure behind Knight Logics partner program — QR brochure links, partner codes, Neon Postgres event logging, dashboard visibility, and Stripe webhook payouts.

Referral codes QR brochures Neon Postgres Stripe webhooks
/ref/:partnerTracked paths
NeonPostgres events
StripeWebhook payouts

Referral network walkthrough & proof

Dashboard walkthrough plus the attribution UI and Command embed partners and operators actually use.

Referral payout tracking dashboard with partner attribution
Partner attribution dashboard with earned vs paid visibility.
Knight Command ADMIN Command Center with live Referral, Outreach, Email, and Social status
Referrals tab inside Knight Command — no orphan dashboard URLs.
Trade network
Trade network fitBuilt to scale local partner onboarding with clear credit.
OutreachEngine CRM queue with brand switcher and send caps
Consult captureForm submits keep referral context into Neon events.
Referral code applied at checkout — tied to the /ref/:partner attribution path

Partner attribution /ref/:partner → payout

QR brochures, Neon event logging, and Stripe webhook settlement

Referral network infrastructure deploys unique partner entry paths, tracked consult forms, and partner dashboards — so credit disputes stop living in spreadsheets.

  • /ref/:partner landing paths with QR brochure assets
  • Neon Postgres event store for scans, forms, and conversions
  • Embeds on port 5050 inside Knight Command Referrals tab

Partner attribution with payout visibility

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.

Case study breakdown

Supports Referral Network Systems and the public Referral Program.

Problem

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.

  • No unique landing path per partner
  • Form submits dropped referral context
  • Payout status opaque to partners
  • Scaling local trade network without trust

What was built

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.

  • Event log for scans, forms, and conversions
  • Partner dashboard without owner-only data leaks
  • Webhook settlement for earned referral fees

Tools used

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.

  • QR assets for print brochures
  • Attribution windows defined in program terms
  • API integration for payment status sync

Early signal

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.

  • Dispute reduction on referral credit
  • Faster partner onboarding with codes
  • Data-backed network expansion decisions

Tools & stack

Neon Postgres Stripe webhooks Custom dashboard /ref routing QR generation

Workflow snapshot

A clear path from intake to launch — scoped to what your team will actually use.

1

Program terms

Define fees, attribution windows, and partner onboarding.

2

Paths & QR

Deploy /ref/:partner routes and brochure assets.

3

Neon events

Log scans, forms, and conversion events.

4

Stripe payouts

Webhook settlement and partner dashboard visibility.

Typical deliverables

What ships when we scope Referral Network System for your trade, territory, and operator workflow.

Attribution paths

  • /ref/:partner landing routes
  • QR brochure generation
  • Consult form referral context capture
  • Neon Postgres event store

Partner dashboard

  • referral-dashboard earned vs paid view
  • Attribution window per program terms
  • Partner onboarding with unique codes
  • Data boundaries for partner privacy

Settlement

  • Stripe webhook payout sync
  • api-integration-services receivers
  • Knight Command Referrals embed
  • referral-network-systems program alignment

Outcomes we design for

Results Referral Network System is designed to produce for owners who review queues weekly — not vanity dashboards.

Dispute reduction

Partners verify earned vs paid without owner email chains.

Faster onboarding

Codes and QR assets deploy in days.

Network intelligence

Owners see which partners and QR campaigns produce consults.

Embedded support

Referral ops inside /admin — not orphan dashboard URLs.

Partner program

referral-network-systems flagship proof

Live workflow behind public Referral Program and partner onboarding.

  • referral-program public join path
  • case-study-knight-command Referrals tab
  • api-integration-services for webhooks
  • business-growth-systems full stack context

Common questions

Is this the same as the public Referral Program page?

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.

Can partners see what they earned?

Yes. referral-dashboard gives partners earned vs paid visibility within program data boundaries so disputes do not live in email threads.

Do you support print QR brochures?

Yes. QR brochure assets and /ref/:partner routes are part of the attribution path so print and digital share the same event log.

Can this run for my company brand, not just Knight Logics?

Yes. We scope partner codes, attribution windows, and payout rules to your program — then wire Stripe webhooks and a partner-facing dashboard.

Are payouts automatic once a referral converts?

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.

Related proof & examples

Examples that belong to Referral Network System. Primary proof first; secondary only when it shares the same system pattern.

Want a similar system?

We can build referral tracking for your company or local trade partner network with QR paths and payout visibility.

Book a Free Consultation