Draft: feat: auto-provision enterprise keys from Whop subscriptions - #40
Draft
sleeyax wants to merge 1 commit into
Draft
Draft: feat: auto-provision enterprise keys from Whop subscriptions#40sleeyax wants to merge 1 commit into
sleeyax wants to merge 1 commit into
Conversation
Whop membership.activated/deactivated webhooks now create and revoke enterprise keys, replacing the manual SQL workflow for individual subscribers. We reuse the license key Whop issues per membership (storing only its hash) so the customer reads it from their Whop dashboard, and gate access on a whop_plans product allowlist.
sleeyax
marked this pull request as draft
June 14, 2026 13:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Needs QA testing
Whop membership.activated/deactivated webhooks now create and revoke enterprise keys, replacing the manual SQL workflow for individual subscribers. We reuse the license key Whop issues per membership (storing only its hash) so the customer reads it from their Whop dashboard, and gate access on a whop_plans product allowlist.