AI Employee Bootcamp: payments move to Whop

Action & questions

Everything unresolved, in one place. Cart opens Monday 17 Aug; only the organic funnel has to be live for it.

The flow

One Worker sits between Whop and everything downstream. It knows what was bought at the moment of the charge, so nothing after it has to guess.

Plans

Twelve live plans, all hidden from the storefront — reachable only through a checkout page. A price that steps on 20 Sep needs two plans, because a Whop plan carries one price.

VIP → Platinum, decided

Lex, 14 Aug: "VIP $197 → Platinum $397 = +$200. Once VIP increases to $297 (Sept 20) → Platinum $397 = +$100. For now, $200 increase is what it needed."

So the upgrade is priced off whatever VIP costs on the day. The $200 rung is live; the $100 rung gets built before 20 Sep. One consequence worth naming rather than discovering: a buyer who paid $197 for VIP in August and upgrades on 21 September pays $100 for a $200 gap. That is the accepted trade-off of pricing by date instead of by what they paid, and it keeps the offer simple to explain.

Every plan carries its own identifiers in Whop metadata — plan_key, offer, tier, is_upgrade, upgraded_from — so a payment can be traced back to exactly which rung was sold without a lookup table.

Affiliates

Sales reach FirstPromoter directly from the Worker. Eight GHL workflows are gone.

Capture

• FirstPromoter's tracking script is in the funnel head code and sets _fprom_tid / _fprom_ref on go.theuncommonbusiness.co.
• The checkout block reads those cookies at load and sends them with the payment, so they arrive as Whop payment metadata and are reported with the sale.
• Cookies first, ?fpr= as fallback: the parameter only exists on the landing hop and is gone by the time most buyers reach checkout.
• Same origin throughout, so the read works — provided FirstPromoter does not set those cookies HttpOnly. Nothing can read an HttpOnly cookie from a page script. The live payment test is what proves this end to end, and it is the single most important thing that test checks.

What the eight workflows did

• Clear a field → write {{order.total_price}} → ×100 → POST the sale.
• The first three steps existed only because GHL cannot multiply inline. The Worker holds cents already.
• {{order.total_price}} does not exist without a GHL order, so those workflows are dead, not redundant.

Your side  Tracking is on every funnel already and carries to checkout. Outstanding: add the bootcamp link to the promoter signup, so promoters have one to share.

Attribution

Organic, ads and tripwire are one attribute on the page. No logic to build.

• Each block declares data-funnel="organic" | "ads" | "tripwire". It rides the payment; the Worker turns it into a tag.
• New funnel page = copy the block, change data-tier and data-funnel. Nothing else.
• Declared, not inferred, because two bootcamp funnels share one page URL.
• The exact page slug also lands in aieb_page, so GHL conditions can target one ad page without a code change.
• Tripwire is a real third value. GHL only ever wired ads and organic.

GHL changes

Tier workflows stay separate, one per tier. Each loses its payment trigger and its price branching, and keeps everything that speaks to the buyer.

The live set is the folder The AI Employee Bootcamp — WHOP: 1 — General Admission (Early Bird + GA), 2 - VIP, 2a — VIP upgrade, 3 - Platinum, 3a - Platinum upgrade, plus 4 - Bounce Email. All five are published and the Worker enters them by ID. The originals are untouched, kept only so the old build can be read side by side — sending a Whop buyer into one would re-run branches that read a GHL order amount that no longer exists.

One addition per workflow: the n8n webhook's custom data gains whop_payment_id. It replaces ghl_order_id as the dedupe key and is the same value Supabase stores as processor_ref.

Fields & tags

Written to the contact on every purchase, before any workflow runs.

Tags, in order

An upgraded buyer keeps the tag from the tier they started on as well as the one they moved to. Hub gating reads the entitlement; the dashboard reads the trail.

Checkout map

data-tier and data-funnel are the only two things that differ between one checkout and the next.

AI Employee Bootcamp — main funnel

AI Employee Bootcamp Ads — rebuilt 15 Aug, new slugs

Source: live GHL funnel pull, 15 Aug 2026, 15:10 ET.

Two things to watch

Editing the checkout

A checkout page holds two lines. Everything inside the block is served from one place, so a wording or styling change is one edit and one deploy — never twelve pages re-pasted.

What a page contains

Who edits what

Links

Where it runs

Everything is on your own Cloudflare account — Hello@theuncommonbusiness.co, account 81ac8dfc3cfa5c403247c595aef3db16. Nothing is hosted by Whop, so it stays yours at handover.

Dashboard: dash.cloudflare.com. Credentials are shared separately — never on this page.

Deploying a change

Step 1 is not optional. embed.js is generated, so the source file can be valid while the string it produces is not — that took every checkout down silently on 15 Aug, with a blank space where the form should be and nothing in the console.

Supabase

• Scott's n8n endpoint receives the purchase and writes to Postgres directly. Whop points at it; nothing of ours sits between.
• That keeps sales private — reaching it over the API would have meant exposing all 17 tables for one insert.
• Failures land in n8n's execution history with alerting already attached.
• Rows land as processor = 'whop', processor_ref = the Whop payment ID — the same shape as the 25,000 GHL rows, so reporting spans both. Plan ID stored alongside.