Paddle

Users report accounts closed after earning $2,000+ with Paddle claiming they 'no longer support the business' and holding funds for 180 days. Some SaaS founders report being suddenly classified as 'high risk' with multiple accounts closed within 24 hours. No proper explanation given.

Paddle requires prior payment processing history for approval - a requirement not disclosed upfront. New SaaS companies trying to integrate before launch face a blocking requirement for three months of transactions. This completely blocks new SaaS from using Paddle at launch.

The onboarding process can be lengthy, posing challenges for new businesses. Verification and approval take time. Strict anti-fraud checks occasionally cause delays or account holds. Getting started is slower than simpler alternatives.

Users report poor support with responses that rarely come, even after days or weeks. One user stated their email went unanswered for two weeks despite multiple follow-ups. Refund requests sometimes wait a week or more without response. Support is faster for enterprise customers.

While standard fee is 5% + $0.50, transactions under $10 incur a 10% fee. For SaaS with low-price tiers or microtransactions, this doubles the effective rate. The fee structure has edge cases that increase costs beyond advertised rates.

Paddle is more expensive than Stripe for many SaaS businesses. While Paddle includes MoR, a typical international Stripe business pays ~5.1% + $0.30 with all add-ons. Paddle's 5% + $0.50 is similar but with less flexibility. The MoR value must justify the cost.

Payouts are done automatically every month with no option for manual payout. For quickly growing SaaS companies needing faster access to cash, this is frustrating. The payout process has been described as 'horrible' for companies needing flexibility.

Users find the interface challenging with hidden features and need for better guidance on setup. The dashboard has a learning curve. Finding specific settings or understanding all options requires exploration.

Once deeply integrated with Paddle's ecosystem, migration becomes complex. The MoR model means Paddle owns customer relationships. Some users express concern about vendor lock-in and limited ability to switch providers.

Users have difficulty customizing the customer experience through checkouts, notably the overlay checkout which is 'not really customizable apart from text color.' For brands wanting unique checkout experiences, Paddle's options are limiting.

Cannot set different webhook URLs for multiple subscriptions under the same legal entity. The API is described as 'still immature despite being around since 2012.' Custom checkout endpoint documentation fails to specify parameter types. Developer experience lags behind Stripe.