# Whop for SaaS: sell software with Whop license keys

> Whop for SaaS explained: access checks for web apps, license keys for downloadable software, and how we license our own WordPress plugin with Whop.

Updated: 2026-11-11 · Canonical: https://whopforwoo.com/whop-for-saas

**Whop can run billing for a SaaS: it handles checkout, subscriptions and payments, and your app asks Whop whether a customer has access.** For downloadable software, Whop also issues a unique license key per purchase, which your server can validate through the API.

We use this ourselves. WhopForWoo is sold on Whop, and the license key you receive at purchase is a Whop license key. This page explains both SaaS models and where a WooCommerce store fits, honestly: often it doesn't need to.

## Two SaaS models on Whop

| | Access check | License keys |
|---|---|---|
| Best for | Web apps where users sign in | Desktop apps, scripts, plugins users download |
| Identifies the customer | Whop user ID stored on your user record | License key issued with each purchase |
| Server calls | `users.checkAccess` | `memberships.retrieve`, `memberships.update` |
| Lock to one machine | No | Yes, a hardware ID in membership metadata |

### Web app: access check

Whop's SaaS guide: create a checkout configuration from your server with your own user ID in `metadata`, redirect to the `purchase_url` (or embed the Checkout element), listen for `membership.activated` on a signed webhook to store the buyer's Whop user ID, then call `checkAccess` before serving paid features. Renewals, cancellations and refunds are reflected in the answer, so you don't track billing state yourself.

### Downloadable software: license keys

1. Install Whop's **Software** app on the product and add the software name and download link. Buyers then see the key and download in their orders. The API returns `license_key` only for products with this app.
2. Your software sends the key and a machine identifier to **your server**.
3. Your server calls retrieve membership with the key ("Retrieve accepts a license key in place of a membership ID"; unknown keys return 404), checks the status (Whop's example accepts `active`, `trialing`, `completed`), and binds a `hwid` in metadata on first use.
4. Customers can reset their key from their orders; your server can reset it by updating metadata to `{}`.

Never ship the Whop API key inside the software: it can read and change every membership in your business.

![Whop Software app settings with software name and download link](https://whopforwoo.com/img/whop-software-app.png)

## How we license WhopForWoo with Whop

Our license server is a small Worker. When you activate WhopForWoo on a site, the plugin sends the key and site URL to our server; the server checks the membership with Whop's API (our API key stays there) and stores the activated sites in the membership metadata. Plans map to site limits: 1, 5 or unlimited. Without an active license the Whop payment method turns off after reminders and a 14-day grace period; one-time plans never expire. A worked guide is in [Whop license keys](https://whopforwoo.com/docs/whop-license-keys).

## Where WooCommerce fits

WhopForWoo is a WooCommerce payment gateway that charges **one-time** payments for WooCommerce orders. It makes sense for a SaaS when:
- you already sell through a WooCommerce store (for example WordPress plugins, themes, templates, or one-time software licenses);
- you want Whop as the processor and WooCommerce as the storefront, coupons and tax engine.

It is the wrong tool when you need monthly or yearly subscriptions billed automatically: WhopForWoo does not do recurring billing through WooCommerce Subscriptions. Use Whop's recurring products with checkout links or the embedded Checkout element instead, and gate access with the check above. See [Whop subscriptions on WooCommerce](https://whopforwoo.com/whop-subscriptions-woocommerce).

## Pros and cons of Whop for SaaS

**Pros**
- License keys built in, no separate licensing service.
- Subscriptions, trials, promo codes and a billing portal where customers update payment methods and cancel.
- Signed webhooks (Standard Webhooks, HMAC-SHA256) and a sandbox for testing.
- Affiliate program built in (Whop's global affiliates default to 30% commission).

**Cons**
- Card fees start at 2.7% + $0.30, plus 1.5% for international cards and 1% for conversion. Compare with [Whop vs Stripe](https://whopforwoo.com/whop-vs-stripe).
- Whop requires every offer to disclose its access period, so open-ended "forever" deals are out; sell a "one-time payment" with a stated access or update period.
- New accounts can face reserves, and access depends on Whop keeping your account in good standing.
- Membership metadata is merged on update and has size limits, so design your activation data compactly.
- Hacking tools, data-scraping tools, game cheats and fake-engagement software are prohibited. Whop decides eligibility.

Get WhopForWoo: https://whopforwoo.com/pricing

## FAQ

### Can Whop be used for SaaS?

Yes. Whop documents two SaaS integrations: an access check for web apps where users sign in, and license keys for software that runs on the customer's machine. Whop handles checkout, billing and subscription management.

### Does Whop generate license keys?

Yes, when the product includes Whop's Software app. Each purchase comes with a unique license key, and the API's retrieve-membership call accepts the license key in place of a membership ID.

### Can I sell a WordPress plugin or theme with Whop?

Yes. We do it: WhopForWoo licenses are Whop license keys, validated by our own license server with Whop's API. The plugin never contains a Whop API key.

### Should a SaaS use WhopForWoo?

Only if you sell through a WooCommerce store. WhopForWoo takes one-time WooCommerce payments; a subscription SaaS is usually better served by Whop checkout links or the Checkout element directly.

## Related

- [Whop license key API: how to validate software licenses](https://whopforwoo.com/docs/whop-license-keys): How the Whop license key API works: the Software app, memberships.retrieve with a license key, machine binding with metadata, resets, server-side checks.
- [Whop API: how it works and how WooCommerce uses it](https://whopforwoo.com/docs/whop-api): Whop API explained: base URL, Bearer auth, dated versions, rate limits, pagination and webhooks, plus the calls a WooCommerce store needs to take payments.
- [Whop webhook: setup, payment events and webhook secret](https://whopforwoo.com/docs/whop-webhooks): Set up a Whop webhook for WooCommerce: endpoint URL, payment.succeeded event, where to get the webhook secret, signature checks, retries and testing.
- [Whop subscriptions and memberships on WooCommerce](https://whopforwoo.com/whop-subscriptions-woocommerce): Can you sell Whop subscriptions or memberships from WooCommerce? What WhopForWoo does (one-time payments), what it doesn't, and three setups that work.
- [Whop for digital products: sell downloads from your WooCommerce store](https://whopforwoo.com/whop-for-digital-products): How to use Whop to sell digital products from WooCommerce: embedded Whop checkout, card, Apple Pay and crypto, honest pros and cons, setup in 5 steps.
- [Whop vs Stripe: fees, payouts and tax compared for a WooCommerce store](https://whopforwoo.com/whop-vs-stripe): Whop vs Stripe: 2.7% + $0.30 vs 2.9% + $0.30, merchant of record vs your own account, tax, payouts and disputes. Worked examples for a WooCommerce store.