← All features

Operations · Payments & Revenue

Take the money where the sign-up happens.

Members pay for a class, a room, a trip, or a meal from their phone. Staff take cash, a check, or a card at the counter. Either way the payment lands on the record it belongs to.

What it helps with

What your team can do here.

Paid at sign-up

The registration and the payment are the same moment.

A member picks a class, a room booking, a trip, or a meal in the portal and pays for it on the spot through Stripe. The money goes to your organization's own Stripe account rather than through ours, and NestPoint takes no cut of it. Because the seat and the payment arrive together, nobody spends Monday morning matching a list of names against a list of card charges.

  • Classes, room bookings, trips, and meals
  • Funds settle into your own Stripe account
  • No NestPoint percentage on top of Stripe's rate

At the front desk

Cash, a check, a card reader, or waived.

Not everybody pays online, and a good front desk already knows it. Staff can record cash or a check, key in a card, tap a Stripe reader sitting on the counter, or waive the fee outright. The method is stored with the payment, so how something got paid is never a guess three weeks later.

  • Stripe card readers, including the WisePOS E and the Reader S700
  • Cash, check, keyed card, payment link, or waived
  • The method stays on the row, which is what makes reconciliation possible

Refunds and corrections

A refund is a row, not an eraser.

Refund all of it or part of it. Card payments go back out through Stripe; cash and checks are recorded as the refund you handed over. Either way the refund is written as its own entry pointing at the payment it reverses, and the original stays exactly where it was. A row entered by mistake is voided with a reason and the name of whoever voided it.

  • Full or partial, with the remaining refundable amount worked out for you
  • Stripe refunds for card payments, recorded refunds for cash and checks
  • Nothing is deleted, and every void carries a reason and an actor

What came in

Every module's money, in one view.

The revenue hub totals what was billed, what was collected, and what is still outstanding across classes, rentals, trips, and meals, for today, the last week, or the last month. Administrators can pull the same figures as reports: an aging breakdown of what is overdue, a split by payment method, and a reconciliation view that lines your records up against the Stripe dashboard.

  • Overview, transactions, outstanding balances, and checkout activity
  • Aging at 30, 60, 90, and past 90 days
  • Reconciliation against Stripe, and a breakdown by payment method

A typical workflow

From a phone at nine to a number you can explain.

One session of summer camp, followed from the moment a parent taps pay to the figure the board reads.

  1. A parent pays for camp. She registers her son in the portal and pays by card. Stripe confirms it and the payment lands on his registration, not in a separate list of transactions.

  2. A neighbor pays at the counter. He has no email address and does not want one. Staff take his check against the same session and put the check number in the note.

  3. One family cannot pay. Staff waive the fee. The waiver is its own entry, so the roster shows a filled seat and the report shows why that seat brought in nothing.

  4. Rain cancels the week. Card payments go back out through Stripe, the check gets a recorded refund, and both refunds sit underneath the payments they reverse.

  5. The board asks what came in. The revenue rollup adds up classes, rentals, trips, and meals for the period, and the reconciliation report shows those totals beside what Stripe says.

Common questions

What teams ask before getting started.

Every fee you charge, on the record that owes it.

Class fees, hall deposits, trip payments, lunch money. See what changes when the payment arrives attached to the person and the thing they paid for.

Card required. Cancel anytime.