Whop payment integration: connect Whop checkout to WooCommerce

A Whop payment integration has three moving parts: your server creates something to pay for (a plan or checkout configuration) with a secret API key, the browser shows Whop’s checkout, and your server waits for the signed payment.succeeded webhook before delivering. On WooCommerce, WhopForWoo wires those three parts to WooCommerce orders, so you configure it instead of coding it.

The integration flow

Customer        WooCommerce + WhopForWoo            Whop
   |  fills checkout  |                                |
   |----------------->| creates pending order          |
   |                  |-- checkout configuration ----->|  (exact total, order metadata)
   |  Whop form       |<------------- config id -------|
   |<-----------------| mounts Whop Elements           |
   |  pays (card / Apple Pay / Google Pay) ----------->|
   |                  |<--- payment.succeeded (signed)-|
   |                  |-- GET /payments/{id} --------->|
   |                  | checks order, amount, currency |
   |  thank-you page  | marks order paid (once)        |

Step by step on WooCommerce

1. Set up Whop Payments. In Whop, go to Balances and set up Whop Payments: choose your payout country, complete KYC (personal details, bank account, ID upload).

2. Create an API key. Whop dashboard → developer settings. Note your Account ID (it starts with biz_). Keep the key on the server: WhopForWoo stores it in WordPress settings and never sends it to the browser or writes it to logs.

3. Install WhopForWoo and open WooCommerce → Settings → Payments → Whop. Paste the API key and Account ID.

4. Add the webhook. The settings page shows your endpoint (https://yourstore.com/?wc-api=whop_webhook). In Whop, create a webhook to that URL, subscribe to payment.succeeded, then paste the webhook secret back into the plugin.

5. Choose the checkout mode. Whop Elements (embedded, recommended) or hosted redirect. The Checkout Block always uses the hosted redirect.

6. Test in sandbox. Switch Sandbox mode on, use sandbox keys, place an order, check that the order turns paid and that the webhook appears in Status & Tools → webhook history.

7. Go live. Swap in production keys and the production webhook secret, disable sandbox.

What a safe Whop checkout integration checks

Whop’s guide is clear that the return URL is not proof of payment. WhopForWoo marks an order paid only when all of these hold:

On any mismatch the order goes on hold with a note. A payment charged without a matching order is listed in Status & Tools with its payment ID so you can create the order or refund it in Whop.

Integration details worth knowing

• API version pinned. Requests send a dated Api-Version-Date header, as Whop recommends, so a Whop API change doesn’t silently alter behaviour.
• Idempotency keys on creation calls prevent double configurations on retries.
• Currencies. 47 are charged natively; other store currencies are converted to USD at a live rate from open.er-api.com, with a sanity check on the rate.
• Outbound connections: only api.whop.com and the exchange-rate API. Browsers load Elements from cdn.whop.com.