Help · Use Bearing
Revenue from Paddle
Each payment and each refund of your Paddle account in Bearing, with the source and the campaign of the visit it came from. Paddle tells Bearing itself; one line of code joins each sale to its visit.
Bearing shows what you sell through Paddle next to your visits, and for each payment the source and the campaign of the visit it came from. Paddle tells Bearing each payment itself, as it happens. This guide is for Paddle Billing, today's Paddle; Paddle Classic is not supported.
What you need
- Bearing installed on your site.
- Access to your live Paddle account, not the sandbox (see below).
- To know which visit each sale came from: one line of code where your site opens Paddle's checkout, for a developer or for the AI that writes your site's code (step 4).
1. Copy the address in Bearing
- Open your site's Settings in Bearing, section Revenue (another payment system), and open Paddle.
- Copy the address shown there. It belongs to this site only.
2. Have Paddle tell Bearing
Paddle calls it a notification destination, a webhook: an address it calls each time something happens in your account. Here, that address is Bearing's.
- In Paddle, open Events, then Notifications, and click New destination.
- Description:
Bearing. Notification type: webhook. URL: paste the address you copied. - Usage type: Platform only, so that only real events are sent.
- Tick these events, and only these:
transaction.completed,adjustment.created,adjustment.updated. Leave API version as it is. - Save, then copy the destination's secret key: it begins with
pdl_ntfset_. If Paddle no longer shows it, open the menu next to the destination, then Edit destination.
Paddle's sandbox is a separate account, and nothing in its messages tells them apart from real ones: connect your live account only, or test sales would count as real ones. For the same reason, never send Paddle's simulations to this address.
3. Paste the secret in Bearing
- Back in your site's Settings, under Paddle, paste the secret key in Signing secret and click Connect.
- From the next sale, the section says when the last message arrived.
4. Join each sale to its visit
Paddle's checkout opens from your site's code, so that is where the code of the visit is handed to it. One line, for a developer or for the AI that writes your site's code:
// Where your site opens Paddle's checkout
const token = window.bearing && window.bearing.token ? window.bearing.token() : "";
Paddle.Checkout.open({
items: [{ priceId: "pri_…", quantity: 1 }],
customData: token ? { bearing_token: token } : undefined,
});- A button that opens the checkout through Paddle's HTML attributes: set its
data-custom-datato{"bearing_token": "…"}, with the token, before the click. - Paddle copies it to the subscription: the renewals keep the source too.
- Without it, every sale is still counted, as Source unknown. Bearing never spreads it over your sources.
Try it without changing your numbers
Paddle's sandbox cannot be used here (see above). Once the line of step 4 is in place, buy one of your products from a browser where you excluded your own visits, then refund it in Paddle: it is a real payment. That browser's code says so, and the sale reaches Bearing as a try: nothing is counted, and your site's Settings show try received under Revenue (another payment system).
What is counted, and what is not
- The amount is what the customer paid, tax included, in the currency they paid in. Currencies are never added together.
- A refund is taken off once Paddle has approved it: Paddle reviews most refunds first.
- Subscriptions and one-off sales are told apart in the Revenue card.
- Nothing from before the first day Bearing measured your site: such a sale could be tied to no visit.
- Payments do not count toward your plan.
- Never the buyer's name, email, address or card. Bearing keeps the amount, the currency, the date, what was refunded, Paddle's reference for the transaction, and a one-way fingerprint of its customer number, to recognise two payments of the same customer.
Your recurring revenue (MRR) is still worked out from Stripe only. And one payment, one way in: do not also send these sales from your site's server, they would count twice.
If nothing arrives, or to stop
- Your site's Settings say when the last message arrived, and when one was refused because the secret does not match: copy the destination's secret key again and paste it.
- In Paddle, the destination's logs show each message and each attempt. Paddle tries again for about two days when Bearing cannot be reached.
- Disconnect, in your site's Settings, makes Bearing forget the secret. Payments already recorded stay. Delete the destination in Paddle too.