Polar on X

Praise is what most people in the section post. Users credit Polar's MCP server with cutting a coding task from 3.7 million tokens to 160k, credit it with showing location-based tax at checkout so a $150 license stays $150 for buyers outside North America, and one thanks it for approving an account in under 10 minutes. Founders say they run their paid plans on it, an agency says open-source billing is easier to sell, and replies recommend it to people picking a provider or thinking of leaving.

7 people like the small touches instead: the "Last Used" tag on sign-in pages and the notifications, one saying they picked Polar purely for the notification style. One finds the tag pointless when Gmail is the only sign-in.

6 are disappointed — over support that went quiet, a policy update one calls "a joke", a deprecated Go SDK that forced a move to the API directly, and an account closed without an email. 2 users are weighing whether to stay, naming Creem and Dodo Payments.

Support complaints are about silence: a startup plan application sent "a few weeks ago" with no response, a public "support can you reply?", a six-day unresolved issue, and one who chatted with the CEO only for the replies to stop.

The logo change caused alarm as much as dislike. A payments user saw the different dashboard and "genuinely thought my money was gone for a second"; another asks why it changed and a third asks for the old one back.

Accounts and payments are being refused on category grounds. One says they were "false reported" and closed without an email, another was denied because AI image/video generation "is not supported", and a reply asks what stops Polar serving video AI apps.

Developer friction is named specifically: a deprecated Go SDK forcing a move to the API directly, products that must be recreated by hand in the sandbox, and a portal that applies one upgrade rule to downgrades and hands unused days back as money credits.

The payout complaints are waits and lost money — one payout held beyond 35 days, one withdrawal marked succeeded that never reached a bank. On features, users name fees, split payments and payment methods such as iDEAL.

The moves and near-moves name what tips the decision. On Creem, the reasons given are "the fees and the split payments feature" plus already being set up there — with "Nothing against Polar though!" — and one user says they may move from Polar to Creem. One swap is finished: a product update announces checkout moved from Lemon Squeezy onto Polar, a post that travelled far.

Stripe comparisons are about features rather than loyalty. A user says what they miss in Polar is the different payment methods Stripe offers, such as iDEAL. Another, choosing between Stripe, Dodo and Polar, says they did not look at tax rates at all and picked Polar purely for its notification style.

Dodo Payments appears once, as an open question about which provider to keep. Gumroad appears once from someone recalling comparing Polar with Paddle and Gumroad and judging Polar the best option, while asking why someone else moved off it.

The AI questions are about billing and fit rather than price. One asks how Polar handles a single task that fans out into many agent calls — "Bill per task or per call?" — expecting per-run billing to be "a real headache for a lot of teams". Another asks whether Polar will switch from people selling digital products to agentic companies. Two more ask what it offers in the age of agentic coding, and what stops it staying the payment provider for video AI apps now that they have learned of restrictions.

The worth-it questions are asked before adopting: whether someone is happy with Polar, whether anyone is already using it because they are implementing it "tomorrow morning", and a reply asking why not use Polar instead of a rival.

Payouts come up once, from someone who moved to Dodo and asks how Polar's payouts perform, calling that "usually where the surprises are".

The meter reset request is detailed: one user of monthly meters for requests, bandwidth and storage wants to restore the full allowance mid-cycle — "80/100 used -> 0/100" — while keeping usage history, and would like the UI to show the reset too, not just have credits re-granted. The same user found the manual credits feature shipped on October 21 and asked whether the newer API is safe in production, calling a reset "a lovely bonus".

Geography is the other want: more withdrawal pipelines, and support for Montenegro, with one noting it would be easier to get into the EU than on some payment providers.

The AI framework asks come from one builder with many AI product ideas, waiting for a TanStack AI plugin to track usage and wanting a plugin setup that is one line of config and done.

Singletons round it out: products created in production appearing in the sandbox automatically, and an API to revoke and rotate organization access tokens.