Edited by Tejas Telkar · Published · Updated
Short answer
Open NotchPop Revenue, select Polar and connect an organization access token with organizations:read and orders:read access. Enter the organization ID if your setup requires it. Read paid-order information alongside currency and sync status, then use the original Polar order for a detailed reconciliation.
Use an organization token with the needed scope
Polar's Organization Access Tokens belong to an organization and receive selected scopes. In the intended organization's settings, open Developers and create a token with an appropriate name, expiration and permissions. NotchPop lists organizations before reading orders, so provide organizations:read and orders:read access for those calls.
The app's Polar form asks for the organization access token and offers an organization ID field. Match these to the business you want to view. An access token from another organization can be valid on its own while still being the wrong source for the revenue you expected.
The token is a private credential. Paste it into the connection form and keep it out of screenshots, chat messages and source code. NotchPop stores connected credentials in Keychain; if you replace or revoke a token at the provider, revisit the corresponding connection.
Read orders with their currency and refund context
The supported Polar calculation uses paid orders. For the order amount, it uses the available net amount or total amount and accounts for the refunded amount without turning the resulting contribution negative. That describes this app's reading; it should not be relabeled as a provider invoice, bank payout or independently reconciled profit.
When an amount changes, inspect the original order and refund information before assuming a display fault. Currency and dates are part of the reading, not decoration. A cross-provider Total can require conversion and have different freshness from the separate Polar view.
Check organization, access and freshness
- Select Polar in Revenue and connect the organization token.
- Confirm the organization ID when supplied.
- Refresh and read the provider's sync result and timestamp.
- Compare a recent paid order with the corresponding Polar record before relying on the overview.
A rejected-token or missing-scope error is a connection problem. Check the token's organization, expiration and both read permissions rather than treating an unavailable reading as zero orders. Wait for a successful fetch before describing the result as current.
If you use several providers, the Dodo payment guide explains a payment-list source, while the Stripe guide separates charge activity from balances. The currency converter guide explains why an indicative conversion is distinct from an actual settlement rate.
Sources and editorial notes
Published by NotchPop, the maker of the app. macOS instructions and third-party claims are linked to the sources below. Settings and offers can change between versions. Read our editorial approach or send a correction.
