Sees paid, unpaid and outstanding across registration, trading and fundraising.
PY · Club OS module
Every payment a club needs to accept, in one place.
Payments is the Club OS layer for taking money without five tills, three apps and a volunteer reconciling them later. Square and Stripe sit underneath registrations, canteen, merchandise, raffles, sponsorship and coupons so the club has one operating picture of what was charged, what is outstanding and what still needs follow-up.
Payments
Live view
Junior season fee Stripe Paid
Raffle · Round 6 Square Open
Gift card · Chen $40.00 left Active
The job
What Payments is for.
Give treasurers and coordinators one payments view across the club’s real income paths — not a separate processor for every stall, form and fundraiser.
Product screenshots go here This module will carry real Club OS captures of the working screens. The layout is ready for them.
Who uses it Treasurer Registrar Canteen / merchandise lead Fundraising coordinator
Built around real club roles.
Collects season fees without chasing bank transfers that never match a name.
Takes card payments that land in the same club record as the order.
Runs raffles and campaigns with rules, tickets and a clear close.
Inside the module 01 02 03 04 05 06 01 02 03 04 01 02 03 04
The functionality committees actually run.
Accept payments across the club
Square and Stripe power the payment paths clubs already run — so money and club work stay connected.
Square and Stripe, ready for clubs
Connect the processors clubs already trust. Card payments, receipts and settlement stay tied to Club OS records instead of living only in a processor dashboard.
Registration fees
Season products, playing fees and levies collect against the person who enrolled. Paid, unpaid and partial sit next to the registration — not in a separate bank CSV.
Canteen Management
Match-day trading should take payment without inventing a second till process. Orders, tickets and payment status stay linked so the canteen board and the treasurer are looking at the same day.
Merchandise Management
Shop orders, deposits and balances honour the same payment rails as the rest of Club OS. Families are not paying one way online and another way at the stall.
Sponsorship collections
Invoice and collect sponsor packages through the same payments layer. Outstanding sponsorship sits visible beside delivery work, not in a forgotten spreadsheet.
One club ledger view
Pretty much every payment a club needs to accept is included: intake, trading, fundraising and sponsor money under one operating picture.
Coupons & gift cards
Member perks, sponsor offers and gift cards only work when every selling module honours the same rule.
Codes with a purpose
A coupon should say what it is for, who can use it, and when it expires. “10% off” in a Facebook comment is not a rule.
Gift cards with a balance
Issue a card, track the remaining value, and redeem it against canteen, merchandise or registrations so the club is not running an honour system.
Campaign windows and limits
Member week, sponsor activation or end-of-season sale — with dates, one-use rules and product limits the counter can follow.
Connected redemption
A code used at the canteen, the shop or registrations should hit the same ledger. Otherwise the treasurer rebuilds it by hand.
Raffles & fundraising sales
Fundraisers should have tickets, buyers and a close date — not a cash tin and a hope.
Raffle campaigns with structure
Create a raffle with ticket price, draw date and what is being raised for. Volunteers sell from the same campaign, not from five paper books.
Tickets tied to people
Attach sales to Club OS people or families when you can. Follow-up, prizes and reporting become possible.
Card payments for fundraising
Take Square or Stripe payments for tickets so fundraising is not cash-only on match day.
A clean close
See tickets sold, money taken and what is still outstanding before the draw — so the club can run a raffle people trust.
How it runs
A path volunteers can repeat.
01 · Connect Square or Stripe Link the processors the club will use for card payments.
02 · Turn on the paths that sell Registrations, canteen, merchandise, raffles, sponsorship and coupons share the same payments layer.
03 · Take and track money Paid, unpaid and balances stay next to the club work that created them.
04 · Reconcile without a side book Treasurers work from Club OS instead of rebuilding the season from processor exports.
What it replaces
The hidden systems clubs already have.
- A different payment app for every stall
- Bank transfers with no person attached
- Paper raffle books and cash tins
- Gift vouchers nobody can honour at the till
Connected modules
This work does not sit alone.
See Payments in a walkthrough.
We will show the working screens, the volunteer path, and how this module connects to the rest of Club OS for your club.
Ready when your committee is
Give the club a system that outlasts the season.
Start with the workflows causing the most pressure, then grow into a full Club Operating System.