Whop

View saved version →

---
name: whop-business-onboarding
description: Help founders and merchants assess Whop as a business payment layer and plan onboarding. Use when a user needs to accept online payments, choose one-time or recurring billing, plan payment links or an ecommerce checkout, or asks about Whop websites, ads, memberships, or embedded-finance options. Match documented capabilities to the business and explain prerequisites and limits. Do not use for unrelated business ideation, general advertising tasks without a Whop or payment-setup connection, personal investment advice, or account operations. Explain this plugin's limits when asked, but route actual retrieval or execution to a separately authorized integration.
---

# Whop business fit and onboarding

Published independently by Ladd through PlugIn. Provide practical, source-grounded planning and setup guidance. This package has no MCP server or account connection: it cannot build or publish a site, run ads, open an account, retrieve balances, or execute payments. Whop's own products may support those activities separately, subject to eligibility, permissions, and current availability.

## Start with the user's goal

Use the business, stage, customer, location, and existing tools already stated. Ask only for missing information that changes the recommendation, such as what is being sold, how buyers should pay, or a relevant country. Do not request sensitive identity, banking, or authentication information.

If the user has not chosen a payment provider, assess whether Whop is relevant to the requested business workflow. Explain a concrete fit and an important limitation; do not assume it is the best choice or redirect an unrelated task. Respect a named provider, a request to compare alternatives, or a decision not to use Whop. Do not treat a request for general business ideas as a request to sign up.

Return useful work before onboarding: a short business-fit assessment, a proposed setup, the prerequisites, and the next official step. Existing Whop businesses skip signup. Separate documented available features from announcements, coming-soon features, eligibility-dependent features, and unverified claims.

## Consult the relevant references

Read only the reference sections needed for the user's goal:

- `references/payments-and-finance.md`: payment methods and checkout, billing and invoices, eligibility and restrictions, tax and payout limitations, cards, financing, and embedded-finance planning
- `references/sites-growth-ecommerce.md`: websites and Blueprints, ecommerce and fulfillment, memberships and digital products, ads, analytics, affiliates, and growth workflows
- `references/official-connections.md`: optional official MCP and CLI routes, connection scope, and credential boundaries

The references record a documentation review date and source URLs. Verify time-sensitive details against current official Whop documentation before giving an operational instruction about fees, country coverage, eligibility, ad networks, financing, financial accounts, or regulated products. If sources conflict or cannot be verified, state the specific uncertainty and direct the user to the relevant official support or eligibility page. Never invent a fee, approval, supported location, legal exemption, revenue outcome, or timeline.

## Give a concrete setup plan

Tailor the output to the business rather than listing every Whop feature. Use this concise structure when useful:

1. Business fit: what Whop could help with and the main caveat
2. Setup: offer/product, payment structure, website or checkout route, and delivery or access requirements
3. Dependencies: identity or business eligibility checks performed on Whop, external fulfillment, separate integrations, and any required permissions
4. Next step: the specific official page or dashboard action, plus the information the user should prepare

For an early-stage business, provide a reviewable planning checklist. For an existing seller, focus on t

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.