Chicken-and-egg: paddle payment rejected me as I have no processing statements
2 comments
Looks like they have recently instated this requirement because I have seen many new SaaS creators in the past using Paddle from the start. WHY THIS ABSURD REQUIREMENT SUDDENLY?!!
p.s. This happened with me also when I applied recently for Paddle.
p.s. This happened with me also when I applied recently for Paddle.
It's disappointing to hear that Paddle requires three months of processing statements before allowing integration for new SaaS products. This creates a classic chicken-and-egg dilemma: without a payment solution, you can't generate transactions, and without transactions, you can't qualify for Paddle.
For new SaaS products, starting with an alternative payment processor like Stripe, which does not have this requirement, seems to be a necessary step. Stripe is straightforward to integrate and widely trusted. After generating the required transaction history, migrating to Paddle for its comprehensive tax handling could be considered.
Alternatively, many tax solutions can integrate with Stripe, providing similar benefits to what Paddle offers without the initial barrier.
This requirement seems counterintuitive and might deter new businesses from considering Paddle from the start. If Paddle could reconsider or provide a pathway for new products without existing transaction history, it could be more appealing to startups.
For new SaaS products, starting with an alternative payment processor like Stripe, which does not have this requirement, seems to be a necessary step. Stripe is straightforward to integrate and widely trusted. After generating the required transaction history, migrating to Paddle for its comprehensive tax handling could be considered.
Alternatively, many tax solutions can integrate with Stripe, providing similar benefits to what Paddle offers without the initial barrier.
This requirement seems counterintuitive and might deter new businesses from considering Paddle from the start. If Paddle could reconsider or provide a pathway for new products without existing transaction history, it could be more appealing to startups.
100% agree
Paddle(https://paddle.com) seems to be a good choice for my case as they can handle sales tax for you, so I applied for Paddle.
However, in their domain verification step, I was rejected because my SaaS do not have prior processing statements (aka, transactions history).
The response:
```
To clarify, you will need to provide processing statements from a payment processor for at least the past three months. These statements help us assess your transaction history and ensure everything aligns with our requirements.
Yes, it typically means that you’ll need to integrate with another payment processor and generate some transaction history before applying for Paddle. Once you’re approved by Paddle, you can then migrate your customer data to our platform.
```
This is kind of ridiculous requirement for a new SaaS product. No payment solution -> no transactions, no transactions -> cannot apply paddle, the chicken-and-egg dilemma.
And if I already integrated another payment solution (such as stripe), then why should I migrate to paddle then? I can just work with some tax solutions (contract or SaaS) to get the same as Paddle can do.
I am not sure how many people got the same experience with Paddle. Just posted my experience here FYI.