r/lemonsqueezy

I created account and store. Also created product. But I cant get the store activated.

Says I need to update tax information, but when i click it nothing happens.

I dont live in any of the supported countries, but I connected PayPal as my payout option and that should be enough for me at this point, but I cant get it started anyways.

It's just blank like this:

https://preview.redd.it/29irf2vgqq1h1.png?width=1367&format=png&auto=webp&s=6a49d82cad91a02f205debfb2ad7a6ed67d8d6ae

I know I wont get IBAN payouts in unsupported countries, but at least I want to use PayPal.

After short google/ai search I tried disabling adblockers, logging in from incognito, from windows sandbox, from firefox on linux vm, from mobile phone on mobile data, etc. Nothing works.

Can anyone help me out?

Please and thank you.

How long does it take for Lemon Squeezy to approve? Do they accept SaaS and not online store

I run a small SaaS on LemonSqueezy and got tired of clicking around the dashboard every time I wanted to check MRR, refund an order, or disable a license key. So I built an MCP server that wraps the LemonSqueezy API into 61 tools and exposes them to Claude, Cursor, VS Code, or any other MCP-compatible assistant.

The interesting bit isn't the API mirror -- there are a few of those already. It's the guardrails. Letting an LLM call refund_order against a live store is the kind of thing that gives ops people heart attacks, so the server has opt-in env vars for: a store allowlist, a per-call refund cap (rejects above N cents before the HTTP call), a destructive-call rate limit, and a parent-filter check so a list-tool without store_id can't silently return cross-store data.

A few other things I'm proud of:

- Zero runtime dependencies. The published bundle is one file (~1.2 MB), so npx u/yawlabs cold-starts in a second.

- Audit log with four levels (off, error, audit, all), plus the audit trail is exposed as an MCP Resource (lemonsqueezy://audit-log) for clients that prefer structural retrieval over parsing stderr.

- Secret-shaped fields are redacted from audit-log inputs even though no destructive tool today accepts a secret -- defense in depth, costs nothing.

- 401/403 from upstream auto-invalidates the in-process API key cache, so a key rotation takes effect on the next request, not after the 1h TTL.

- npm publish has provenance attestation. Nightly integration tests against a real test store catch upstream schema drift.

Install (npm):

npx u/yawlabs

There's also a Dockerfile + Containerfile if you want it bundled.

Honest limits:

- The store allowlist only gates tools that accept storeId directly. Tools that route by their own resource ID (refunds, cancels, archive) still need a LemonSqueezy API key scoped to the right store -- that's the only authoritative boundary. README's "Operating the server unattended" section spells out the recommended layered config.

- Stdio transport only. If you want HTTP/SSE, look at Pipedream or Zapier's hosted MCPs (different deployment model).

- I know LemonSqueezy isn't Stripe-sized -- this is a niche tool for niche users. Posting in case you're one.

Code, README, full tool list, and the SEMVER policy:

https://github.com/YawLabs/lemonsqueezy-mcp

npm:

https://www.npmjs.com/package/@yawlabs/lemonsqueezy-mcp

Happy to take feedback on the guardrail surface, the audit log shape, or anything else. If there's a LemonSqueezy operation I missed (the License API side is in there too: activate/validate/deactivate), open an issue.

• I've noticed quite a lot of bad testimonials on how Lemon Squeezy handles support (not), and how unnecessarily burdensome their processes can be for sellers at times.
• They have 1.2 stars on Trustpilot.
• I've noticed a lot of complaints in the current sub, overwhelmingly so.

So, my question for people using this tool is: Are you satisfied?

On paper, having a MoR sounds like a great idea - being able to sell worldwide with a few clicks is remarkable. What wonderful times we're living in to be able to do that! But they are a proxy between the paying customer and me, so all money goes through them. With so many bad reviews, I'm not sure I should trust them with my and my customers' money.

What are your thoughts on this?