Help · Use Bearing
Revenue from Polar
Each payment and each refund of your Polar account in Bearing, with the source and the campaign of the visit it came from. Polar tells Bearing itself: nothing to code.
Bearing shows what you sell through Polar next to your visits, and for each payment the source and the campaign of the visit it came from: which post, which newsletter, which ad ends in a sale. Polar tells Bearing each payment itself, as it happens. You set it up once, in a few minutes.
What you need
- Bearing installed on the site where your checkout links are.
- Access to your Polar organization's Settings, on Polar itself, not on its sandbox (see below).
- Nothing to code when your site uses Polar's checkout links.
1. Copy the address in Bearing
- Open your site's Settings in Bearing, section Revenue (another payment system), and open Polar.
- Copy the address shown there. It belongs to this site only.
2. Have Polar tell Bearing
Polar calls it a webhook: an address it calls each time something happens in your organization. Here, that address is Bearing's.
- In Polar, open Settings → Webhooks and click Add Endpoint.
- URL: paste the address you copied. Format: Raw.
- Tick these events, and only these:
order.paid,order.refunded. API Version: choose2026-10. Leave the other fields as they are. - Save. On the endpoint's page, click Copy Secret: Polar makes the secret itself.
Polar's sandbox is separate, and nothing in its messages tells them apart from real ones: connect your Polar organization only, or test sales would count as real ones.
3. Paste the secret in Bearing
- Back in your site's Settings, under Polar, paste the secret in Signing secret and click Connect.
- From the next sale, the section says when the last message arrived.
How a sale finds its source
- A Polar Checkout Link: nothing to do. When a visitor clicks it on your site, Bearing adds the code of this visit to it, as
reference_id, and Polar gives the code back with the payment. If the link already carries areference_idof your own, Bearing leaves it: those sales count as Source unknown. - A checkout your developer creates through Polar's API: pass the visit token in
metadata.reference_id, as below. - Subscriptions: the first payment takes the source of the visit; the renewals keep the source of the customer's first payment.
- Without the code (a link shared outside your site, a script blocked), the sale is real revenue in Source unknown. Bearing never spreads it over your sources.
// In the browser, when the visitor starts to pay
const token = window.bearing && window.bearing.token ? window.bearing.token() : "";
// On your server, when you create the checkout session
// metadata: { reference_id: token }Try it without changing your numbers
Polar's sandbox cannot be used here (see above). Buy one of your products through a checkout link of your site, from a browser where you excluded your own visits, then refund it in Polar: 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, in full or in part, once you make it in Polar. Polar's refund form takes the amount before tax; Bearing takes off what the customer really got back, tax included.
- 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, Polar's reference for the order, 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 secret again in Polar and paste it.
- In Polar, the endpoint's page lists each delivery and can send one again. After ten failed deliveries in a row, Polar turns the endpoint off and tells you by email: turn it back on in Settings → Webhooks.
- Disconnect, in your site's Settings, makes Bearing forget the secret. Payments already recorded stay. Delete the endpoint in Polar too.