Does ProductLense work with Paddle?

Yes. ProductLense connects to Paddle with aPI key, webhook secret key, backfills 12 months of history, and stays current through signed webhooks plus a nightly reconcile. One connection is included on Starter; Growth and Scale allow every provider at once on the same site.

What data does ProductLense read from Paddle?

Customers, subscriptions, payments, refunds and fees, read-only. Payments: completed transactions. Refunds: refund and chargeback adjustments. Fees: grand total minus earnings: Paddle’s cut and tax, so net revenue equals your payout.

Can ProductLense change anything in my Paddle account?

No. ProductLense only makes read calls and receives webhooks. It never creates, changes, refunds or cancels anything, never moves money, and never sees card numbers. Credentials are encrypted at rest, and the AI features only ever see aggregated numbers, never your customers’ data.

How does ProductLense match Paddle payments to visitors?

Set custom_data.pl_user_id on the Paddle customer to the id you pass to identify for the strongest match; otherwise ProductLense matches by email. Your site calls identify with the same user id after signup, and ProductLense follows the payment to that visitor’s first touch: source, medium, campaign and landing page.

Paddle analytics: see revenue and profit by channel

Paddle is a merchant of record: it sells to your customer, collects and remits sales tax and VAT, and pays you the rest. ProductLense records the amount the customer paid and the part the merchant of record kept as the fee, so profit is based on what reaches you.

Setup steps

In Paddle, open Developer tools → Authentication and create an API key with read access.
In ProductLense, open Settings → Billing connections → Paddle and paste the key.
In Paddle → Developer tools → Notifications, add a webhook endpoint with the URL ProductLense shows after you save the connection (pattern https://api.productlense.app/api/webhooks/{provider}/{connection_id}).
Subscribe the destination to the events listed below and paste the secret key into ProductLense.
ProductLense backfills 12 months of transactions and adjustments.

Credentials and permissions

Credentials ProductLense asks for
Field	Secret	Where to find it
API key	Yes, encrypted at rest	Paddle → Developer tools → Authentication. Needs read access to customers, subscriptions, transactions and adjustments.
Webhook secret key	Yes, encrypted at rest	The pdl_ntfset_... key shown when you create the notification destination pointing at ProductLense.

Webhook

URL pattern, shown with your connection id after you save:

text

https://api.productlense.app/api/webhooks/paddle/{connection_id}

Events: transaction.completed, transaction.updated, adjustment.created, adjustment.updated, subscription.created, subscription.updated, subscription.canceled, customer.created, customer.updated

Verification: Paddle-Signature header: timestamp plus h1 HMAC-SHA256, rejected after 5 minutes.

What ProductLense reads

Customers: Customers with email and custom data.
Subscriptions: Subscriptions with status and billing interval.
Payments: Completed transactions.
Refunds: Refund and chargeback adjustments.
Fees: Grand total minus earnings: Paddle’s cut and tax, so net revenue equals your payout.

What ProductLense never touches

Never creates, changes, refunds or cancels anything: read-only API calls and incoming webhooks only.
Never moves money, issues payouts, or reads bank account details.
Never sees full card numbers; providers do not expose them.
Never sends your customer data to the AI model: Ask and the daily insight see aggregates only.

Match payments to your users

Set custom_data.pl_user_id on the Paddle customer to the id you pass to identify for the strongest match; otherwise ProductLense matches by email.

server: create the Paddle customer

await fetch('https://api.paddle.com/customers', {
  method: 'POST',
  headers: { Authorization: `Bearer ${process.env.PADDLE_API_KEY}`, 'Content-Type': 'application/json' },
  body: JSON.stringify({ email: user.email, custom_data: { pl_user_id: user.id } }),
});

Paddle and ProductLense: questions

Does ProductLense work with Paddle?: Yes. ProductLense connects to Paddle with aPI key, webhook secret key, backfills 12 months of history, and stays current through signed webhooks plus a nightly reconcile. One connection is included on Starter; Growth and Scale allow every provider at once on the same site.
What data does ProductLense read from Paddle?: Customers, subscriptions, payments, refunds and fees, read-only. Payments: completed transactions. Refunds: refund and chargeback adjustments. Fees: grand total minus earnings: Paddle’s cut and tax, so net revenue equals your payout.
Can ProductLense change anything in my Paddle account?: No. ProductLense only makes read calls and receives webhooks. It never creates, changes, refunds or cancels anything, never moves money, and never sees card numbers. Credentials are encrypted at rest, and the AI features only ever see aggregated numbers, never your customers’ data.
How does ProductLense match Paddle payments to visitors?: Set custom_data.pl_user_id on the Paddle customer to the id you pass to identify for the strongest match; otherwise ProductLense matches by email. Your site calls identify with the same user id after signup, and ProductLense follows the payment to that visitor’s first touch: source, medium, campaign and landing page.
How are Paddle fees and taxes handled?: Paddle is a merchant of record: it sells to your customer, collects and remits sales tax and VAT, and pays you the rest. ProductLense records the amount the customer paid and the part the merchant of record kept as the fee, so profit is based on what reaches you. Grand total minus earnings: Paddle’s cut and tax, so net revenue equals your payout.

Connect Paddle and see revenue by channel today.

Add the script, connect Stripe or any of 14 other billing providers, and see revenue by channel the same day.

Start free Read the docs →