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

Brand Social System

none
statusno payment required
buy resolver/brand/social
success route/brand/social
fulfillment api/api/products/fulfillment?product=brand-social-system
analytics eventbrand_social_system_opened
product id envnot required
checkout url envnot required

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 1Open the Brand Social System
Step 2Choose a platform format
Step 3Generate or review the brand-social packet
Step 4Create the asset
Step 5Route into offers, campaigns, community, or Studio after proof exists