Connections
Whop permissions LatchPay asks for
The required permissions that gate checkouts, the two optional ones for refunds and dispute evidence, and how to re-approve the app.
Updated
Two kinds of permissions
When you install the LatchPay app on your Whop business, Whop asks you to approve a set of permissions. LatchPay checks them on its side after the install and again on dashboard loads (cached for five minutes). The Whop page lists each one with a check or a cross.
Required: checkouts pause without them
Without every one of these, the connection stays at "install pending" and no checkout is created:
- payment:charge — create the buyer payment on your business
- developer:manage_webhook — register the webhook that reports payments, refunds and disputes
- webhook_receive:payments — receive payment events
- webhook_receive:refunds — receive refund events
- webhook_receive:disputes — receive dispute and pre-dispute alert events
- plan:create — create the hidden one-time plan that carries each order total
- payment:basic:read — read a payment back (status, refunded amount)
- member:basic:read — read the buyer record the payment created
- member:email:read — read the buyer email on payments and disputes
- payment:dispute:read — list chargebacks and inquiries for the Chargebacks page
- payment:dispute_alert:read — list pre-dispute alerts and early fraud warnings
Optional: only for what you switch on
These two move money or file documents on your behalf. Checkouts run without them; the dashboard only marks them as not granted and the feature that needs them stays off:
- payment:manage — refund a payment from LatchPay (the opt-in auto-refunds in Fraud & risk)
- payment:dispute — file dispute evidence from the Chargebacks page
Without payment:manage the automatic refunds in Fraud & risk cannot be switched on; you refund on Whop. Without payment:dispute the evidence form on Chargebacks is read-only and you file on Whop.
Re-approving the app
When LatchPay adds a permission to its app (the dispute reads were added with the Chargebacks page), every connected business has to approve the app once more. The dashboard shows a banner naming what is missing and a Re-approve on Whop link. Open it, approve the LatchPay app on the business again, then press Re-check on the Whop page.
- A required permission that is missing pauses checkouts until it is granted; buyers get Shopify's checkout meanwhile.
- A 401 or 403 from Whop on the re-check counts as "not installed": the connection goes back to install pending until you approve again.
- A network error keeps the connection as it was and is retried on the next check.