1
2 Comments

I built a dating app where men pay a deposit to send the first message

The idea came from a simple frustration: women on dating apps get flooded with low-effort messages. Men swipe without thinking. Nobody has skin in the game.

So I built NoPayNoDate.

Here's how it works:

Women set a deposit amount ($20–$200) to unlock their inbox
Men pay that deposit via Stripe to send a first message
If she declines → 100% refunded, automatically
If the date is confirmed by both → she receives the deposit (minus 10% platform fee)
We only make money when a date actually happens
No date, no revenue. Aligned incentives.

The tech stack:
Next.js 16, Stripe Connect with escrow, Better Auth, Neon Postgres. Built solo in a few weeks.

The hardest part wasn't the code — it was the legal framing. The #1 question I get: "Isn't this prostitution?"

Short answer: no. A deposit is proof of intent, not payment for a service. Same logic as a restaurant reservation deposit. The date content is entirely free.

What's next:

Waitlist is open
Looking for feedback from both sides (men and women)
Curious if anyone has tackled escrow-based trust mechanics before
Would love brutal feedback from the IH community. Is the positioning clear? Is the model flawed somewhere I'm not seeing?

on March 28, 2026
  1. 2

    This is actually a really interesting mechanism because it forces people to be more intentional instead of treating interactions like infinite-scroll content.

    Feels like a lot of dating app behavior now comes from the fact that there’s basically zero friction or accountability tied to messaging.

    1. 1

      Thanks! That's exactly the insight behind it. Most dating apps are optimized for engagement (swipes, likes, notifications) not for actual connections. The deposit creates a small friction that filters serious intent — and women get to set their own price, which puts them in control.

      Still early days but curious to see if behavior data confirms the thesis.