T
Théo JUSTINE
Whop now documents a GoHighLevel payment-provider integration for checkout pages, payment links, invoices and subscriptions. I would like this request to also cover a clearly supported, first-class Whop connection at two distinct levels:
- Agency billing: let the agency connect its own Whop business directly from the agency payment/SaaS settings, with an onboarding experience comparable to connecting Stripe. Explicitly document and support the SaaS subscription lifecycle, successful-payment provisioning, renewals, failed payments and cancellations, plus wallet/rebilling features where supported.
- Independent sub-account payments: let each sub-account connect its own Whop business and receive its own customers’ payments. The agency’s merchant account and each client’s merchant account must stay separate, with clear permissions and routing.
In both cases, keep HighLevel payment links, invoices and checkout flows, with payments recorded in Transactions and the relevant payment/subscription events available to workflows. Clearly show which recurring and off-session operations are supported, and protect existing subscriptions from duplicate billing during any migration.
HighLevel already documents Custom Payment Providers in SaaS Mode. If Whop supports some of this through that route today, please make that compatibility explicit in the interface and documentation. The goal is a reliable, easy-to-configure integration across agency and sub-account use cases.
A
Ans Jk
I agree esspecially since Stripe freazes funds