Bearing

Help · Use Bearing

Revenue: the payment providers Bearing follows

Every way Bearing can learn what your site earns and tie each payment to the visit it came from: Stripe, connected in two minutes, WooCommerce through the Bearing plugin, Lemon Squeezy, Paddle and Polar, which tell Bearing each payment themselves, and any other payment system through your site's server.

Bearing shows what your site earns next to its visits, and for each payment the source and the campaign of the visit it came from. That is how you know which post, which newsletter or which ad ends in a sale. Here is every way a payment can reach Bearing today, each with its guide.

  • Stripe. Paste a read-only key in your site's Settings: Bearing reads your payments itself, with nothing to code. Subscriptions, one-off sales and recurring revenue (MRR) included. A WooCommerce shop paid through the Stripe extension is read here too. Step-by-step guide
  • WooCommerce. Install the Bearing plugin for WordPress and paste a key: each paid order reaches Bearing with the visit it came from, whatever takes the payment (WooPayments, PayPal, Mollie, a bank transfer…). Nothing to code. Step-by-step guide
  • Lemon Squeezy. Paste an address in Lemon Squeezy and a secret in your site's Settings: Lemon Squeezy tells Bearing each sale and each subscription payment itself. Links to its checkout carry the visit by themselves. Nothing to code. Step-by-step guide
  • Paddle. Paste an address in Paddle and its secret in your site's Settings: Paddle tells Bearing each payment and each refund itself. To know which visit a sale came from, one line where your site opens Paddle's checkout, for a developer or the AI that writes your site's code. Step-by-step guide
  • Polar. Paste an address in Polar and its secret in your site's Settings: Polar tells Bearing each payment and each refund itself. Its checkout links carry the visit by themselves. Nothing to code. Step-by-step guide
  • Any other payment system. PayPal, your shop's own checkout, a platform that warns your site of each sale: your site's server tells Bearing each payment. For a developer, or for the AI that writes your site's code. Step-by-step guide

What is the same for all of them

  • A payment joins its visit, and nobody is followed. The link is a code made in the page's memory when the visitor starts to pay. It is not a cookie, nothing is stored on the visitor's device, and it says nothing about who they are.
  • A payment Bearing cannot tie to a visit is still counted, as Source unknown. It is real revenue: Bearing never spreads it over your sources.
  • Revenue starts where visits start: nothing dated before the first day Bearing measured your site, since it could be tied to no visit.
  • Never the buyer's name, email, address or card. Bearing keeps the amount, the currency, the date, what was refunded and the payment's reference.
  • Currencies are never added together.

One payment, one way in. If Bearing reads your Stripe account, or hears your payments from Lemon Squeezy, Paddle or Polar, do not also send those payments from your server: they would count twice.

What only Stripe gives today

Your recurring revenue (MRR) is worked out from the subscriptions Bearing reads in Stripe. A payment sent by your server, or told by Lemon Squeezy, Paddle or Polar, can say that it is a subscription's, and the Revenue card then counts it as such; it does not make an MRR.

Your payment system is not here?

If your site has a developer, or an AI that writes its code, your server can send its payments whatever took them. And tell us which system you use, at support@bearingstats.com: it helps us choose the next one to connect with nothing to code.