Whop Payment Gateway for WooCommerce — setup guide

1. Overview & requirements

This plugin puts Whop's card and crypto checkout inside your own WooCommerce checkout page. In the default Embed on Checkout mode the card fields render in your payment method box and WooCommerce's own Place Order button starts the payment flow. Test this normal path in your own theme.

You do not manually create or map Whop plans to WooCommerce products. The gateway creates a one-time Whop plan and checkout from the live order total, including quantities, coupons and shipping.

Requirements

2. Install the plugin

1. Download the ZIP

   After purchase, download the plugin ZIP from your Freemius account. Don't unzip it.

2. Upload it to WordPress

   Go to Plugins → Add New → Upload Plugin, choose the ZIP and click Install Now.

3. Activate

   Click Activate Plugin. A Whop entry now appears under your WooCommerce payment methods.

4. Enter your licence key

   You'll be prompted for the licence key from your Freemius receipt. This is what enables automatic updates — the gateway still works without it, but you won't get new versions.

3. Get your Whop credentials

The plugin needs an API key and Company ID first. You will add the webhook signing secret after creating the callback in step 5.

1. Create an API key

   In your Whop dashboard, open your developer / API settings and create a new API key for this store. Copy it immediately — most dashboards show a secret key once.

2. Copy your Company ID

   Your Company ID identifies which Whop company the payment belongs to. It's shown in your Whop company settings and typically looks like biz_xxxxxxxx.

3. Decide sandbox or live

   If you want to test first — and you should — use your sandbox credentials here and switch them out later at step 9.

4. Connect the gateway in WooCommerce

1. Open the gateway settings

   Go to WooCommerce → Settings → Payments, find Whop in the list and click Manage.

2. Paste your credentials

   Put the API key and Company ID from step 3 into their fields.

3. Set the title your customers see

   This is the label in the payment method list. Something plain like Credit card or crypto converts better than the word "Whop", which most of your customers won't recognise.

4. Enable the gateway and save

   Tick Enable, then Save changes. Leave sandbox mode on for now.

6. Choose a checkout mode

One dropdown, three payment experiences. You can change it whenever you like without touching your credentials, your webhook or any existing orders.

Which one should you pick?

All three modes use the same cart-derived payment and webhook verification. Their presentation differs: Embed on Checkout renders fields in WooCommerce, Popup opens an on-page modal, and Direct Redirect uses a Whop-hosted page. Test the mode you choose in your own theme.

7. Appearance & language

Making the form look like your store

The payment form is Whop's iframe, but you control how it presents itself:

• Theme — light or dark, with a high-contrast option where needed
• Accent colour — match your buttons and links
• Background colour — blend into your checkout panel
• Corner radius — match your theme's inputs so the fields don't look pasted in

Set these to your existing checkout styles and most customers won't register that the fields belong to a different system, which is the whole point.

Language

The payment form is available in 28 languages. Set one explicitly, or leave it on automatic to use the primary language from your WordPress site locale when that locale is supported.

On a multilingual store, test each translated checkout on staging. Automatic mode follows the WordPress site locale mapping; it is not browser or location detection.

8. Currency handling

47 listed store currencies are passed to Whop natively. For a store currency outside that list, the gateway converts the order amount to USD using a live rate with safeguards. Test the currencies that matter to your store in sandbox.

Testing this properly

1. Set your store currency to each one that matters commercially and place a sandbox order in each.
2. Confirm the amount and currency shown in the checkout match the path you expect. Test a zero-decimal currency such as JPY specifically.
3. Test a coupon and a shipping cost together, because that's where rounding errors surface.
4. Test one currency outside the native list and confirm the USD conversion behaves as you expect.

9. Test, then go live

Run a full sandbox order

Sandbox mode lets you exercise the checkout and order-confirmation path before real charges. Place a test order and check the parts that apply to your selected checkout mode:

1. The checkout appears in the expected place: embedded fields, popup, or hosted redirect.
2. The amount and currency match the cart path you tested, including coupons and shipping.
3. The signed payment.succeeded webhook moves the matching order to a paid status.
4. Your normal WooCommerce fulfilment behaviour occurs after payment.
5. Submit once with a deliberately invalid billing field and confirm validation fires before any charge.

Switching to live

1. Confirm HTTPS is active

   Live payments require it. Check the certificate covers the exact domain your checkout runs on, including or excluding www as appropriate.

2. Swap in your live credentials

   Replace the sandbox API key and Company ID with the live pair.

3. Register the matching live webhook and signing secret

   Make sure your live Whop endpoint and the signing secret saved in WooCommerce match the live environment before accepting real orders.

4. Turn sandbox mode off and save

   Place a small real order only after you have confirmed the live credentials and webhook are configured correctly. If you later refund a payment in Whop, record that operationally against the WooCommerce order as appropriate for your workflow.

10. Orders after payment

Order status

You choose what a paid order becomes:

• WooCommerce default — the normal behaviour, which is usually Processing for physical goods and Completed for downloads only
• Force Processing — when you fulfil manually and want everything queued
• Force Completed — when everything you sell is instant access

If you sell digital products and customers are waiting on a download, Force Completed is usually what you want.

When something goes wrong mid-payment

If a verified payment arrives before WooCommerce can match it to an order, the gateway records it for review in its status tools. Review and reconcile these entries promptly; payment checkout and third-party fulfilment are separate responsibilities.

Refunds

Refunds are issued from your Whop dashboard, since that's where the funds sit. Record the refund against the WooCommerce order afterwards so your reports stay accurate.

11. Settings reference

Every setting on the gateway screen, and what it actually affects.

12. Troubleshooting

Ordered roughly by how often each one actually happens.

Before you open a ticket

These four details get your issue resolved on the first reply instead of the third:

1. WordPress, WooCommerce, PHP and plugin versions.
2. Sandbox or live, and which checkout mode.
3. Classic checkout or the Checkout Block.
4. What you expected, what happened, and the order number. Never send your API key.