Pay Only When the Group Forms
For group-chat classes, venue bookings, and group buys, participants authorize a maximum amount and are charged together only once the required headcount, date, and price are all met.
When friends book a venue, fill a class, or organize a group buy, the organizer sets a minimum number of participants, each person’s maximum price, the date, and a signup deadline. Participants open a link and authorize only the most they are willing to pay. The page shows in real time how many more people are needed, whether the quote is within range, and which condition has not yet been met. No one in the group chat has to keep asking, “Did you actually send the money?”
The payment service charges everyone and confirms the order only once the headcount, date, and final quote all meet the preset conditions. If a venue reprices, the time changes, or someone drops out and the conditions no longer hold, existing authorizations are automatically released. The organizer does not have to collect money first and then issue individual refunds. Before confirmation, every participant can see the amount they will actually pay.
Organizers can create separate templates for venues, classes, and group buys, such as “Book a badminton court once six people join” or “Eight people share a pottery class.” The system writes confirmed attendance and payment status back to the event page, making waitlist management easier. If the group still has not formed near the deadline, the page offers clear options to cancel or adjust the conditions.
The first version uses a compliant payment provider for authorization and capture; the product does not hold user funds itself. It does not decide whether an activity is worth joining. It simply turns the agreement to gather the group first and pay second into rules everyone can see.
Why now
As observed on August 7, X Money ranked 20th in Product Hunt’s new-product feed. S1 Payments are being brought back into a social-network context, making the gap for “gather the group first, then pay” in group chats easier to see.
Target user
The primary users are people who regularly organize sports games, short classes, meals, or small group buys in group chats. The hardest moment comes when they are ready to book: plenty of people say they are in, but it is unclear who is actually willing to pay. Organizers do not want to front the cost or strain relationships by repeatedly chasing people. Participants worry that there will not be enough people, the price will change at the last minute, or refunds will be delayed. Both sides need to see the same conditions before an order is placed.
Minimal entry point
Use Stripe Checkout or PaymentIntents with manual capture. S2 Create an individual PaymentIntent for each participant at their payment cap. Store the headcount, date, quote, and deadline on the server, and update event status through authorization webhooks. Once conditions are met, capture the actual amount. If it is lower than the cap, release the unused amount. S2 If conditions fail, cancel the corresponding PaymentIntents. The first version accepts only payment methods that support authorization followed by capture. The signup deadline must precede the expiration of every authorization. Do not support group buys spanning multiple months or organizer-collected payments initially. Send venue payments through a single merchant first, then validate the need for Connect payouts.
Punching above its weight
Recruit initial users from people who organize recurring activities, including sports-group hosts, class teaching assistants, and interest-community admins. Build ready-to-share template pages for badminton courts, pottery classes, and private group dinners. Keep product attribution on every successful group page so participants can start their own next time. Create short demo videos around specific needs such as “charge only when enough people join.” Local venues could also include the link in their booking replies.
Competitors & gaps
- SplitwiseGoogle
- Splitwise already lets users create groups, split expenses, and track balances. Users can also record offline payments and, in some regions, settle directly. S3 It works well for shared expenses that have already occurred and for ongoing relationships. Its core flow still records costs first and settles them later. Its public documentation does not offer a minimum headcount, signup deadline, or price cap. Nor does it hold participants' ability to pay until conditions are met. Organizers still need to book the venue or front the money, then wait for members to settle. If someone drops out, the debt can be recalculated, but the venue booking may not be reversible. The gap is not a more granular bill-splitting algorithm, but coordinating conditions before a transaction happens. The new product should retain the low-friction join-by-link experience without requiring everyone to maintain a running ledger. It should also surface failed groups, expiring authorizations, and price changes directly.
- PartifulGoogle
- Partiful already covers event invitations, RSVPs, and payments. Chip In can request a fixed amount or let guests choose their own amount. Payments redirect to an external service, so the platform cannot verify them. S4 Its ticketing feature can verify payments and invoices and supports door check-in. It is closer to an event publishing and ticketing tool, suited to events with a fixed time and price. Its public documentation does not describe charging everyone only when a minimum attendance threshold is met. It also does not describe having each person submit a maximum payment amount in advance. When a class can run only if it fills, organizers still need to determine manually whether the group has formed. If pricing changes with attendance, a fixed ticket price cannot easily express each person’s cap. The opportunity is to make signup conditions and payment authorization part of the same state. The page must also make clear whether the gap is headcount, date, or an over-limit quote. The product does not need to replicate a full invitation system; it can focus on small bookings initiated in group chats.
How it makes money
Charge organizers a flat service fee only when a group forms and payment is successfully captured. Charge nothing for groups that do not form, and list payment-processing fees separately. Start with frequent organizers, then offer subscription templates for venues and classes.
The case against
Card authorizations may appear as pending charges. Even if they have not settled, participants may think they have already been charged. S2 Authorization windows also vary by card network and payment method. For longer signup periods, early authorizations may expire first. The system can only ask participants to confirm again, which can reduce the formation rate. If a venue raises its price above an individual’s cap, the entire order must be canceled or reauthorized. If the platform collects funds for venues and then pays them out, merchant onboarding and reconciliation work also increase. Chargebacks, disputes, and duplicate authorizations require customer support as well. Any mistaken charge would directly damage trust within the group. Validation should focus on short-cycle activities rather than trying to cover every kind of group buy first.