Whop

Import customers and payments into Revenue → Payments, Customers and Attribution. Whop memberships do not expose a numeric renewal price on any public endpoint, so membership MRR is not imported — the same contract as the Lemon Squeezy connector. This connector is read-only.

1. In the Whop business dashboard open the developer settings and create an API key.
2. In Revenue → Connectors → Add a connector, choose Whop. Enter a label, the API key and the webhook signing secret (ws_… or whsec_…). Credentials are encrypted in the vault.
3. Copy the revealed URL into the company's webhook settings and enable the payment.* events: payment.created, payment.succeeded, payment.failed, payment.pending, payment.canceled.
4. Use Sync now, then inspect the last sync and event receipts. Verify a known payment and refund against Whop before relying on totals.

Signatures follow the Standard Webhooks scheme: webhook-id, webhook-timestamp and webhook-signature headers, HMAC-SHA256 over id.timestamp.rawBody, v1,<base64> signatures, five-minute replay tolerance. Webhooks.

Payments are keyed on the payment id. Whop reports money in major units (total: 6.9 is six dollars ninety), so amounts are rounded into cents. refunded_amount is cumulative on the payment object, so refund substatuses restate the stored row; paid becomes succeeded and void/unresolved become failed.

Sync pages /payments with the first/after cursor, filtered to the backfill window with created_after when one is set. Each payment carries its embedded user, which lands as the revenue customer.