Skip to content
GenCreatorCheckout map

Checkout should open a delivery packet, not a dead-end receipt.

This is the revenue control room: provider status, product ID env keys, success redirect targets, delivery artifacts, analytics events, and launch blockers for every GenCreator offer.

Selected checkout contract

Creator Vault Kit

Whop
statusneeds provider product
buy resolver/products/buy?product=creator-vault-kit
success route/products/checkout/success?product=creator-vault-kit
fulfillment api/api/products/fulfillment?product=creator-vault-kit
analytics eventcheckout_intent_creator_vault_kit
product id envWHOP_PRODUCT_ID_CREATOR_VAULT_KIT
checkout url envNEXT_PUBLIC_WHOP_CHECKOUT_CREATOR_VAULT_KIT_URL

Product checkout contracts

Every product needs a payment event, success route, and delivery artifact.

The route does not pretend checkout is live. It names exactly what is missing so Whop, Stripe, delivery email, and analytics can be wired without ambiguity.

plannedWhop

GenCreator.community

Enter with one artifact, one question, one weekly proof loop, and the room state that routes pricing, offers, and Studio.

success

/products/checkout/success?product=gencreator-community

buyer receives

  • Community OS packet
  • Weekly proof loop
  • Source pulse ritual
  • Review thread entry

Selected fulfillment path

Buyers should know what happens after payment.

The success route can be used as the redirect target for Whop products later. Until provider products exist, it stays an honest preview of delivery.

Step 1Confirm Whop payment event
Step 2Send fulfillment email from the product contract
Step 3Open starter packet
Step 4Invite upgrade path into community review

entitlement: creator_vault_kit

Join waitlist

Create the voice, offer, audience, proof, and approval memory layer before any assistant drafts.

Self-serve setup, product updates, and community review path. No private implementation support.