How to Set Up Paddle Webhook Notifications with Webhookify

Published Feb 21 202610 min read
Paddle webhook setup with Webhookify

Paddle is a complete payments infrastructure platform designed for SaaS companies, handling everything from checkout to subscriptions, invoicing, and global tax compliance. As a merchant of record, Paddle takes care of sales tax, VAT, and payment processing so developers can focus on building their product. Paddle webhooks are essential for keeping your application in sync with payment events -- knowing when a subscription is created, a payment succeeds or fails, or a customer requests a refund. With Webhookify, you can transform those Paddle webhook events into instant, AI-powered notifications delivered to Telegram, Discord, Slack, Email, or mobile push notifications. Hear a cash sound on your phone every time a new sale comes in.

This guide covers the complete setup process for connecting Paddle webhooks to Webhookify, so you get real-time alerts for every payment event without deploying custom webhook handler code.

Why Monitor Paddle Webhooks with Webhookify?

  • Instant Sale Notifications: Get an immediate push notification with a cash sound on your mobile device every time a new transaction completes in Paddle. Know the exact moment revenue hits your account, whether you are at your desk or on the go.

  • Subscription Lifecycle Tracking: Monitor the complete subscription lifecycle -- creation, updates, cancellations, and payment failures -- in real time. Get Slack or Discord alerts when a customer cancels so your retention team can follow up.

  • Payment Failure Alerts: Failed payments mean lost revenue. Webhookify notifies you instantly when a transaction payment fails, giving you the opportunity to reach out to the customer or investigate the issue before it compounds.

  • AI-Powered Revenue Summaries: Instead of reading through raw JSON containing product IDs, price objects, and currency codes, Webhookify's AI translates each event into a clear message like "New subscription: Pro Plan at $49/month from john@example.com."

  • No Backend Required: Normally, processing Paddle webhooks requires a server with an endpoint that validates signatures, parses payloads, and triggers actions. Webhookify handles all of this for you -- just paste a URL and start receiving notifications.

Prerequisites

  1. A Paddle account (Sandbox or Live). Sign up at paddle.com if you do not have one.
  2. At least one product or price configured in your Paddle catalog.
  3. A Webhookify account. Sign up for free at webhookify.app.
  4. A notification channel configured in Webhookify (Telegram bot, Discord webhook, Slack workspace, or Email address).
  5. Access to the Paddle Dashboard with permissions to manage Developer Tools settings.

Step-by-Step Setup Guide

1

Create a Webhookify Endpoint

Log in to your Webhookify dashboard at webhookify.app. Click the "Create Endpoint" button and give your endpoint a clear name like "Paddle Payments" or "Paddle Subscriptions."

Webhookify generates a unique HTTPS endpoint URL:

https://hook.webhookify.app/w/your-unique-endpoint-id

Copy this URL to your clipboard. This endpoint is active immediately and can receive webhook payloads from Paddle right away. All incoming requests are logged in real time on your Webhookify dashboard with full headers and body data.

2

Configure Your Notification Channel

Set up your preferred notification channels in Webhookify before connecting Paddle. Navigate to Settings in the Webhookify dashboard:

  • Telegram: Connect the Webhookify bot for instant personal alerts. Perfect for indie developers who want to hear their phone buzz with a cash register sound every time they make a sale.
  • Discord: Add a Discord webhook URL for team-wide payment notifications. Great for SaaS teams with a dedicated revenue channel.
  • Slack: Connect via the Webhookify Slack app or incoming webhook URL. Ideal for teams already using Slack for operations.
  • Email: Enter your email address for a written record of every payment event.
  • Mobile Push: Download the Webhookify app on iOS or Android. Enable the cash sound notification to hear a satisfying "cha-ching" with every successful payment.

For payment monitoring, mobile push with cash sound is especially popular among indie hackers and bootstrapped founders who love the dopamine hit of hearing a sale come in.

3

Set Up Webhooks in Paddle

Now configure Paddle to send webhook events to your Webhookify endpoint:

  1. Log in to the Paddle Dashboard.
  2. Navigate to Developer Tools > Notifications in the left sidebar.
  3. Click "New destination" to create a new webhook destination.
  4. Enter a description such as "Webhookify Notifications."
  5. In the URL field, paste your Webhookify endpoint URL.
  6. Select the events you want to receive (covered in the next step).
  7. Click Save destination.

If you are using Paddle's Billing (the newer API), the navigation may be slightly different:

  1. Go to Notifications in the Paddle dashboard sidebar.
  2. Click "New notification destination".
  3. Choose Webhook as the destination type.
  4. Paste your Webhookify URL and select your events.
  5. Save the configuration.

Paddle will begin sending webhook events to your Webhookify endpoint immediately for any of the selected event types.

4

Select Events to Monitor

Paddle offers a wide range of webhook events across transactions, subscriptions, and customers. Select the events most relevant to your business:

Transaction Events (Revenue Tracking):

  • transaction.billed -- A transaction has been billed and an invoice issued.
  • transaction.completed -- Payment has been successfully collected for a transaction.
  • transaction.payment_failed -- Payment collection failed for a transaction.
  • transaction.canceled -- A transaction was canceled.
  • transaction.ready -- A transaction is ready for fulfillment.

Subscription Events (Lifecycle Tracking):

  • subscription.created -- A new subscription has been created.
  • subscription.updated -- A subscription has been modified (plan change, quantity update, etc.).
  • subscription.canceled -- A subscription has been canceled.
  • subscription.paused -- A subscription has been paused.
  • subscription.resumed -- A subscription has been resumed from a paused state.
  • subscription.activated -- A subscription has moved to an active state.
  • subscription.past_due -- A subscription payment is past due.
  • subscription.trialing -- A subscription trial has started.

Other Events:

  • customer.created -- A new customer record has been created.
  • customer.updated -- Customer details have been updated.
  • adjustment.created -- A refund or credit adjustment has been issued.

For most SaaS businesses, enabling all transaction and subscription events is recommended so you have full visibility into your revenue pipeline.

5

Test Your Configuration

Paddle provides tools to test your webhook integration:

  1. In the Paddle Dashboard, navigate to Developer Tools > Notifications.
  2. Find your Webhookify destination and click on it.
  3. Use the "Send test notification" option if available, or use Paddle's sandbox environment to simulate a purchase.
  4. To test with a real-like scenario, create a test checkout using Paddle's sandbox mode and complete a purchase.

After triggering a test event:

  • Check your Webhookify dashboard to see the webhook payload logged in real time.
  • Verify that your notification channel (Telegram, Discord, Slack, or mobile) received the alert.
  • If you enabled the cash sound on mobile, you should hear it when a transaction.completed event arrives.

If the test is successful, your production setup is complete. Every Paddle payment event will now trigger an instant notification.

Paddle Webhook Events You Can Monitor

Here is the complete list of Paddle Billing webhook events that Webhookify captures and forwards:

  • transaction.billed -- Invoice issued for a transaction
  • transaction.canceled -- Transaction was canceled
  • transaction.completed -- Payment successfully collected
  • transaction.created -- New transaction created
  • transaction.paid -- Transaction marked as paid
  • transaction.past_due -- Transaction payment is overdue
  • transaction.payment_failed -- Payment attempt failed
  • transaction.ready -- Transaction is ready for fulfillment
  • transaction.updated -- Transaction details modified
  • subscription.activated -- Subscription is now active
  • subscription.canceled -- Subscription was canceled
  • subscription.created -- New subscription started
  • subscription.imported -- Subscription imported from another system
  • subscription.past_due -- Subscription payment is overdue
  • subscription.paused -- Subscription paused
  • subscription.resumed -- Subscription resumed after pause
  • subscription.trialing -- Subscription in trial period
  • subscription.updated -- Subscription modified
  • customer.created -- New customer record created
  • customer.updated -- Customer information changed
  • adjustment.created -- Refund or credit issued
  • adjustment.updated -- Adjustment details modified

Each event payload includes detailed information about the transaction amount, currency, customer details, product information, and subscription period.

Real-World Use Cases

  • Indie Hacker Revenue Alerts: As a solo founder, every sale matters. Configure Webhookify to send mobile push notifications with the cash sound for every transaction.completed event. You will know the instant someone purchases your product, complete with the customer's email and plan details.

  • Churn Prevention for SaaS Teams: Route subscription.canceled and subscription.past_due events to a dedicated Slack channel. When a customer cancels, your retention team gets an immediate alert with the customer's details and subscription history, enabling a timely follow-up.

  • Payment Failure Recovery: Monitor transaction.payment_failed events via Discord or Telegram. When a subscription payment fails, you can proactively reach out to the customer, update your dunning sequence, or flag the account for manual review.

  • Finance and Accounting Sync: Forward adjustment.created events (refunds and credits) to email for your finance team's records. This creates an automatic paper trail of all refunds processed through Paddle.

Example Notification

When a new subscription is created in Paddle, Webhookify delivers a notification like this:

{
  "event_id": "evt_01h8bkfmywq0abcde12345",
  "event_type": "subscription.created",
  "occurred_at": "2026-02-21T10:15:30.123456Z",
  "data": {
    "id": "sub_01h8bkfmywq0xyz98765",
    "status": "active",
    "customer_id": "ctm_01h8bkfmywq0customer1",
    "currency_code": "USD",
    "billing_cycle": {
      "interval": "month",
      "frequency": 1
    },
    "current_billing_period": {
      "starts_at": "2026-02-21T10:15:30.123456Z",
      "ends_at": "2026-03-21T10:15:30.123456Z"
    },
    "items": [
      {
        "price": {
          "unit_price": {
            "amount": "4900",
            "currency_code": "USD"
          },
          "description": "Pro Plan - Monthly"
        },
        "quantity": 1
      }
    ]
  }
}

Webhookify's AI summary would display:

New Paddle Subscription: Pro Plan - Monthly at $49.00/month. Status: active. Billing cycle: monthly. Next billing date: March 21, 2026.

This lets you immediately celebrate the new customer without diving into the raw payload.

Troubleshooting

  1. Paddle shows "Failed" status for webhook deliveries: Check that your Webhookify endpoint URL is correctly formatted and starts with https://. Paddle requires HTTPS endpoints. Also verify there are no extra spaces or characters in the URL.

  2. Events are received but notifications are not sent: Confirm that your notification channel is properly connected in Webhookify settings. Test the channel by clicking the "Send test notification" button in Webhookify to isolate whether the issue is with Paddle's delivery or your notification channel configuration.

  3. Missing some event types in Paddle dashboard: Depending on your Paddle version (Classic vs. Billing), the available events may differ. Make sure you are looking at the correct version's documentation. Paddle Billing (v2) has a different event structure than Paddle Classic.

  4. Webhook payload shows sandbox data in production: Ensure you configured the webhook in the correct Paddle environment. Sandbox and Live environments have separate webhook destination configurations. Check which environment you are logged into in the Paddle dashboard.

  5. Duplicate notifications for the same event: Paddle may retry webhook delivery if it does not receive a timely response. Webhookify responds quickly to prevent retries, but during rare network issues, you might see duplicate events. Each event has a unique event_id you can use to identify duplicates.

Use Paddle's sandbox environment to thoroughly test your webhook setup before going live. The sandbox lets you simulate purchases, subscription changes, and payment failures without processing real payments. Once you have verified everything works in sandbox, simply update your live environment with the same Webhookify endpoint URL.

Hear Your Paddle Sales in Real Time

Create a free Webhookify endpoint and get instant Paddle payment notifications with a cash sound on your phone, plus alerts on Telegram, Discord, and Slack.

Get Started Free

Related Articles

Frequently Asked Questions

How to Set Up Paddle Webhook Notifications with Webhookify - Webhookify | Webhookify