Skip to content
HookWatch beta
FeaturesUse casesPricingQuickstartSecurityCompare
Resources
Resources overviewGuidesIntegrationsComparisonsChangelogDocumentationMCP server
Sign in Start beta
Changelog v1.4.0 New

Paddle Billing and plan enforcement

Overlay checkout through Paddle, subscription sync from verified Paddle webhooks, and endpoint-limit enforcement on paid plans.

Published 1 min read
On this page

Billing goes live in this release. Workspaces can now subscribe to a plan through Paddle, and the plan a workspace holds is kept in step with Paddle’s own state rather than set by hand.

Added

  • Overlay checkout — the billing tab opens Paddle’s overlay checkout to start a subscription, and supports changing or cancelling it in place. The flow handles Paddle initialisation failures, checkout poll timeouts, and double-submits.
  • Webhook plan sync — Paddle webhooks are signature-verified before they are trusted, then parsed and applied to keep each workspace’s subscription and plan accurate. Subscriptions upsert on workspace so a cancel-then-resubscribe settles on the correct owner.
  • Plan enforcement — the endpoint limit is enforced on creation, including on a duplicate path, returning 409 when a workspace is at its plan’s limit. Event overage is softly enforced with a dashboard banner and an hourly nudge email.

Improved

  • The admin panel received a UI and UX pass alongside the billing work.

HookWatch is in beta; see the pricing page for current plans.

Notes

Release date comes from the v1.4.0 git tag (9 July 2026).

Related resources

Changelog v1.17.0 MCP server and HTTP API docs The whole workspace API is exposed as roughly 48 MCP tools for AI assistants, alongside new public documentation for the HTTP API and MCP. 1 min read Changelog v1.18.0 Workspace SSO and inactivity timeout Single sign-on through your own SAML 2.0 or OIDC identity provider, with an optional Require SSO enforcement and a session inactivity timeout. 1 min read Changelog v1.19.0 Overage pricing on metered usage Paid plans can now run past their included usage with metered overage, with projected charges surfaced in billing settings before they land. 1 min read
Get started

See what happened to every webhook.

HookWatch keeps the request, the response, and every attempt for each delivery — so the debugging, retry, and replay steps in this article are a matter of reading, not reconstructing.

Start using HookWatch Read the documentation