All ideas/billing, fintech/A SaaS platform providing billing and subscription endpoints and flows for platform plans with native Stripe integration, clearly separating platform billing from third-party payouts.

GitHubB2BPaymentsbilling, fintech

A SaaS platform providing billing and subscription endpoints and flows for platform plans with native Stripe integration, clearly separating platform billing from third-party payouts.

Scouted 18 hours ago

7.0/ 10

Overall score

Turn this signal into an edge

We help you build it, validate it, and get there first.

From detected pain to an actionable plan: who pays, which MVP to launch first, how to validate it with real users, and what to measure before spending months.

Expanded analysis

See why this idea is worth it

Unlock the full write-up: what the opportunity really means, what problem exists today, how this idea attacks the pain, and the key concepts you need to know to build it.

Score breakdown

Urgency8.0

Market size7.0

Feasibility8.0

Competition5.0

The pain

There is a lack of an integrated and distinct solution to manage platform subscriptions and billing separate from creator payouts in systems using Stripe Connect.

Who'd pay

SaaS companies and marketplaces using Stripe Connect that need to manage their own platform subscriptions and billing independently from creator or vendor payouts.

Signal that triggered it

"We still need first-class platform subscription endpoints for Floom plans (checkout + billing portal), separate from creator-payout primitives."

Original post

v1.2: Add platform Stripe checkout + billing portal flows (separate from Connect)

Published: 18 hours ago

Repository: floomhq/floom Author: federicodeponte Why Floom currently exposes Stripe Connect flows well (onboarding/payments/subscriptions for connected accounts). We still need first-class platform subscription endpoints for Floom plans (checkout + billing portal), separate from creator-payout primitives. Scope - Add platform billing endpoints (exact path names up to implementation): - create checkout session (workspace/org-scoped) - create billing portal session (workspace/org-scoped) - Keep platform billing distinct from existing Connect routes. - Reuse existing webhook idempotency discipline for billing events. - Include auth + workspace scoping consistent with Cloud mode session model. Acceptance Criteria - Authenticated workspace owner/admin can create checkout session for platform plan. - Authenticated workspace owner/admin can open billing portal. - Webhook events update platform billing state idempotently. - Event replay does not duplicate side effects. - API docs include route purpose distinction: platform billing vs Connect.

View on github ↗

Your daily digest

Liked this one? Get 5 like it every morning.

SaaS opportunities scored by AI on urgency, market size, feasibility and competition. Curated from Reddit, HackerNews and more.

Free. No spam. Unsubscribe any time.

Open source ↗