Integrations
Connect Paddle revenue
Verify Paddle payments, adjustments and refunds for one Premely site.
- Paddle
What it is
The Paddle connection receives signed Paddle webhooks and records supported commercial events for the selected Premely site.
Why use it
Use Paddle revenue with traffic reports and goals when Paddle is the source of truth for completed payments and adjustments.
Before you start
- You need owner or admin access in the Premely workspace.
- You need permission to create a notification destination in Paddle.
- Choose Test or Live to match the Paddle environment you are connecting.
How to use it
- 1
Reserve a webhook URL in Premely
Open your site's Settings, choose Integrations, find Paddle and choose Connect. Select Test for a Paddle sandbox account or Live for your live account, then choose Create Paddle endpoint. Copy Webhook URL and keep this dialog open. Paddle supplies the signing secret in a later step.
Reserve the Premely URL, add the destination in Paddle, then paste Paddle's endpoint secret back into Premely. Shown in Premely with disposable demo data; your values will differ.
- 2
Add the destination in Paddle
In the matching Paddle account, open Developer tools, then Notifications and New destination. Enter a description such as Premely revenue, choose Webhook as the notification type, and paste the Premely Webhook URL into URL. Use platform events for live payments; enable simulation events only when testing.
- 3
Select supported events
In the destination's event list, select
transaction.completed,adjustment.createdandadjustment.updated, then choose Save destination. - 4
Copy Paddle's secret back into Premely
Copy the endpoint secret for that Paddle destination. Return to the Premely dialog, paste it into Provider signing secret, then choose Activate Paddle revenue. Do not use a Paddle API key or a secret from a different destination.
Paste the endpoint secret from Paddle, then activate the connection. Do not paste a Paddle API key. Captured from the real Premely interface using disposable local-review values. Example URLs and credentials cannot be used for a real connection.
- 5
Verify the first event
For a Test connection, send a supported event through the Paddle sandbox destination. For Live, wait for a supported live payment or adjustment. Reopen Paddle in Premely and check Last verified event. If it still says Waiting for first event, check the destination URL, environment, subscribed events and secret before trying again.
Check Last verified event after a supported payment or adjustment. This example is configured but still waiting; Connected alone does not verify delivery. Captured from the real Premely interface using disposable local-review values. Example URLs and credentials cannot be used for a real connection.
What to expect
Check the site and environment
Each connection sends revenue to one Premely site. A Test connection does not verify a Live connection. Keep the provider environment and the Premely mode the same throughout setup.
Currencies stay separate
Premely does not silently combine or convert different currencies. Provider revenue appears in Revenue and Revenue / Visitor only in its valid currency context.
Revenue and visitor attribution are separate
A verified payment can appear in revenue without being linked to a visitor. Premely shows the visitor link only when the payment carries matching Premely attribution data.
Duplicate deliveries do not duplicate revenue
If the provider retries the same event, Premely does not count it as another payment.
Use the destination's signing secret
Paddle issues the signing secret. The URL comes from Premely, but the secret must be copied from the matching Paddle destination back into Premely.
Useful ways to apply this
Subscription and adjustment reporting
Review completed Paddle transactions and supported adjustments beside traffic and goals for the selected site.