Collect in context
Connect recurring plans, add-ons, packages, services, retail, and account balances to the same member relationship.
Payments & billing
See the money, the member, and the next action.
Connect recurring billing, one-time purchases, packages, balances, failed payments, recovery, and revenue visibility to the member relationship behind every transaction.
Member context attached
Recurring and one-time revenue
Failures lead to follow-through
Revenue & collectionsCurrent operating period
This monthNet collected$265.8K+3.6% from prior period
Recurring revenue$198.4K74.6% of collected
Past-due balance$452.965 member accounts
Failed payments5Needs follow-through
Collected revenueBy week
Recurring billingOne-time salesPackagesBalancesFailed paymentsRecoveryRefundsReconciliation
The payments operating advantage
A transaction should never lose the relationship behind it.
Payments become operationally useful when the team can see what was charged, why it was charged, what member relationship it belongs to, what changed, and what should happen next.
Recognize exceptions
Surface failures, past-due balances, refunds, credits, disputes, and account changes before they become hidden back-office work.
Move to resolution
Give billing, member service, access, communication, and reporting workflows the context needed to coordinate the next action.
Payments workspace
Five views of the same financial relationship.
The revenue summary, transaction detail, recurring obligations, past-due work, and reconciliation picture should agree because they are built from the same operating context.
See your billing modelRevenue overviewSample workspace · illustrative dataThis month
Gross processed$272.4KAll payment activity
Net collected$265.8KAfter refunds and fees
Recurring revenue$198.4KMemberships and add-ons
Open past due$452.965 member accounts
Collected by weekCurrent period
Transaction historySample workspace · illustrative dataLatest first
Recent activityAll types
Jordan MillerUnlimited Membership · recurringAug 1$149.00Paid
Alex RiveraSemi-private Add-on · recurringAug 1$49.00Past due
Taylor ChenTrial Membership · new saleAug 2$89.00Paid
Sam KellyUnlimited Membership · recurringAug 1$149.00Failed
Morgan PatelTraining Package · one-timeAug 4$720.00Paid
Recurring obligationsSample workspace · illustrative data$198.4K current period
Recurring relationshipsMember context
Unlimited MembershipJordan Miller · monthly$149
Small Group Add-onJordan Miller · monthly$49
Semi-private MembershipAlex Rivera · monthly$129
24/7 MembershipTaylor Chen · monthly$89
Unlimited MembershipSam Kelly · monthly$149
Past-due and failed-payment workSample workspace · illustrative data$452.96 open
Open accounts5 members
Alex RiveraSemi-private Membership · Aug 1$129.00Past due
Sam KellyUnlimited Membership · Aug 1$149.00Failed
Casey MooreTraining Add-on · Aug 5$79.00Past due
Riley James24/7 Membership · Aug 7$65.00Failed
Drew WilsonRecovery Add-on · Aug 9$30.96Past due
Reconciliation and settlement viewSample workspace · illustrative dataBalanced
Gross processed$272.4K
Refunds & credits$2.7K
Net settled$265.8K
SettlementGrossNetStatus
Aug 10 settlement$18,642.00$18,155.42Matched
Aug 9 settlement$12,408.00$12,076.11Matched
Aug 8 settlement$9,884.00$9,612.77Review
Aug 7 settlement$15,216.00$14,801.63Matched
Revenue relationships
Support the ways fitness businesses actually collect money.
Recurring plans are central, but the full financial relationship may also include add-ons, packages, appointments, classes, retail, merchandise, credits, and adjustments.
Recurring memberships
Primary plans and recurring add-ons with billing cadence, renewal, account status, and member context.
Packages & services
Prepaid sessions, appointments, assessments, recovery services, and other one-time purchases.
Point-of-sale revenue
Retail, merchandise, drop-ins, and desk transactions connected to inventory and the member where appropriate.
Credits & adjustments
Refunds, credits, discounts, account corrections, and other changes with an auditable operating reason.
The billing lifecycle
The financial relationship should remain understandable from agreement through resolution.
Each stage adds context the next stage should not have to reconstruct.
Authorize
Connect the agreement, plan, package, service, amount, cadence, and payment method.
Collect
Process recurring and one-time obligations while preserving the member and revenue context.
Recognize
Separate successful collections, failures, refunds, credits, adjustments, and open balances.
Resolve
Coordinate payment updates, recovery, member support, access decisions, and account changes.
Reconcile
Match transactions, settlements, adjustments, and reporting back to the operating record.
Exceptions in context
A failed payment is a member situation—not only a processor response.
Attendance, membership value, service use, communication, access, and prior account history can change the right next action.
Payment signals · sample workspaceIllustrative data
MemberAmountRelationshipEngagementStatus
Alex Rivera$129.00Semi-privateLow visitsPast due
Sam Kelly$149.00UnlimitedDecliningFailed
Casey Moore$79.00Training add-onActivePast due
Riley James$65.0024/7FrequentFailed
Connected to the rest of the platform
The financial record becomes more useful when the surrounding workflows understand it.
Memberships, services, scheduling, access, communication, and reporting should use the same account truth instead of maintaining parallel versions of payment status.
MBMembersPlans, add-ons, packages, balances, history, and the full relationship.
SCSchedulingPaid services, package usage, eligibility, appointment status, and completion.
CRCRM & journeysPayment reminders, recovery communication, member support, and follow-through.
ACAccess controlAccount status, membership policy, eligibility, and access exceptions.
RPReportingRevenue, collections, recurring mix, past due, refunds, and reconciliation.
Payments questions
What operators usually need to understand.
The right billing setup depends on memberships, add-ons, packages, services, locations, payment rules, access policies, and the way the team resolves exceptions.
Can BuzOps handle recurring and one-time payments?
Yes. The financial relationship can include recurring memberships and add-ons alongside packages, appointments, classes, retail, merchandise, credits, and other one-time transactions.
How do payments connect to memberships and services?
Transactions can retain the member, plan, package, add-on, service, or point-of-sale context behind the charge so billing history and operational history stay aligned.
What happens when a recurring payment fails?
The failed obligation can be surfaced with the member relationship, amount, plan, attendance, services, communication, and account history. The exact recovery and access workflow should be configured around the business policy.
Can BuzOps track refunds, credits, and adjustments?
Refunds, credits, discounts, and account adjustments can be recorded with the related transaction and operating reason so reporting and reconciliation reflect the change.
How do multi-location payments work?
Multi-location setups can preserve the shared member and account relationship while still reporting transactions, services, registers, and revenue by location where needed.
How is existing billing data moved into BuzOps?
The transition plan depends on the current processor, memberships, future billing obligations, balances, payment methods, transaction history, packages, locations, and required integrations. Those details are mapped before a specific migration sequence is recommended.
See your revenue model in BuzOps
Bring the memberships, add-ons, packages, services, payment exceptions, access policies, and reporting requirements that shape the financial operation.
A useful walkthrough should show how money moves through the real member relationship—not only how a transaction is processed.