When Organizations Bill Their Members: Stripe Connect

A handshake as a symbol for partnership Photo: Kristin Hardwick · StockSnap (CC0 1.0), via Openverse

Last week I described how Xircuit itself takes in money — the platform billing through which an organization pays for its access. This week the flow reverses. It's no longer the organization paying us, but the members paying their organization, with Xircuit sitting right in between as the platform.

That sounds like a small shift, but in truth it's a different state of matter altogether. As soon as money no longer flows between two parties but between three, every question gets more complicated: who owns the customer relationship, who carries the payment risk, where does the payout go, and what does the platform get for facilitating it. It took me a while to model that cleanly, and this post explains how it ended up.

From Platform Billing to Marketplace

Up to this point, Xircuit was, in terms of payment, a classic product: an organization subscribes, we charge, done. That's a straight line with two points. What this week adds turns the line into a triangle — the classic marketplace constellation, where a platform brings supply and demand together without being the seller itself.

Concretely, that means: an organization — a gym, a practice, a club — wants to charge its own members for something. Dues, course fees, add-on services. Xircuit provides the infrastructure for that, but doesn't act as the contractual partner of the members. The money belongs to the organization, not to us. We're the intermediary that ensures the payment runs through cleanly, technically, legally, and from a bookkeeping standpoint.

The big advantage of this two-tier setup is that both models exist side by side without interfering with each other. Xircuit continues to bill the organization; the organization additionally bills its members. Two flows, one foundation.

Why Stripe Express Connect

Stripe has a dedicated product for exactly this constellation: Connect. It's the building block that lets marketplaces and platforms pass payments on to third-party accounts. I chose the Express Connect variant, and that was a deliberate trade-off.

Express takes most of the complexity off the organization's plate. It gets a Stripe-hosted onboarding, a Stripe-managed dashboard for its payouts, and doesn't have to fight its way through full account setup itself. For us as the platform, that means less responsibility for sensitive payment and identity data — it sits where it belongs, with Stripe. The nice side effect: the crucial payment integration stays the same as with platform billing. It's the same Stripe account, the same keys, the same webhooks — just a different flow running over them. I didn't have to build a second integration, just extend an existing one.

This continuity mattered to me. Every additional payment integration is an additional source of failure, an additional secret, an additional endpoint that can go down. Building on an already-vetted integration is considerably lower risk than putting a new one next to it.

Onboarding: So That Payouts Actually Arrive

The trickiest part of a Connect setup isn't the payment itself, it's the onboarding. Before even a single euro can be paid out, Stripe has to know the organization: who runs it, which bank account receives the money, what tax and regulatory details are on file. If anything is missing here, the payout gets stuck — and nothing frustrates an operator more than revenue that's stuck somewhere in the system.

That's why the onboarding walks the operator step by step through the Connect registration. They start the process from within Xircuit, get routed to the Stripe-hosted flow, enter their details there, and return afterward. In the background, we track whether the account is fully set up and ready for payouts, and only unlock the billing features once it is. The goal of all this guidance boils down to one sentence: payouts should arrive cleanly. No half-set-up account, no blocked transfer, no nasty surprises at the end of the month.

A money transfer as a symbol for payouts Photo: Rawpixel (CC0 1.0), via Openverse

As soon as three parties are involved, the most important question is: where does the money flow, and who keeps what. From the start I made sure that the revenue share and fees are modeled transparently — not as a hidden deduction buried somewhere deep in a booking, but as a clearly named part of the flow.

When a member pays, the main amount goes to the organization. Xircuit's platform share and Stripe's processing fees are broken out cleanly, so both sides can trace exactly how the amount is composed. The operator sees what arrives for them. The member sees what they pay. And in between there's no gray zone where money disappears unexplained.

That's not a purely technical decision, it's one about trust. A marketplace lives on both sides believing in it. The moment an operator gets the feeling the platform is reaching opaquely into their earnings, the relationship is damaged. Transparency in the data model is the prerequisite for transparency in communication to even be possible.

All Seven Verticals Covered

One point I'm particularly proud of: the model isn't tailored to a single industry. All seven onboarding verticals that Xircuit supports are covered by member billing. Every industry can run its own billing model.

That wasn't a given. A gym thinks in monthly membership dues, a therapeutic practice in individual services, a club perhaps in annual dues with tiered rates. Had I built the billing model too tightly around any one of these ideas, the other six would have fallen by the wayside. The appeal of Connect lies precisely in the fact that the underlying mechanics — payment, revenue share, payout to a connected account — are identical across all verticals. What differs is what the organization configures on top, not the foundation underneath.

That way the platform stays generic while every organization can design its own fitting model on top. That exact separation between a unified substrate and industry-specific configuration is what holds Xircuit together across the individual verticals.

What This Means for Operators

Taking a step back, this week is about a shift in roles. On Xircuit, the organization is no longer just a customer, but itself a provider to its members. It gets a tool in hand that lets it run its own business independently, without having to build its own payment infrastructure.

For the operator, in everyday terms that means: they register once through the guided onboarding, connect their account, and from then on their members' payments run through a flow they neither have to program nor monitor. The payout lands in their account, the revenue share is clear, and the technical responsibility for card data, fraud detection, and regulatory requirements sits with Stripe. Xircuit remains the bracket that ties everything together — visible where it helps, and invisible where it would get in the way.