Published April 22, 2026 · 12 min read

Stripe Rejected My SaaS. Then Lemon Squeezy. Then Paddle.

I spent three weeks building an AI face swap SaaS, polished the safety features, wrote the terms of service, and got everything ready to start taking payments. Then I got rejected by three payment processors in five days. This is the story, with the actual rejection reasoning, and how I ended up accepting crypto payments and paying 0.5% in fees instead of 2.9%.

The setup

The product is Swap-Video — upload a selfie and a video, AI swaps your face onto the person in the video. Three-model NSFW ensemble, three required consent checkboxes, C2PA-compatible AI-generated metadata on every output, and auto-delete of uploads after 24 hours. As safety-conscious as you can reasonably make a hosted face swap service.

I thought I had a chance with the traditional payment processors because of the safety layers. I was wrong — they never got that far in reading my application.

Attempt 1: Stripe

Stripe was the obvious first choice. I'm based in Israel, which Stripe nominally supports through Stripe Atlas, but the path for an Israeli founder with a personal LLC is thorny.

I filled out the business details carefully — listed the product as "AI video processing SaaS", described the face swap functionality, linked to the safety page, and submitted. Rejection came within 48 hours. The relevant line:

"Unfortunately, your business activities fall outside the scope of services Stripe can support. This decision is based on our Restricted Businesses list and our risk assessment."

Stripe's Restricted Businesses list doesn't explicitly mention face swap, but "products that impersonate real people" and "content that could be used to defraud or mislead" cover it implicitly. The geographic side probably didn't help either.

Takeaway: Stripe applies their ToS to face swap even when the product itself is safety-focused. I moved on.

Attempt 2: Lemon Squeezy

Lemon Squeezy is pitched as "Stripe for indie makers" and runs a merchant-of-record model, which I'd hoped would make the category-risk conversation more productive. I submitted a full store application with screenshots of the safety flow, the NSFW ensemble, and the consent pattern.

Three days later, rejection. Their phrasing:

"We're unable to approve your store at this time. Our Acceptable Use Policy prohibits AI services that impersonate real people, which includes face swap functionality regardless of safety measures."

That wording matters — "regardless of safety measures." Lemon Squeezy's AUP treats the category as blanket-banned. I'd been hoping the 3-model NSFW filter and consent checkboxes would move the needle. They didn't.

In hindsight: this was the moment I should have stopped trying traditional processors. But I had one more idea.

Attempt 3: Paddle

Paddle is the enterprise-leaning merchant-of-record alternative. They publish a detailed Acceptable Use Policy, which I read before applying. Sure enough, in section 4.3: "face-swapping software or services" is explicitly listed as a Prohibited Business.

I tried anyway, thinking the explicit safety layers might warrant an exception. They didn't. Paddle rejected within 24 hours without even requesting a live demo of the product. At this point I'd burned a week and a half on payment processors and had zero way to accept money.

The crypto pivot

The realization came after the Paddle rejection: the payment processor market treats the category as restricted, not the implementation. No amount of safety engineering changes that. The question was never "is this specific product safe" — it was "will someone complain loudly enough that we regret approving it."

That left high-risk merchant accounts or crypto. High-risk merchant accounts charge 4-8% in fees and require substantial reserves. Crypto was suddenly the pragmatic choice.

I evaluated three options:

I went with NOWPayments. Integration took about four hours, including testing the webhook verification (HMAC-SHA512) and wiring the invoice creation into the existing Supabase session model. The fees dropped from the 2.9% + $0.30 I'd budgeted for Stripe to a flat 0.5%. At $9.99/month, that's $0.05 in fees instead of $0.59. Over 10,000 monthly subscribers that would add up to $54,000/year in savings.

The trade-offs

Crypto-only payment has real downsides, and pretending otherwise would be stupid.

Downsides:

Upsides I didn't expect:

What I would do differently

If I were starting over, I'd skip directly to crypto and not waste a week on traditional processors. Specifically:

  1. Read the AUP before you apply. Both Lemon Squeezy and Paddle clearly list face swap as prohibited. I wasted days not doing this. For "AI that generates/modifies content with humans," assume blanket-banned.
  2. Evaluate the crypto processors upfront. NOWPayments, BTCPay, and Coinbase Commerce are the three to know. Each has different trade-offs — NOWPayments is the lowest-friction if you want something working today.
  3. Design the checkout flow for crypto-first from day one. Don't build a Stripe integration and then bolt crypto on — the UX considerations are different (invoice expiry, underpayments, confirmation lag) and retrofitting is painful.
  4. Communicate the crypto requirement before users click the pricing button.Not burying it in FAQ #4. Adding a notice above the "Go Pro" button cut abandonment noticeably because users who hate crypto self-select out earlier.

What this means for other "high-risk" SaaS categories

Face swap is one of a growing list of categories that traditional processors treat as blanket-prohibited regardless of implementation:

If you're in one of these, the processor conversation is not worth having in 2026. Go crypto, or go high-risk merchant account. The crypto route is genuinely viable — the fees are lower, the geographic coverage is better, and the user experience has gotten remarkably good. It's just a different thing to build around.

The actual numbers

A month after going live with NOWPayments:

One last thing

If you're reading this because your own SaaS just got rejected — you're not alone, this is extremely common, and it's not a judgment on your product. The payment processor landscape is more restrictive than most countries' laws, and the bar keeps moving. Move on to crypto, ship your product, and come back to traditional processors in a year when you have the volume to negotiate or when policies shift.

Try the product I built after this saga

Try Swap-Video Free →

2 free swaps, no credit card. Pro plan accepts crypto (BTC, USDT, ETH, 300+ others).

Related posts