Built on Whop
We are not a payment company, and that is the point.
Whop processes the payments, holds the plans, bills the subscriptions, executes the refunds, collects the tax and pays you out. Chekvo is everything between you and that infrastructure — and everything between your customer and that payment element.
The split
Who owns what.
| Capability | Whop | Chekvo |
|---|---|---|
| Card capture, wallets, 3DS | Source of truth, in their frame | Never touches it |
| Payment processing & status | Source of truth | Mirrors and presents it |
| Payment methods available | Source of truth | Per-checkout configuration |
| Plans and pricing objects | Source of truth | Created per checkout, managed here |
| Subscription billing | Billing engine | The book, MRR, churn, controls |
| Card retries & dunning | Entirely theirs | Reflects it; never runs its own |
| Refunds | Executes them | Initiates, records, mirrors to your store |
| Payouts, tax, chargebacks | Entirely theirs | Surfaces them |
| The checkout page | Payment element only | OursThe whole page around it |
| Checkout builder | — | OursOurs. The core product |
| Buy Links | A bare purchase URL | OursNamed, tracked, attributed, expirable |
| Orders & customers | Payment records | OursNormalised model, profiles, LTV |
| Analytics | Raw commerce data | OursFunnel, offers, links, cohorts |
| Shopify | Not involved | OursCatalogue in, order back |
| Workspace, roles, audit | — | OursEntirely ours |
The rule we hold ourselves to: if Whop has an opinion about it, Whop wins and we project. If it is presentation, merchandising, workflow or measurement, it is ours.
Integrity
Whop is authoritative, so we can prove agreement.
A signed event, or nothing
Your browser saying “payment complete” is a hint, not proof. An order exists only when a signature-verified webhook from Whop says so.
Recorded once, by construction
Every event carries a unique id under a database constraint. A redelivered webhook is rejected by Postgres, not by code that has to remember.
Reconciled nightly
We list payments directly from Whop and diff them against our orders. Whop wins every conflict, and drift becomes a work queue instead of a surprise.
Connecting
One approval screen. No secrets.
You install Chekvo onto your Whop company and approve a permission list. We register the webhook endpoint ourselves and verify the connection before it is marked live. There is no API key to copy, no event list to tick, and no dummy product to create as an “order bucket”.
What we ask for
Create a checkout so your customer can pay · read your products and plans · read payments so orders and analytics stay accurate · cancel a subscription when asked.
What we cannot do
Withdraw or move your money · change your payout bank · delete your products or company · see a card number. Revoke us in Whop at any time.
Try the whole path before connecting anything.
A simulated Whop company lets you walk checkout, payment, webhook and order end to end — then connect your real account when you are satisfied.