Whop features and business tools
Capabilities from official Whop documentation. Open a feature for its practical benefit, conditions, and source.
Checkout links
Create and edit shareable checkout links for free access, one-time payments, or recurring subscriptions.
Send customers directly to a payment page without building one.
Each link connects to a whop. Leave “Show on store page” unchecked to share a link privately. Checkout links are initially capped at $2,500; higher amounts require approval.
Embedded checkout
Accept one-time and recurring payments on your own site with Whop’s Checkout element.
Keep the customer’s payment experience inside your website.
Choose the Checkout element for a complete checkout, payment elements for a custom form, or wallet buttons for eligible devices. Fulfill from payment.succeeded, not a browser redirect.
Flexible products and pricing
Offer free access, one-time purchases, or recurring subscriptions, with multiple billing options, stock limits, and timed access.
Sell different membership tiers and choose which apps each product unlocks.
Recurring products can use weekly, monthly, or yearly billing cycles. Add another billing period to offer multiple pricing options for a product.
Trials, discounts and waitlists
Offer trials, promo codes and approval-based waitlists. Waitlist applicants can answer questions before you review them.
Qualify applicants and control access to a whop without admitting everyone immediately.
People who join through a waitlist checkout link do not receive immediate access. Approved applicants automatically receive access and a notification. Existing trial and discount capabilities are unchanged.
Local payment methods
Shows eligible regional payment methods automatically at checkout, with per-link controls to show or hide methods.
Lets customers use payment options available in their region.
Availability depends on the customer’s IP-based geography, checkout currency, amount, pricing type, merchant settings, and whether the method is enabled for the account. Methods marked ¹ require Whop to enable them. ACH, SEPA Debit, iDEAL, Cash App, and PayPal support one-time payments and recurring subscriptions; other listed local methods support one-time payments only. iDEAL appears only in checkout opened from a Whop store or product page, not on direct checkout links or in embedded checkouts.
Adaptive pricing
Displays eligible one-time checkout prices in the buyer’s local currency and processes payments domestically.
Lets buyers see a familiar currency and access eligible local payment methods; domestic processing avoids international card and currency conversion fees for sellers on those transactions.
Off by default and enabled per checkout link. Buyers can switch to the original currency; buyers in unsupported regions see the original price. Subscriptions continue in the original currency. There is no additional Whop fee to enable it, but the buyer’s displayed local price includes a currency conversion fee.
Financing and BNPL
Offer thirteen documented financing options to eligible buyers through Whop checkout, including Afterpay, Splitit, Klarna, Sezzle and ClarityPay.
Let eligible customers spread a purchase over installments.
Whop must approve the business for financing. Options depend on customer eligibility and provider availability; some require contacting Whop Support to enable them. Settlement differs by provider: Sezzle orders settle on a 15-day basis, and SeQura uses staged payouts.
High-ticket financing
ClarityPay supports eligible US purchases up to $30,000.
Finance higher-priced programs and services for eligible buyers.
Confirm approval, current terms and checkout limits before quoting a buyer.
Invoices and saved payment methods
Create and send one-time invoices or set up recurring invoices that are emailed each period or charged to an authorized saved payment method. Track invoice status, send due-date reminders, and void, download, or export invoices.
Bill customers and keep records of paid and outstanding invoices.
Recurring automatic charges require a saved payment method and customer authorization. Financing requires access approval; crypto requires setup. Unpaid invoices are automatically voided after 120 days. Passing payment processing fees to the customer is optional.
Subscription recovery
Whop emails customers and automatically retries failed subscription payments. Merchants can also retry a failed payment from the dashboard.
Gives customers a way to update their payment method and merchants a way to retry a failed charge.
Automatic retries run for five days; Whop cancels the subscription if payment still fails. Merchants can choose whether members retain access while past due. A successful payment restores access automatically.
Payment orchestration
Optional routing across payment providers.
Route payments through multiple providers without building a routing system.
Paid option; measure the effect on the business’s actual payment mix.
Tap to Pay on iPhone
Accept one-time contactless card and mobile-wallet payments through the Whop iOS app, including optional tips. Point of Sale mode lets you charge from a product list or enter a custom amount.
Take in-person payments into the same Whop balance as online sales without a card reader.
Requires iPhone XS or later, iOS 18 or later, the latest Whop iOS app, internet, and a business address in Australia, Canada, Poland, the UK, or US. Turn on Point of Sale in Settings → Tap to Pay to charge from a product list or custom amount. Tap to Pay cannot start subscriptions; customers can use a checkout link or QR code instead.
Courses
Video lessons, quizzes and progress tracking.
Deliver paid training with lessons and progress tracking.
Delivered through the Courses app.
Chat and forums
Live discussions and threaded conversations.
Include discussion and support in a paid membership.
Use product access to separate free and paid spaces.
Files and content
Digital downloads and rich-media resource pages.
Deliver downloads and member resources with paid access.
App-based delivery.
Bookings and events
Paid/free appointments and live or in-person events.
Sell appointments and tickets alongside other products.
Confirm event-specific requirements in the selected app.
Livestreams and replays
Broadcast to members and retain recordings.
Provide live training and let members watch recordings later.
Configure the community’s Events and livestream experience.
Discord access
Connect a Discord account and enter servers included with a membership.
Sell access to an existing Discord community.
Link Discord in External accounts, authorize Whop Bot, then select Discord in the purchased whop and claim access. On mobile, use the same External accounts page in your browser.
Per-client products and private spaces
Give each client selected chat, files, content, events and booking access.
Keep each client’s payment and delivery space connected.
Set up separate client access deliberately.
App Store extensions
Browse and install apps for a whop by category, or filter by newest, trending, and most addicting.
Find apps that add functions to an existing whop without building them yourself.
App capabilities and pricing vary. Apps can also be configured after installation, as covered by the related Add Apps documentation.
Product affiliate programs
Track referral purchases and automatically pay commissions, with global, member, and custom partner rates.
Reward partners and members for referred sales without handling commission payments manually.
The global rate defaults to 30% and can be changed. A member rate of 0% makes members earn the global rate instead. Custom partner rates can be a percentage or fixed amount on the first payment or recurring payments. Commissions are paid after a 30-day waiting period.
Automatic partner revenue share
Set a partner’s revenue share across all products or override the percentage for individual products. Whop calculates the split after its fees and deposits the partner’s portion into their Whop balance when a transaction completes.
Pay strategic partners their share of each transaction without processing the split manually.
Revenue share splits transactions rather than attributing sales through referral links.
Clipping & Content Rewards
Run clipping or original creator-content campaigns with budgets and view-based rewards.
Pay creators to distribute clips or produce original content.
Approve submissions and configure payment per 1,000 views. Views are not guaranteed sales.
Whop Ads
Run ad campaigns through Whop-owned accounts from the Whop dashboard, with first-party attribution based on payment data and pre-launch checks of ad creative and copy.
Manage campaigns and connect conversions to Whop sales data. Eligible pending Whop balance can fund ad spend before it settles.
You or your media buyer supplies the strategy and creative and runs the campaigns; Whop Ads is not a managed service. Campaigns are managed in Whop, not an ad network’s ads manager. There is one ad account per Whop business and no credit line for ad spend. Lookalike audiences based on Whop buyer data and AI creative tools are coming soon.
Whop Pixel and server events
Track browser activity with the Whop Pixel and report conversions known only to a server through the Events API.
Connect CRM sales, bookings, and other off-browser conversions to a visitor’s journey for ad attribution.
Use the Events API only when the conversion cannot be reported in the browser. Install the Pixel across the funnel; capture its visitor ID and the full page URL when the action starts, then send the event with a server-held API key with event:create permission. Events must be no more than 28 days old. Use the same event name and ID to deduplicate browser and server reports. Do not send purchase events for sales Whop processed.
Reinvest pending revenue into ads
Documented ad funding includes pending Whop balance.
Fund advertising before eligible sales revenue settles.
Confirm account eligibility and available balance.
Welcome and win-back messaging
Sends automated Whop DMs when someone joins or leaves a whop, with an option to send an email notification too. Messages can include names, media, and a selected team member as the sender.
Welcome new members with next steps and follow up with departing members for feedback.
Set up and enable the User joined and User left automations separately under Dashboard → Marketing → Support chats.
Marketplace storefront
Present products to buyers browsing Whop.
Make products available to people browsing Whop.
Listing creates an opportunity for discovery, not a promised volume of leads.
Business analytics
Track customer activity, revenue, subscriptions, payments, affiliates, disputes, and refunds with customizable dashboard widgets.
Review business performance and customer engagement in one dashboard.
Some metrics, including page visits, MRR, ARR, and revenue after Whop fees, are estimates. Widgets are grouped under Users, Payments, and Resolution Center.
Dispute Fighter
Tracks dispute status, outcomes and response deadlines, automatically uploads customer and access evidence, and lets sellers submit additional evidence.
Reduces manual evidence collection and helps sellers respond before the deadline.
Response deadlines vary by case; missing one results in an automatic loss. The card issuer makes the final decision, and some disputes cannot be challenged.
Fraud rules and risk scores
Apply checkout rules based on risk score, amount, card details, email or IP address to block, review, challenge or allow payments.
Apply your own risk policy alongside Whop’s fraud controls.
Pass account_id when creating rules, especially when managing multiple accounts. New or changed rules take effect within a couple of minutes. Review authorizes eligible card payments without capture; buyers receive membership access at authorization, and Whop captures automatically after 48 hours unless the payment is captured or voided sooner. Unsupported methods skip review. Some checkouts cannot carry a 3D Secure challenge. Allow rules do not bypass Whop’s controls. Writing rules requires payment:manage.
Tax service
For direct sales, sellers can choose to have Whop calculate and collect tax for them to remit, have Whop collect and remit tax and file returns in covered regions, or handle tax themselves. For marketplace sales, Whop calculates, collects, remits, and files tax where marketplace laws and Whop's registrations apply.
Lets sellers choose how much of their direct-sales tax process Whop handles.
The collect-only option calculates tax where the seller has added tax registrations; the seller must register where required, remit, and file. Its stated coverage is all U.S. states and territories plus jurisdictions on Numeral’s coverage list. The collect-and-remit option covers U.S. states and territories, the EU, and the UK. Sellers can choose tax-inclusive or tax-exclusive prices. Managed options do not remove obligations outside covered jurisdictions or for sales outside Whop.
Team roles
Invite team members, assign preset or custom roles, change permissions, and remove access.
Give teammates access appropriate to their work and revoke it when needed.
Require 2FA can be enabled from the Team tab. Operations excludes payouts, developer tools, dashboard analytics, account profile editing, and crypto wallets. The Advertiser role can manage ad campaigns and view analytics and account balance. Role changes and removals take effect immediately.
Stripe subscription migration
Move eligible subscriptions together with stored payment tokens.
Move eligible subscribers without asking them to re-enter payment details.
Card-based active/trialing subscriptions; preview eligibility, coordinate token transfer and notify customers.
Connected accounts and payouts
Onboard connected accounts, transfer funds to them, and create payouts to their selected payout methods. Platforms can choose to cover payout fees from their own balance.
Pay connected accounts programmatically and choose which account bears payout fees.
Payout recipients must complete identity verification and add a payout method. Payouts cannot exceed the available balance. API version 2026-11-03 and later requires a quote submitted before it expires; a timeout retry should use the same payout idempotency key and original quote token. Platform fee coverage must be set on both the quote and payout requests and requires an applicable fee coverage policy or an API key authorized to manage subaccounts’ fees.
Marketplace take rates
Collect an application fee on a direct charge to a subaccount, or collect payment on the platform account and transfer funds to subaccounts later.
Choose whether the subaccount owns the original payment or the platform controls transfer timing and amount.
With direct charges, the subaccount handles Whop fees, refunds, and disputes. The application fee must be positive, less than the total payment, and no more than the captured amount. With transfers, the platform is the merchant of record for the original payment and handles its fees, disputes, and refunds. The sending account must complete KYC verification and have sufficient balance; the recipient must have a Whop account able to receive funds. Review the cause of a failed transfer before retrying.
Identity verification
Start hosted individual KYC or business KYB verification, optionally pre-fill identity fields, and read the resulting status.
Verify payout recipients without building an identity collection interface or asking users to retype information you already have.
An Account API key with the identity:write scope is required. After an identity_profile.updated webhook, retrieve the current status; the webhook does not include the new state. A US individual's tax identification number is required to create a payout account. Users in sanctioned countries or regions are not supported. Reusing a Sumsub verification requires a Reusable KYC agreement and a single-use share token; a partially sufficient verification still requires the user to complete a hosted session. Previously documented API document submission and verification-management capabilities remain supported.
Whop Cards
Spend eligible Whop balances using cards and mobile wallets, and issue employee cards with spending limits.
Use business revenue for purchases and control team spending.
Regional eligibility and merchant restrictions apply. 5% cashback is limited to selected merchants, currently including Uber. Pending balance can fund card spending, instant payouts and ads. Standard bank withdrawals and account-to-account transfers require settled funds.
Card issuing for platforms
Issue cards to users through the API.
Let customers spend platform balances; potential interchange income.
Confirm program eligibility and commercial terms.
Whop Treasury
An announced stablecoin-based balance product with variable yield.
Allocate eligible balances to a variable-yield product.
Launch advertised up to 6% APY; check the live rate. Not guaranteed or FDIC-insured.
Websites and Blueprints
Deploy a copy of a business’s products, pricing, images, store styling, and hosted website from a blueprint.
Start with a connected sales site, then edit it or roll back a build from the dashboard.
The gallery separates Whop-verified curated blueprints from other community blueprints. Source code can be cloned with the CLI. Blueprint publishers earn 10% of Whop’s profit on sales through the deployed site, not 10% of seller revenue.
Managed hosting
Hosts uploaded website builds, supports promotion and rollback, provides encrypted app secrets and server logs, and authenticates server-side Whop API requests.
Deploy and operate a Whop-connected website without configuring a separate server.
Logs are retained for 7 days and exclude client-side JavaScript errors. Automatic API authentication acts as the app’s business, not the visitor. The injected key permits payout and transfer reads but cannot withdraw funds, send transfers, or manage payout destinations; use OAuth for visitor identity.
APIs, SDKs and embedded elements
Integrate payments, subscriptions, payouts, identity, wallets, community and analytics through Whop APIs, SDKs and embedded elements.
Combine documented business services in an existing product.
Use server-side credentials for your own product, or the CLI to build for Whop’s marketplace. Test money flows in the sandbox.
CLI and MCP
Connect AI clients to Whop documentation and a reviewed subset of live Current API operations through the MCP server. The CLI remains available for terminal workflows.
Look up current documentation and work with authorized Whop data while building.
The MCP server uses browser sign-in at /mcp, with no API key in the client configuration. Business context is selected per operation; endpoints requiring a first-party whop.com session are excluded. Tool calls run when the agent makes them. Payment, credential, and destructive tools carry a hint that clients use to request approval, but the MCP client decides what to approve. Inspect proposed actions and use a stable idempotency key for retries after uncertain outcomes. The retired /sse endpoint returns a 404.
Software access and licensing
Check a signed-in user's current access to a web-app product, or validate purchase-linked license keys for downloadable software.
Gate paid software access using Whop membership status.
For web apps, link the purchase to your user record through checkout metadata and a verified membership.activated webhook, then check access before serving paid features. For downloadable software, install the Software app to issue keys; validate keys on your server. You can limit a key to one machine by storing and comparing a hardware ID in membership metadata. Keep the account API key server-side.
Native iOS checkout SDK
Sell in-app purchases and subscriptions in a native iOS app, display subscription variants, and check entitlements to gate premium content.
Use Whop checkout for US purchases and StoreKit elsewhere, with subscription status available to control access.
Requires iOS 17.0+, Xcode 15.0+ and Swift 5.10+. Configure the SDK with a scoped `iap:read` API key and variant mappings. Compatibility symbols including `plans` and `planMappings` refer to variants.
App distribution
Publish apps that Whop businesses can install from the App Store into their communities.
Distribute software to businesses using Whop, with Whop handling sign-in, billing, and mobile.
Businesses choose whether to install an app; installations and revenue are not guaranteed.
Bounties
Post funded tasks once or on a repeating schedule, restrict workers by country, and collect work as links, uploaded files, or both. Rewards are released when submissions are approved.
Workers can see that a reward is funded before starting, while task posters can review work before payment.
Task posters fund the reward pool up front.
Business formation
Start LLC or C-Corp formation for a business account and track the application through company_formation.
Connect business setup to a hosted filing checkout.
Defaults to LLC. C-Corp formation requires share_structure and officer roles on each founder. Filing is submitted after payment; creation of the application is not completed formation.
WhopX
Founder community with access tied to verified Whop earnings.
Access an operator community organized by verified earnings.
Published entry tier starts at $1,000/month processed on Whop; benefits vary by tier.
Whop Partners
Earn for referring businesses to Whop.
Earn referral income from businesses introduced to Whop.
Published terms describe up to 30% of Whop gross profit, not 30% of the merchant’s sales.
Neobank Blueprint
Deploy a branded financial product with balances, cards, deposits and withdrawals.
Start a branded financial product on Whop infrastructure.
Customize the template and confirm enabled financial rails. The blueprint does not itself confer a banking license.
Embedded wallet
Embed account balances, funding, transfers, conversion, payouts, cards, reports and ledger activity using Whop wallet elements.
Let users manage and inspect money within your product without building each view from scratch.
Account scope and viewer authorization apply. Data-backed surfaces can use the viewer’s session when no token is provided; personal-account balance reads are limited to the viewer’s own balance. Some actions open Whop-hosted flows, while others require the host to handle an event or provide the necessary access token and scopes. The host must handle identity-verification requests. FX currencies require fxEnabled. Previously supported wallet capabilities remain supported.
Platform fee markups
Change only account fee fields reported as adjustable, while leaving omitted fields unchanged.
Manage permitted account pricing without replacing unrelated fees.
Effective rates are shown in the response. Pricing provenance and comparisons require parent-account access. This endpoint does not establish a public fee schedule.
Whop Workforce
A public work community where people complete paid tasks and submit proof.
Source people for defined paid tasks.
Workforce is the worker-facing program; Bounties is the documented task, review and payment infrastructure. Confirm campaign distribution before promising reach.
Recurring bounty programs
Schedule paid tasks to repeat hourly, daily, weekly or monthly, with separate submissions and escrow for each occurrence.
Run recurring tasks and show submission status in your own product.
Recurring tasks require publish_at and publish_at_timezone. Escrow is the gross reward per accepted submission multiplied by the number of winner slots, with a $5 total minimum. Rewards, slots and schedules are fixed after publication. Approval and denial happen in the Whop dashboard, not through the API; integrations must poll for outcomes. Workers finish data-capture and livestream proof in Whop.
Blueprint publishing income
Publish a business blueprint and receive 10% of Whop profit on attributed site sales.
Earn from sales attributed to deployed copies of your blueprint.
Applies to sales through the deployed site, not 10% of seller revenue or every financial fee.
Whop AI assistant
Ask Whop AI for help with your business and reports on user and membership data.
Get help in plain language while working in Whop.
For a setup task, ask for a plan and confirm which actions the assistant can perform in your account. Whop AI reporting is documented; do not assume every workflow is fully automated.
AI website builder
Describe a website in Whop’s dashboard to create a hosted first draft, then edit it or pull its source.
Start a site from a business brief instead of a blank repository.
Open Websites → New website → Create your own. Website apps cannot later be converted into marketplace b2c_app apps.
Pay your team
Pay team members from your Whop balance in Dashboard > Team, or pay another Whop user from their profile.
Send an approved contractor or team payment without building a custom payout integration.
Team payments carry a 3% fee included in the total sent. Recipient receives an email and DM and can cash out via Profile > Balance. Dashboard payments: select Pay next to the person, enter amount, choose balance and Send.
Custom checkout with payment elements
Build a checkout form with PCI-isolated payment fields and your own pay button. Recognized Whop buyers can sign in to use saved payment methods.
Control the checkout form while keeping card numbers off your page.
Include Whop’s merchant-of-record notice and an HTTPS return URL. Charge the confirmation token from your server, and fulfill only from a signature-verified payment.succeeded webhook, not the return page.
Card cashback rules
Lets a neobank operator set cashback rules for card purchases, funded from its own balance.
Offer targeted spending rewards while controlling each rule’s rate, scope and dates.
The operator funds the cashback.
Express checkout
Show Apple Pay and Google Pay buttons for a product variant on supported devices.
Let buyers pay through an available wallet without a full form.
Register the payment-method domain and use HTTPS. Keep a regular checkout option when a device has no wallet. Fulfillment must come from the server webhook.
Custom wallet payment requests
Open Apple Pay or Google Pay from your own button, calculate the order amount and charge a confirmation token from your server.
Use wallet payment in a custom cart or checkout interface.
Check canMakePayment first, register the domain and use HTTPS. A wallet checkmark indicates token creation, not a settled server charge. Handle any next action and fulfill from payment.succeeded.
Subscription lifecycle management
Pause, resume, cancel or restore subscriptions and add free days.
Manage changes to recurring access and billing.
Use documented membership operations; saving payment methods and handling refunds are separate payment flows.
Whop Verified Partners
Lets certified partners set permitted fees for referred businesses and request attribution from businesses already on Whop.
Supports custom deals and partnerships beyond referral-link signups.
Enrollment requires a $199 USD one-time payment, completion of the partner course, and identity verification. Fee changes are limited to rates Whop allows; an existing business must accept an attribution request.
Resolution Center cases
Manage customer payment cases with an event timeline, requests for information, and merchant decisions. Customers can appeal a case decided in the merchant’s favor or withdraw an open case.
Track and resolve payment complaints in one workflow.
Accepting a case refunds the payment in full. Merchants may request customer information up to three times per case. A customer may appeal a case once, which escalates it to Whop for platform review.
Account data exports
Starts asynchronous exports of account resources and provides a download link when an export is complete.
Lets teams retrieve account data for use outside Whop.
Available only for resources the credential is allowed to export; the download link is provided after completion.
Webhook delivery management
Lets developers inspect delivery attempts, send test events, and replay past webhook deliveries.
Helps teams troubleshoot integrations and retry event delivery.
Replayed deliveries are sent to the webhook's current URL. Replays retain the original webhook ID by default, which may cause consumers that deduplicate events to drop them.
Lead records
Create and manage records of prospective customers who have not yet purchased.
Track interest in a company or specific product.
Documented in the Legacy API reference.
Member token balances
Record token credits, debits, and transfers between members within a company.
Manage a company-specific member token balance through the API.
Documented in the Legacy API reference.
Shipment tracking records
Associate a physical shipment and its tracking information with a payment.
Keep shipment details tied to the corresponding payment.
Documented in the Legacy API reference.
Economic Intelligence
Shows recommended next actions in the business dashboard based on business context.
Helps operators decide what to work on next.
Recommendations are suggestions, not guaranteed outcomes.
App notifications
Send app-attributed notifications to users of an experience or an account team, and read a user's notification feed and unread badges.
Add notifications and unread indicators to an app experience.
Sending requires an app API key or a credential acting on behalf of an app. Reading a user's feed and badges requires a user credential; sends are processed asynchronously.
Account reserves
Shows an account’s held balance by currency, including why funds are held and the days they unlock.
Helps teams understand held funds and their expected availability.
The information is available through the account reserves API.
Financial activity and reports
Provide an account or user's money-movement activity feed and account financial reports over a date range, with breakdowns of report categories.
Review balance movements and examine the entries behind report totals.
Financial reports are available for an account; activity feeds cover an account or user.
Embedded chat
Add real-time chat to a web or native iOS app, including shared channels, direct messages, and support conversations.
Offer conversations within an app while Whop handles messages, real-time updates, media uploads, and chat UI.
Embedded users must be authenticated with account-scoped tokens or OAuth; existing platform users can be created or mapped to Whop users.
Passkeys
Lets users register, list, and delete their own passkeys through the API.
Supports passkey management and confirmation before a sensitive action.
These beta API endpoints require a user session; API keys and OAuth tokens cannot list passkeys. Registration and deletion use single-use WebAuthn challenges.
Connected account controls
Lets a platform suspend or delete a connected account it directly owns.
Gives platforms controls for managing connected accounts.
The beta API cannot suspend the platform account or another platform’s account. Deletion requires no settled, pending, or reserved balance in any currency and no active, trialing, or past-due memberships.
Payment quotes
Price a proposed purchase using the payment details and buyer location before creating a payment.
Show a buyer a price calculated for their purchase and location before charging them.
Buyer location is determined from the shipping address, then billing address, then a supplied IP address.
Authorize and capture payments
Authorize a card payment and capture its full amount later.
Separate card authorization from collection when the full amount should be captured later.
Capture must occur while the payment is in `requires_capture` and before `capture_expires_at`. Partial or multiple captures, capturing more than the authorized amount, and tips are not supported.
AI business plugins
Connect Whop business operations to Claude Code or Grok Build through a plugin.
Manage products, checkout, payments, payouts, ads, and stats from a supported terminal-based tool.
Requires installing the plugin for Claude Code or Grok Build.
Financing applications
Lets an eligible merchant create an application, save required answers, review its terms and submit it for payment-financing approval.
Gives merchants a way to complete financing requirements and track the review state.
An existing ledger account is required, restricted industries cannot apply, and submission requires presenting the current terms, policies and disclosure and collecting affirmative acceptance. Approval is not guaranteed.
Checkout branding
Set checkout colors, fonts, and borders for an account, with overrides for individual links and sessions. Prefill known customer details at checkout.
Keep checkout pages consistent with a business or campaign and avoid asking customers to re-enter known details.
Session styling takes precedence over link styling, then account defaults. Fonts are limited to system, Roboto, and Open Sans. A prefilled email can be locked or hidden; provide the email parameter to use either option. Prefilled phone and address fields remain editable.
Payment decline guidance
Look up payment decline codes and the documented next steps for the buyer.
Resolve failed payments with an appropriate action instead of repeated blind retries.
Some failures require another method, corrected card details, bank authentication or contacting the issuer. A duplicate-transaction decline calls for checking whether payment already completed.
GoHighLevel integration
Use Whop as a native payment provider for GoHighLevel payment links, checkout pages, invoices, and subscriptions. The integration also supports saved-card charges, full and partial refunds, and payment status updates in GoHighLevel.
Customers can pay without leaving a GoHighLevel funnel or invoice, while subscription changes and payment updates stay in sync.
Requires access to the GoHighLevel agency or sub-accounts and admin access to the Whop business. Connect the intended accounts through the setup wizard, choose payment methods, and set Whop as the default provider in each connected sub-account before payments route through Whop.
HubSpot integration
Sync Whop payments, memberships, and products into HubSpot, and generate Whop checkout links from deal or contact records.
Let sales teams see payment and subscription activity and send checkout links from HubSpot.
Requires a Whop business with at least one product and a HubSpot account that can install apps. Install the app, provide a Whop API key, and sync products again after adding or changing them. The app syncs every Whop payment, including payments that did not start in HubSpot.
QuickBooks integration
Sync Whop sales, completed payouts and refunds with QuickBooks Online according to the selected mode. Add Whop payment links to QuickBooks invoices, create Whop plans from recurring invoice templates, and sync QuickBooks items to Whop products.
Reduce manual bookkeeping and collect QuickBooks invoice payments through Whop.
Requires admin access to a Whop business and a QuickBooks Online company; QuickBooks Desktop is not supported. Map accounts and choose All Sales, Withdrawals Only or Invoicing Only. Historical backfill is optional, and switching modes affects only future activity. Withdrawals Only can double-count revenue when used with QuickBooks invoices. For invoices, remove tax settings from matching Whop products to avoid taxing buyers twice.
Zapier integration
Use Whop payment, membership, dispute, invoice and waitlist events to start Zaps. Use actions and searches to manage or look up Whop records in workflows with other apps.
Connect Whop to existing business automations without writing a custom integration.
Zapier is an external service. The current documentation lists 16 triggers, 20 actions and 12 searches. Create Payment charges a member’s saved payment method asynchronously; confirm the result with a New Payment or Failed Payment trigger. Older Zaps may use trigger names that no longer appear in the current app.
Payment controls
Shows the controls active on an account with elevated risk, including reserves, automatic-refund thresholds, payout delays, fees, and possible checkout restrictions. Account controls are also available through the API.
Helps a business understand how risk controls affect its payments, checkout, and access to funds.
Whop sets controls per account and reviews them continuously; they may tighten as risk rises and ease or lift as it falls. Not every listed control applies to every account. No fee rates are specified on this page.
Payment health dashboard
Review dispute and refund rates, dispute reasons, and the payment controls active on your account. Compare disputes filed in a 30-day window with disputes grouped by purchase date.
Find the source of payment problems and track recovery.
The by-purchase-date view only counts payments after the selected dispute window has elapsed. Healthy, At risk, Critical, and Low data statuses depend on the metric and payment method; do not treat every network as using the same threshold.
Account suspension guidance
Explains suspension reasons, appeal routes, permanent bans, and how funds are handled during a suspension.
Helps account holders identify where to appeal and understand when remaining funds may be withdrawn.
Most suspensions can be appealed within 30 days; a human reviews every appeal. Tax authority orders and platform-requested suspensions require different contacts. For reasons other than fraud, sanctions, or tax orders, the remaining balance may be withdrawn by standard bank withdrawal 120 days after suspension; a new chargeback can move the date to 90 days after that chargeback. Fraud, sanctions, and tax-order suspensions require review, and funds are not released if the suspension is upheld. Reserve funds follow their own schedule. Permanent bans can be appealed within the same 30-day window.
iOS in-app purchase pricing
Automatically marks up eligible one-time products under USD 700 in the Whop iOS app by 42.86% to offset Apple's 30% in-app purchase fee.
Helps preserve the creator's product earnings while making the different iOS app price clear to customers.
Apple processes these purchases and receives the 30% fee. One-time purchases of USD 700 or more and all subscriptions use Whop's web checkout without that App Store fee. Customers can avoid the iOS app price by buying in a browser. Apple-processed purchases can remain pending for up to 75 days, and customers must request refunds directly from Apple.
Funded claim links
Create funded transfer links that recipients redeem into their personal Whop balance after signing in.
Send money to recipients through a redeemable link.
Claim codes are secrets. Company API keys cannot claim for a recipient; each user can claim a link once. Reuse the same idempotency key when retrying. This is a money-transfer flow, separate from business ownership invitations.
Wallet perpetual trading
Submit a market buy or close a perpetual position from a Whop-managed wallet.
Connect supported wallet balances to a documented trading workflow.
Hyperliquid perpetuals are the supported venue. The trading API is beta and can change without a new version date. A pending response is not completion; retrieve the trade until completed, failed or in_review. Reuse the same idempotency key for a retry.
Platform payment trends
Read platform-wide payment reports across up to four time windows, with breakdowns by business type, industry and account or customer country.
Compare payment patterns across business categories and markets.
The platform report takes no account_id and is available to authenticated callers. Groups representing fewer than three businesses are suppressed or return null metrics; these are aggregate reports, not customer-level records.
Sandbox testing
Test a Whop integration in a sandbox before going live.
Check integration behavior without using a live environment.
Account ownership transfer
Transfers account ownership to another user by user ID or email address.
Lets an account owner hand over ownership without recreating the account.
If the recipient already has the owner role, the transfer is immediate. Otherwise, ownership moves when they accept an invitation.
Membership account transfers
Move a membership or purchase between Whop accounts using a transfer link.
Consolidate purchases when a customer has multiple Whop accounts.
Copy Transfer membership from the order menu, sign into the destination account and open the link. Each membership links to one Discord account at a time; disconnect Discord from the incorrect Whop account before reconnecting it. This is a customer membership transfer, separate from business ownership.
Sign in with Whop
Add Whop sign-in to a website using OAuth 2.1 and Proof Key for Code Exchange (PKCE).
Let visitors sign in with their Whop account.
Requires an OAuth integration.
Account deletion
Lets a user permanently delete their entire Whop user account from account settings.
Provides a way to close a user account.
Delete businesses and withdraw any balance first. Cancel all memberships before deleting the account. This does not delete just one business or whop.
Two-factor authentication
Lets account holders enable two-factor authentication using an authenticator app or text message.
Adds an extra layer of account security.
Whop recommends an authenticator app over SMS. Enabling 2FA logs you out of devices that refresh automatically.
Approximate location visibility
Let users hide their approximate location from other Whop users in account settings on the web or in the Whop app.
Gives users control over whether their approximate location is visible.
Users who hide their location also cannot see other users’ approximate locations.
Account email updates
Let account holders change their email address in account security settings by verifying a code sent to the new address.
Keep the account’s contact email current.
If the registered email is inaccessible, Whop Support must verify the account holder’s identity before making changes.
Account phone number updates
Let account holders add or change the phone number on their Whop account in account security settings, with verification by text message.
Keep the account’s phone number current.
Requires access to the phone number to receive a verification code.
Account username updates
Let account holders change their Whop display username in account settings.
Keep the name shown to others on the platform current.
Affiliate marketplace
Lets affiliates browse offers, review commission rates and earning stats, get referral links, and track their earnings.
Find offers to promote and monitor referral income.
Commissions have a 30-day waiting period after a referred purchase. Disputes, refunds, or fraud detection return the commission to the business.
Tracking integrations
Connect a whop to supported external analytics platforms by entering tracking IDs and API keys.
See where visitors come from and connect page views to marketing campaigns.
Supported platforms are Google Analytics, Hyros, Meta, TikTok, X, Reddit, Pinterest, and HubSpot. Activation requires setup in Dashboard → Settings → Analytics.
Tracking links
Create custom links to a Whop store or checkout and measure clicks, revenue, conversions, and buyers for each link.
Compare how marketing links perform across channels.
Set up links in Dashboard > Marketing > Tracking links. Choose the destination and pricing plan when creating a link.
Xero integration
Connect Whop to Xero as a bank feed. Sales, fees, refunds, lost chargebacks and payouts arrive as statement lines to match to existing invoices. Optional payout mapping records payouts as transfers to the corresponding Xero bank account.
Reconcile Whop activity against existing Xero invoices and, when payout mapping is enabled, bank deposits.
Uses the Xero Sync app; it does not create invoices, contacts or products. Requires Whop business admin access and a paid Xero organisation with bank-feed support. Demo and ledger organisations are unsupported; multiple currencies require a multi-currency Xero plan. New activity reaches Xero within about 15 minutes, but matches require confirmation in Xero. Payout mapping requires an account in the payout currency; an existing connection may need to be reconnected to enable payout transfers.
External ad account connections
Connect external accounts through an OAuth flow, inspect linked accounts, and disconnect them from Whop.
Lets teams manage connections used for social advertising without deleting the underlying platform accounts.
Personal profile connections must be completed in a browser signed in as the Whop user who started the flow.
Early dispute alerts
Notifies sellers about an early dispute alert and supports automatic refunds for alerted payments below a configured threshold.
Gives sellers a chance to resolve an issue before it becomes an official dispute.
Set the refund threshold in Dashboard > Settings > Risk. For new accounts without healthy payment history, Whop automatically refunds alerted transactions under $500; the setting can be changed or turned off after healthy payment history is established. Each early dispute alert costs $29.
Payout methods
Add multiple payout destinations and withdraw to an eligible bank account, mobile wallet, or crypto wallet. Standard and instant payouts are available where eligible, and supported international payouts can use a currency other than the account holder’s local currency. Change the payout country for an existing Whop from payout settings.
Choose an eligible destination and payout currency for earnings, or update the payout country when needed.
Options vary by country. A bank account must accept the payout currency, and a foreign-currency payout method must be offered in the account holder’s country. Standard payouts take up to 5 business days; instant payouts take a few minutes and can include pending funds, but are unavailable when a withdrawal requires compliance review. PayPal payouts require a PayPal purchase. Coinbase payouts require a crypto purchase, a Coinbase wallet, and a one-time pricing plan.
Split payment checkout links
Turn a recurring checkout link into a fixed installment plan with a set number of payments.
Let customers pay over multiple billing periods rather than all at once.
Whop charges each installment on the schedule and stops after the final payment. The seller receives each installment as the customer pays it; this is not financing that pays the seller upfront.
Customer transactional emails
Send customers purchase, renewal, payment-failure, cancellation, and refund emails, with a setting to turn these transactional emails off.
Keep customers informed about payment and membership events without setting up each notice yourself.
Connected accounts created by a platform through the API start with customer emails off; the platform can enable them. Turning transactional emails off also stops order confirmations, renewal reminders, and payment-failure notices. Invoice emails, billing-schedule notices, and automated messages still go out. Whop’s email wording cannot be edited.
Checkout questions and redirects
Add pre-checkout questions and configure post-checkout redirects for a product.
Collect information before checkout and direct customers after checkout.
Listed as advanced options when creating a free product.
Mobile membership access
Lets members open their whops and use content in the Whop app or a mobile browser.
Members can access their memberships on a phone.
Members must log in with their Whop account. Linked services, including Discord, may require additional steps in those services’ apps or sites.
Purchase and membership lookup
Members can find joined whops in their account sidebar and view purchases under Orders. If a purchase is missing, they can use the order confirmation or purchase details linked from a bank or card statement to identify the account used.
Helps customers locate purchased access and determine which account holds it.
Customers must sign in to the account used for the purchase. If the purchase does not appear under Orders, they may be signed in with a different email address.
Member notes
Add and list notes on a member record.
Keep member context available to the account team.
Notes are visible to the account's team.
Notification preferences
Let users view and set notification preferences, including per-experience levels and topic-specific settings.
Give users control over which notifications they receive.
An experience with no saved level has an effective level of `all`. Preference changes submitted as a batch are applied together or not at all.
Member content rewards
Let members earn creator-defined rewards for actions inside a whop, such as finishing a course or posting in a forum.
Encourage participation in member content and discussions.
The creator must enable Content Rewards and define the actions and rewards. Redemption options depend on the creator's setup.
Instagram partnership ads
Invite an Instagram creator to grant permission for partnership ads and check the status of that permission.
Lets a business coordinate creator permissions for ads using its connected Instagram account.
The creator must approve the invitation in Instagram. Permission remains pending until approval; refreshing the partner retrieves the creator’s response.
Custom affiliate deals
Invite specific affiliates and set a flat or percentage reward on the first payment or every payment. Limit referrals to selected plans.
Tailor referral terms for individual closers, creators, communities, or partners.
Invite users by email, Whop username, or Whop user ID. Invited affiliates receive unique referral links that track conversions and handle payouts.
Preferred settlement currency
Convert each new sale into a selected settlement currency: USD, EUR, GBP, CAD, or AUD.
Receive new sales in a chosen supported currency.
The documentation covers which sales convert and how refunds, disputes, and platform fees settle.
OAuth grant visibility
Lists the apps the authenticated user has authorized, with a separate grant for each account authorized.
Lets users see which apps they have authorized for each account.
Requires a user session. API keys and OAuth tokens cannot list grants, and users cannot read another user's grants.
Balance swaps
Swap one crypto token for another in an account or user wallet, or convert between fiat balances.
Preview a swap’s price before moving funds and check the status of a crypto swap while it processes.
Fiat conversions use the mid-market rate. Crypto swaps finish in the background.
Failed ads payment retries
Queues a background retry of failed ads payments across an account’s campaigns using its configured ads payment methods.
Lets an account retry failed campaign payments and check campaign status for the outcome.
A queued retry does not mean payment succeeded; check each campaign’s delivery_status and issues.
Balance deposits
Retrieve available bank-transfer and crypto deposit methods for an account.
Show an account how it can add funds to its balance.
Crypto deposits require a $10 minimum.
Payout quotes
Provide a short-lived quote showing a payout’s fee, exchange rate and destination amount before the payout is submitted.
Let the sender review the expected payout details before moving funds.
The quote is provider-backed. Funds do not move until the returned quote token is submitted to create the payout.
Customer tracking page
Provides a hosted customer tracking page with account branding and support contacts.
Gives customers a branded place to view tracking information and find support contacts.
The account must turn customer tracking on in its preferences. The page’s branding and support contacts are publicly retrievable without authentication.
Reverse bank deposits
Send a bank deposit back to the bank account that wired it and remove it from the Whop balance.
Return a bank deposit to its originating account.
The available balance must cover the deposit minus the deposit fee, which is refunded.
Cancel payouts
Cancel a payout before it is sent to the payout provider, or request that the provider stop a payout already sent.
Recover funds and fees when a payout can still be canceled.
A payout in review, or processing with nothing sent yet, is canceled and its funds and fees return to the balance. Cancellation after it has been sent is a request to the provider, not a guaranteed stop.
Klaviyo integration
Connects an account’s existing Klaviyo account to Whop using a private API key.
Lets teams link an existing Klaviyo account to their Whop account.
Requires an existing Klaviyo account and a private API key. The source does not describe what data or actions the connection supports.
Shopify fulfillment integration
Connect Shopify fulfillment when selling physical products through Whop.
Use Shopify fulfillment alongside Whop checkout.
The guide does not specify setup steps or availability.
VAT and GST registration details
Lets eligible sellers confirm whether their business is registered for VAT, GST, or a similar tax and add or update a registration number in Settings > Tax.
Helps Whop apply the correct tax treatment to its fees and services and keep accurate tax records.
The request covers supported countries outside the United States and its territories, including former sellers. Respond by November 30, 2026; payouts may be paused from December 1 until the information is provided. An owner or a team member with permission can add a number, but only the owner can confirm the business is not registered. Whop does not require a VAT or GST number to sell.
Scheduled app runs
Run hosted Whop app code on a schedule, either once per time slot or once for each installation.
Automate recurring app tasks.
Applies to hosted apps.
AI-generated media
Generates image or video assets through the Whop CLI and makes them available as files.
Creators can use generated assets wherever uploaded files are accepted.
Generation is billed from a balance. The CLI has no sandbox or test mode; commands run in production.
Ad audiences
Lets advertisers upload a customer list as an audience to target or exclude from Whop ad campaigns.
Supports more specific campaign targeting.
The audience API is labeled beta. Campaigns cannot target Sudan, Russia, Cuba, Iran, or North Korea.
Account record search
Search an account’s members, memberships, payments, affiliates, reviews, Resolution Center cases, promo codes, and accounts in one call.
Find related account records without searching each resource separately.
Search is scoped to one account. Subaccounts can be included when requested.
Whop Levels
Awards points for spending with Whop Cards, on Whop Ads, and on Investing. Points unlock levels and discounted payment volume.
Businesses can reduce payment acceptance rates on eligible volume.
Cards and Ads earn 10 points per dollar; Investing earns 1 point per dollar. Points reset on the 1st of each month, but the level persists across a user's Whop businesses. Only unlocked volume receives the discounted rate; other payments return to the standard rate until more volume is unlocked. Rates depend on where the customer's card was issued. At level 10, the stated rate is 0% for cards issued in the US, Canada, EU, UK, and Australia; other regions have different rates.
Account experiments
Lets an account list, create, update, and manage experiments, including exposures.
Provides a way to manage experiments and review exposure records.
Experiment creation is not yet available to all accounts. Account experiments do not accept tags. The CLI has no sandbox or test mode; its commands run in production.
Idempotent API requests
Accepts an Idempotency-Key header on authenticated Current API POST requests and replays a successful request’s stored response when retried with the same key.
Lets developers retry a timed-out request without creating a duplicate charge, transfer, or resource.
Responses are stored for 24 hours. Use a fresh key for each distinct operation; an identical retry with the same key replays the response, while a different request returns 400 and a retry during execution returns 409. Error responses can also be replayed.
API version pinning
Pins Current API requests to a dated version using the Api-Version-Date header or an API key version pin.
Lets developers adopt breaking API changes when they are ready while keeping an integration’s request and response shapes stable.
An explicit header overrides the API key pin. Official SDKs send the version used to generate them. Without a header or stored key pin, requests use the original 2025-01-01 behavior; newly created keys use the latest released version. Review intervening changelog entries before upgrading.
App views
Lets developers configure member-facing experience views, creator dashboard views, or both for a Whop app.
Place an app’s member features in the Whop sidebar and its business tools in the creator dashboard.
Configure view paths in the app’s Hosting settings. The page’s access-validation examples will not run as written because verifyUserToken is not available in the current @whop/sdk.
Scoped access tokens
Mint short-lived tokens for a specific user within an account, or for the account itself, with an explicit list of allowed actions.
Let a client access the Whop actions it needs without exposing an API key.
Mint tokens on your server. They expire after one hour by default, with a three-hour maximum. Always specify scoped_actions: omitting it gives the token every permission held by the minting credential. Account access tokens have no user attached and cannot use endpoints that act as a user.
App user access checks
Lets an embedded Whop app identify the viewer from a short-lived token and check their access to an experience, account, or product.
Helps developers restrict app views to eligible members or account team members.
The user token is attached only to same-origin iframe requests. The documented verifyUserToken helper is unavailable in the current @whop/sdk, so the TypeScript snippets do not run as written. Python's helper requires PyJWT and an app ID; Ruby provides a module helper, not a client method.
Chat API
Send and read community messages, manage channel moderation settings, add reactions, and open support conversations from a backend.
Connect community chat and one-to-one support workflows to an app without embedding a chat interface.
This is the server-side API, separate from Embedded chat. Apps need the relevant chat and support-chat permissions before publishing.
Support chats
Provides one-on-one customer support conversations tied to an account, with an inbox for team members.
Teams can manage customer conversations using open and resolved states without giving every responder full account admin access.
Requires a customer Whop user ID or username. Create or retrieve a support channel and use its ID to render the chat; build the team inbox with the support channels API. Moderators can help respond. Support chats do not grant product or membership room access.
Development proxy
Runs a local Whop app behind a proxy that injects the x-whop-user-token header, replicating production iframe authentication behavior during development.
Lets developers test requests with the user-token header on localhost.
Supports a wrapped mode for Node-based development scripts and a standalone mode for other frameworks. The documented verifyUserToken method is not available in the current @whop/sdk.
Forum API
Create and read forum posts and comments, and add reactions through the SDK.
Build tools that publish content or work with discussions in a Whop community.
Content is scoped by forum experience. Apps need the relevant forum and chat permissions; forum reactions are limited to hearts.
Frosted UI
Provides a React component library and design system with accessible components, typography, colors, responsive styling, and dark mode support.
Helps developers build consistent interfaces for Whop apps.
Install @whop/react and wrap the app with WhopApp to set up the theme and iframe SDK. Tailwind integration is optional.
Iframe app navigation
Lets an embedded Whop app open external websites and display Whop user profiles through the iframe SDK.
Gives users a way to follow links and view profiles from within an app.
Initialize @whop/iframe or use WhopIframeSdkProvider. The SDK works only in client-side JavaScript or Client Components.
App permissions
Lets developers declare the permissions an app needs, mark them required or optional, and request creator approval when the app is installed.
Creators can review access at install and decline permissions that are optional.
Every API call needs its matching permission. The approval flow also applies when testing on your own account. Adding a permission to an existing app requires each creator to re-approve it before calls needing that permission succeed.
Claude Code plugin
Connects Claude Code to a live Whop business through a plugin that bundles the Whop API MCP server and usage skills.
Lets an authorized user work with products, payments, ads, and business statistics from the terminal.
Install the plugin, restart Claude Code, and authorize access through Whop. It requests an admin permission profile covering every business the Whop user manages. Financial, credential, and destructive operations require preview and approval before execution. The MCP server only reaches production, not the sandbox.
Grok Build plugin
Connects Grok Build to a live Whop business through the Whop API MCP server and plugin skills.
Lets an authorized user work with products, payments, ads, and business data from Grok Build.
Install the plugin, then sign in and approve access through /mcps. It requests an admin permission profile covering every business the Whop user manages. Financial, credential, and destructive operations require approval after a preview.
React Native apps
Build a Whop app for iOS, Android and web from one React Native codebase, with experience and dashboard views.
Develop mobile and web views together and test development builds before submitting them for production review.
Requires Node.js 22+ and pnpm 9.15+. The page’s client-side data-fetching and server-side token-verification examples use deprecated SDK interfaces. Development builds require Dev mode to preview; production builds require approval.
Payment refunds
Issue full or partial refunds for successful payments through the API and retrieve refund records.
Handle customer refunds and reconcile refunded amounts.
Refunds go through the original payment processor, and the matching membership status updates automatically. Issuing a refund requires `payment:manage`; retrieving refunds requires `payment:basic:read`. A disputed payment cannot be refunded through `payments.refund`.
Dispute evidence submissions
Retrieve disputes, stage supporting evidence, and submit a response through the API.
Give teams a way to respond to chargebacks and track their status.
Evidence can be edited until submission, after which it cannot be edited. The buyer’s bank decides the dispute; a response does not guarantee a favorable outcome. Reading disputes requires `payment:dispute:read`; updating or submitting evidence requires `payment:dispute`.
Stats API
Lets apps discover available metrics and retrieve account revenue, payment, and engagement time series, with supported filters and breakdowns.
Enables custom reporting over a selected date range.
Account revenue queries require the `stats:read` permission. Filters and breakdowns must use properties supported by the selected metric.
Embedded payout portal
Lets platforms embed a portal where users manage their own payout methods.
Users can manage payout methods without the platform building that interface.
This overview does not specify setup requirements or payout-method eligibility.
Embedded ad reporting
Mount charts or tables showing an advertising account’s spend and results over a selected window.
Show campaign reporting in your own interface, with optional links from table counts to your tracking pages.
The elements are scoped to a Whop account ID and use a scoped access token for authenticated access. Links to tracking pages require absolute URLs.
Element appearance customization
Styles Whop elements with themes and per-part overrides across web and React Native.
Helps embedded elements match the surrounding interface.
Documented for @whop/elements@1.10.0 and @whop/elements-react@1.10.0. Web uses CSS variables and class declarations; React Native uses numeric tokens and style objects for the same part names.
Headless PayPal checkout
Lets a site use its own PayPal button to start a checkout session for one or more items. An optional shipping flow can price addresses through the seller’s webhook before the buyer approves.
Supports a custom PayPal checkout flow, including server-priced shipping.
Requires @whop/elements or @whop/elements-react v1.10.0 or later. Shipping pricing requires an enabled HTTPS webhook subscribed to shipping_address.changed. Show the session’s terms links and obtain active acceptance when required. The PayPal flow cannot handle carts with a promo code, buyer fee, marketplace split, or renewing plan, or accounts that cannot price the payment through their webhook. After a full-page redirect, read the outcome from redirectUrl rather than the show() promise.
Embedded account dashboard
Embed an account’s payments table, payment details, and outstanding-action banners on your site.
Give account holders payment information and next-step prompts within your own interface.
Requires an accountId. A server-minted access token needs scopes for the information shown; payment reads require payment:basic:read, and outstanding-action banners require payout:account:read. The payments table is intended for accounts with modest payment histories. The host application handles requested deposit, verification, and payment actions; the elements do not complete those actions themselves.
Required action banners
Displays outstanding account actions in an embedded dashboard, including identity verification, deposits and tax tasks.
Lets account holders see what needs attention without the host building its own action list.
Mounts inside Dashboard. Its access token needs payout:account:read, plus identity:write to start verification. Verify opens a hosted identity session; Add money requires the host to mount a deposit flow. The element displays nothing when there are no outstanding actions or when its read fails. Call refresh() after a viewer returns from verification or depositing.
Checkout tax ID collection
Collects a buyer’s business tax registration type and value in a Payments element.
Lets buyers select the appropriate registration type, with a default based on their country.
Mount inside Payments. The host supplies API validation errors and must send the collected pair to its own order or customer record.
Embedded event stream
Displays a raw, filterable stream of an account’s measured page views, leads, purchases, and custom pixel events inside a Tracking view.
Lets teams inspect the events behind a metric or search an identifier to review one person’s journey.
Mounts inside Tracking and uses its account ID and access token. An identifier search shows the person’s whole history rather than the selected time window.
Embedded audience tracking
Embeds an account’s pixel-tracked people, events, and individual person records on a website.
Lets a team inspect visitor activity and attribution alongside its own tools.
Requires an account ID. For cross-origin use, supply a server-minted scoped access token; list access requires member:basic:read or company:basic:read. Additional scopes enable filter-option counts and the People table’s saved-audience filter.
Embedded people directory
Embeds a searchable, filterable list of visitors and customers resolved from pixel activity, with source, spend, and activity information.
Lets a platform show account-level people data and connect a person row to its own detail view.
PeopleElement mounts inside Tracking and uses its account ID and access token. Documented for @whop/elements@1.10.0 and @whop/elements-react@1.10.0.
Embedded person profile
Embeds a view of one person’s identifiers, acquisition source, spending, and event history.
Lets a team inspect a person’s activity from its own tracking interface.
Mounts inside Tracking and requires an identifier for the person. Available inline or as a modal overlay.
Embedded verification status
Displays an account’s individual and business verification status and the capabilities that status unlocks in an embeddable element.
Lets a platform show verification standing and available capabilities within its own interface.
The element is read-only. A verify-button press reports a verification request but does not open a flow; the host must mount its own verification flow. The verification rows and capability list can be hidden independently.
Embedded identity verification
Embeds an individual KYC or business KYB flow that collects details, handles hosted verification and follow-up requests, and displays the result.
Lets a platform offer verification without building its own verification UI.
Mount KycElement inside Verifications. The page documents @whop/elements@1.10.0 and @whop/elements-react@1.10.0.
Embedded compliance requests
Displays outstanding account compliance requests and opens forms to answer them within an embedded verification interface.
Lets account holders address outstanding requirements without leaving the settings page.
Requests already with a reviewer are visible but cannot be answered; they can optionally be hidden. The element renders an all-clear when nothing is outstanding.
Embedded wallet activity
Displays an account’s ledger activity in an embedded wallet view, with filters and callbacks for selected rows.
Lets a platform show money movements and open its own detail screen when a viewer selects a row.
Mounts inside Wallet. For a scoped read, an account token needs company:balance:read and a user token needs user:balance:read; without a token, the viewer’s session works only same-origin.
Embedded wallet balances
Display an account’s balance history, holdings, and a per-currency breakdown of available, pending, reserve, and negative amounts in embedded wallet views.
Let users inspect what makes up their balance without building these views from scratch.
Mounts inside Wallet. Account balance reads require a scoped token with `company:balance:read`, or the viewer’s same-origin session. Reading a `user_` balance requires viewer authentication.
Embedded settlement details
Shows available funds, pending settlement dates, reserve terms, and any negative balance in a wallet balance details modal.
Lets users review settlement and reserve details without leaving an embedded wallet.
Requires a Wallet and Balances handle. Opens through createOverlay; it cannot be mounted inline.
Embedded balance conversion
Embeds a wallet flow for converting an account’s USD balance to Gold, Coinbase Wrapped Bitcoin, or a stock token, and back.
Lets customers convert balances within an embedded wallet.
Mounts inside Wallet. A cross-origin mount requires an access token scoped to company:balance:read and either crypto_wallet:swap or crypto_wallet:manage.
Embedded wallet deposits
Renders an embedded deposit flow with an amount field and available crypto and bank-transfer funding instructions.
Lets a platform present account funding options within its own page.
Personal-account funding rails require the account holder’s same-origin session or a scoped access token. Bank transfer may require identity verification. Card and platform-balance options are opt-in and require the host to handle the subsequent flow; the element does not collect card payments.
Embedded financial reports
Display balance history and financial activity in an embedded wallet, with filters, activity drill-down, and CSV exports.
Let users review balance movements and export the underlying activity without leaving the wallet interface.
Reports mounts inside Wallet. This page documents @whop/elements@1.10.0 and @whop/elements-react@1.10.0.
Embedded wallet transfers
Adds a send-money interface inside an embedded wallet for transfers to a user or another account, or for creating a redeemable claim link.
Lets people send funds without leaving the host app.
Mounts inside Wallet, inline or as a modal. Direct transfers require a token scoped to `payout:transfer_funds`; recipient lists, account recipient search, and claim links require their respective additional scopes. Disable actions the host is not authorized to offer.
Embedded wallet withdrawals
Embed a withdrawal flow that collects an amount and payout method, presents available standard and instant options with live fees and arrival estimates, and lets the user add a payout method when needed.
Let users review payout options and request a withdrawal within an embedded wallet.
WithdrawElement mounts inside Wallet and can be inline or modal. It can list methods and create the payout using a scoped access token or a same-origin viewer session. Alternatively, a host can supply payout data and create the payout after confirmation. Available methods, limits, and speeds depend on the account and payout destination.
Embedded website analytics
Shows an account’s whop.site websites and Whop Pixel-reported domains in an embeddable table with traffic, attributed sales, revenue, trends, and most-viewed pages.
Lets a platform show merchants website performance in its own interface.
Reading stats requires a scoped token with `stats:read`, except inside Whop’s own app where the viewer’s session carries the read. whop.site rows can appear before traffic arrives. Optional edit and settings buttons report clicks; the host page must provide the editing interface.
Embedded pixel setup
Embeds a wizard for installing the Whop Pixel, checking a page for it, and verifying conversion events.
Lets account owners set up and check pixel tracking within a website or campaign flow.
Mounts inside Websites, inline or as a modal. Scans require a scoped token with `company:basic:read`; additional paths and suggestions require the scopes documented for them. A completed wizard does not itself confirm that setup requirements are met.
Legal documents and checkout acceptance
Lets businesses upload terms of service, privacy policies, return policies, and EULAs to their Whop, and optionally require customers to accept terms before purchasing.
Customers can review the business’s policies and confirm agreement before checkout.
Terms acceptance must be enabled under Dashboard > Settings > Legal.
App organization
Group apps into categories and reorder apps and categories.
Make a product’s apps easier for members to navigate.
Apps can also be renamed. Members see only apps included in products they have joined or purchased.
Billing portal
Lets customers view membership details and billing history, update payment methods, and cancel or transfer memberships. Developers can link directly to a membership’s portal from an app, email, or customer dashboard.
Gives customers a self-service way to manage billing and memberships.
Customers can open the portal through Profile → Orders. The API’s manage_url is unique to each membership; users must log in to access it.
Embedded message search
Lets users search messages in a channel, DM, or support chat through an embedded interface.
Helps users find messages without leaving the embedded interface.
The documented SearchElement is legacy. For new integrations, use the search overlay in @whop/elements. The legacy element can be mounted in a container or shown as a modal, with a company or channel ID to scope the search.
Embedded element localization
Sets the locale for legacy Whop embedded components, controlling the language and formatting of text, dates, and numbers.
Helps embedded components fit supported audiences.
Set `locale` when initializing WhopElements. The documented default is `en`; supported values are `en`, `es`, `zh`, `nl`, `pt`, `de`, `hu`, `it`, `fr`, `ja`, `pl`, and `tr`. This legacy type reference does not change the availability of other Whop Elements.
3D Secure
Lets sellers turn on bank verification for card payments.
Helps reduce fraud reports and shifts liability for fraud disputes to the card issuer.
Turn it on under Settings → Risk.
Business category review
Classifies businesses at signup and re-checks their classification periodically and when their business or processing pattern changes. High-value or conflicting cases receive manual review.
Helps identify businesses that may need compliance review or documentation.
Restricted categories require prior approval and applicable licenses or certifications. If Whop cannot verify what a merchant sells, it pauses payouts and requests proof; a merchant who does not respond may be suspended.
Social apps and games
Offer interactive community experiences such as live trivia, video networking, anonymous forums, and giveaways through apps.
Give members ways to participate beyond courses and standard discussions.
Browse the community app category in the dashboard and activate the apps that fit the community.
App installation lifecycle
Sends app-specific events when an account installs or removes an app. Lets the app store an external ID and metadata on each installation and look up an installation by external ID.
Helps developers connect an installation to a record in their own system, stop access when the app is removed, and reconnect it after a reinstall.
Installation events go only to the app’s own webhook. The app needs the appropriate permissions to read or update installations. Do not store secrets in installation metadata or external IDs.
Direct file uploads
Creates a file record and provides presigned URLs for uploading bytes directly to Whop storage, including multipart uploads for large files.
Lets developers upload from a browser without routing file bytes through their server, then use the file ID where Whop accepts a document.
Requires API version 2026-08-21-1 or later. Poll until the upload is ready before using its ID. Multipart is required above 5 GB. Files are private by default; public files are cached and cannot be revoked.
Minimum balance retention
Set a minimum balance to keep in the account when configuring automatic withdrawals.
Keep funds available for refunds while using scheduled withdrawals.
Available with automatic withdrawals on a daily, weekly, or monthly schedule. Manual withdrawals do not support a minimum balance setting.
API request logs
Lists requests made to Whop’s API using an account’s API keys.
Helps developers review API activity when troubleshooting integrations.
The CLI has no sandbox or test mode; its commands run in production.
Embedded app purchases
Lets an embedded Whop app open Whop checkout for a one-time purchase or subscription through the iframe SDK.
Customers can start a purchase from within the app.
Create the checkout configuration on the server, open the payment modal with inAppPurchase, and validate the payment through webhooks before granting access.