Paddle rejected my account. Here's the map of what actually works in 2026

Disclosure: I'm Oded, co-founder of UniPaaS, the FCA-authorised Payment Institution (No. 929994) behind paas.build, and we compete with Paddle.

The title above is the sentence builders keep arriving with - right here on dev.to, in Hacker News threads, and in our inbox. This is the map I give them, including the branches where Paddle is still the right call.

Why good products get rejected

Paddle is a Merchant of Record. The moment it approves you, it becomes the legal seller of everything you sell. So its underwriting answers exactly one question: "do we want to legally own this business's sales?"

A brand-new solo builder with no history is the riskiest possible answer to that question, regardless of how good the product is. Builders who have been through it report the same four themes:

• No prior processing history. The chicken-and-egg: you need a payments track record to get approved, and you need approval to build a track record.
• An incomplete-looking site. Missing terms, no pricing page, no live domain, no visible product. Reviewers open your site.
• Identity mismatches. The applying entity, the domain owner and the bank account don't line up.
• Category restrictions. Paddle has tightened around some generative-AI products.

Very little of this is documented, which is why the rejection email feels random. It isn't. It's a business model doing exactly what it was built to do.

The decision tree

Two questions decide your next move.

1. Is "global tax handled for me" your top requirement?

If yes, stay in the MoR category. This is Paddle's genuine strength, and it's a real one: as Merchant of Record it remits VAT/GST across 100+ jurisdictions, and that liability sits with them, not you. No PayFac gives you that.

Don't switch categories - fix the application and get back in the queue:

• Make the site look finished. Live domain, real pricing page, terms of service, privacy policy, a working demo.
• Explain the business plainly. What you sell, to whom, expected volume, refund policy. Vague reads as risky.
• Match identities. Applicant, domain owner and bank account should line up cleanly.
• Budget for the queue. Initial review typically takes days; domain reviews and appeals can stretch longer with no committed timeline.

If Paddle says no a second time, Lemon Squeezy and the other MoRs run the same model with different risk appetites. Same category, different reviewer.

2. Do you need to be selling this week, under your own brand?

Then the fix is structural, not cosmetic. A payment facilitator (PayFac) inverts the model: you stay the merchant, your name is on the checkout and the statement, you own the customer relationship, and risk is managed with limits and monitoring instead of upfront gatekeeping.

That's what progressive KYB means at paas.build in practice: a real merchant account, sandbox and production, in the same session - individuals and sole traders included. You're live immediately with a cap of roughly £1,500 while verification completes in the background. No processing history required, because the cap is the underwriting.

Paddle asks "prove you're established." Progressive KYB says "start small, we'll verify as you grow." If you were rejected for being new, that's the difference that matters.

On price: paas.build charges 3.9% flat. Paddle charges 5% + $0.50, which on a $9 subscription is $0.95 - an effective 10.6%. The fixed fee is what stings at small ticket sizes.

Where the PayFac path does not work

I promised honesty, so here it is:

• Geography. paas.build onboards builders registered in the UK, EU or US. Your customers can pay from anywhere in the world, but if you're based outside those regions, this branch of the tree is closed to you.
• Tax is yours. You are the seller of record, so VAT and sales tax filing are your responsibility. We ship guides and tax-engine integrations, but the liability does not move. If that sentence made your stomach drop, go back to question 1.
• The cap is real. Roughly £1,500 until verification completes. Fine for a launch; if you're already at volume, plan for the verification step.

The map, folded up

• Rejected, and you need tax handled globally: harden the application and reapply to Paddle, or try another MoR. The review queue is the price of the tax shield.
• Rejected, and you need to launch now under your own brand, from the UK, EU or US: a progressive-KYB PayFac gets you a live, capped account the same day.
• Based outside the UK, EU and US: the MoR category is probably your only route. Make the application airtight before you resubmit.

The rejection wasn't a verdict on your product. It was a filter built for a different business model. Pick the model that matches what you actually need, and stop paying the queue tax for a shield you may not even want.