How to Collect Payments at a Community Signup

May 28, 2026 · 8 min read

Someone on your committee finally asks the obvious question: "Can we just collect the fee when people sign up?" It's a reasonable ask. Instead of chasing Venmo requests, reminding people to bring cash, or sending a PayPal link after the fact, you collect the money at the moment of commitment — when people are most motivated to pay.

The problem is that most signup tools either don't support payments at all, or they charge you significantly for the privilege. This guide covers when payment collection makes sense, what it actually costs across different platforms, and how to set it up without spending your afternoon on it.

When collecting payments at signup makes sense

Not every event needs payment collection. For a lot of community events — volunteer shifts, school committee sign-ins, potluck dish assignments — there's no money involved and the complexity isn't worth it.

Payment collection earns its setup cost when:

• You have a per-person cost — class fees, activity fees, field trip costs, camp registration. Any event where each participant owes a specific amount.
• You're tired of chasing payments — if you've ever sent three follow-up messages to collect a $15 fee from someone who signed up two weeks ago, this solves it.
• You need to guarantee commitment — paid signups have dramatically lower no-show rates than free ones. If you're ordering food, reserving seats, or paying per head in advance, that matters.
• You're managing limited capacity — payment at signup ensures you're not holding spots for people who were never really committed.

If none of those apply — if it's just a volunteer shift or a potluck dish assignment — skip the payment setup and use a free tool with no overhead.

What payment collection actually costs

This is where a lot of organizers get surprised. The platform fee is rarely the full picture — you also pay Stripe's (or another processor's) base fee on every transaction. Here's how the math works across common tools:

Note: "You keep" figures are approximate and don't account for monthly fee amortization across transactions.

The key insight: Eventbrite looks free but takes the most per transaction. SignUpGenius requires $39/month before you collect a single dollar. PayPal is cheap per transaction but requires you to manually collect and track payments outside your signup tool.

For most community organizers collecting $10–$50 per person for recurring events, Mercurylist's model (flat $12/month, 2% platform fee, Stripe's base fee) works out best once you're running more than a handful of transactions per month.

When does payment collection pay for itself?

If you're on Mercurylist Pro at $12/month and charging $20 per signup, you need to collect about 2 payments per month before the time savings alone justify the subscription. At that point you're not chasing Venmo requests, manually reconciling payments, or sending reminder messages about unpaid fees.

For a typical PTA or church event series — a cooking class, a family camp registration, a field trip — you'll usually have 15–40 paid signups per event. The math works clearly in favor of automation once you're past your first event.

How to set it up on Mercurylist (step by step)

The setup takes two parts: connecting your Stripe account once, then enabling payment on each event you create.

Step 1: Connect your Stripe account

Go to Settings → Stripe Payment Collection → Set Up Stripe Account. This opens Stripe's hosted onboarding — you'll enter your bank details, verify your identity, and authorize Mercurylist to process payments on your behalf. Takes about 5 minutes. Stripe handles all the compliance and security.

You only do this once. After setup, all future paid events use the same connected account and payouts go directly to your bank account — not to Mercurylist first.

Step 2: Enable payment when creating an event

When creating a new event, check "This event requires payment from attendees" and enter the amount. That's it. Attendees will be taken to a Stripe checkout page after selecting their slot. Payment confirmation is automatic — you'll see the status in your dashboard and the attendee gets a receipt from Stripe.

Step 3: Monitor in your dashboard

Your event dashboard shows each signup with their payment status. Unpaid signups are flagged. If someone's slot is unpaid, you can decide whether to hold their spot or open it back up. Payouts from Stripe typically land in your bank account within 2 business days.

Common questions

What if someone wants a refund?

Refunds are issued through your Stripe dashboard directly. Stripe's standard refund policy applies. You can issue full or partial refunds. Stripe returns the processing fee on full refunds issued within a certain window (check Stripe's current policy).

Can I charge different amounts for different slots?

Currently Mercurylist sets one price per event. Per-slot pricing (e.g., VIP vs. general admission) is on the roadmap. For now, if you need different prices, create separate events for each price tier.

What if I don't want to collect payments for every event?

Payment is opt-in per event. The "requires payment" checkbox is off by default. You can mix paid and free events on the same account — a paid cooking class and a free volunteer shift can coexist in your dashboard without any friction.

Do attendees need a Stripe account?

No. Attendees just enter their credit or debit card at checkout — the same experience as any standard online payment. No Stripe account, no Mercurylist account required.

The bottom line

Collecting payments at signup isn't complicated — the tools exist, the fees are predictable, and the upside is real: higher show rates, no manual payment chasing, and clean accounting. The question is just whether your event volume justifies a monthly subscription.

For most active community organizers running 2+ paid events per month, the answer is yes. For occasional events with no per-person fee, stick to the free tier and don't overthink it.