Failed gym payments and the rules for billing and access

Write a separate answer for each part of the membership:

• Collection: which invoice remains owed, whether another attempt is appropriate, and what evidence confirms payment.
• Attendance: whether the person can visit or book, which membership covers them, and what happens when grace ends.
• Contract and future billing: whether the membership continues, when a pause or cancellation takes effect, and what happens to later invoices.

A replacement card can leave an invoice unpaid. A restriction on attendance can leave the contract in place. Paying an invoice can remove a payment restriction while a freeze or missing waiver still prevents attendance. Staff need to see which decision has actually changed before promising that everything is resolved.

Stripe can save a card without creating a charge. Its payment status guidance also distinguishes an incomplete or processing payment from a successful one. Use the confirmed payment result, rather than the fact that someone finished entering card details, when deciding whether a bill has been paid.

Sources:[1][2]

A grace period is a decision about how long otherwise eligible members may continue using a membership while payment is unresolved. Compare the deadlines your software supports using completed groups of failed invoices:

1. For each candidate deadline within the period you have observed, calculate how much of the starting balance remained unrecovered. Include unresolved invoices; timing among successful recoveries alone leaves them out.
2. Identify which recorded visits or bookings each deadline would have restricted under the proposed rules. Check existing bookings as well as permission to make new ones.
3. Choose a deadline whose remaining unpaid balance, allowed attendance, and follow-up your business can handle within the agreement and applicable requirements. Assign a staff review before that deadline for cases automation cannot resolve.

This comparison uses payment behavior observed under your current policy. Treat it as planning evidence, not a forecast of how members will respond to a different deadline. Compare later completed groups using the same measurement window.

Capacity belongs in that decision. If grace permits bookings, state whether a member can reserve a place in a full class and what happens to that booking if grace ends before the class. Record unpaid dues and reserved places separately; do not assume every reservation represents a lost sale.

The retry schedule and access deadline need separate rules. A further attempt may be appropriate after access has been restricted, subject to the payer's authorization and provider rules. It should not quietly extend the grace period unless your stated policy provides for that. Stripe Billing's retry guidance describes its own retry schedules and hard-decline limits; check which features your membership software actually uses.

Sources:[3]

State the event that starts grace and the exact deadline, including the time zone. An invoice becoming due, a payment failing, and software first recording that failure can happen at different times. If your software counts elapsed hours, check the deadline across clock changes.

Where a system uses a fixed grace period, plan follow-up and staff review around that supported window. A suggested policy duration is not proof that the software can implement it.

Your policy needs an answer for the next renewal even when this month's visit is blocked. Review the membership agreement, applicable requirements, and software behavior before choosing how attendance restrictions affect future billing.

If billing continues, specify when staff will review the account before another period is charged. Otherwise, an account can move from one unpaid renewal into several while staff are treating it as one unresolved incident. Make the continuing billing terms clear to the payer.

If you approve a pause or stop future billing, record the effective date and decide what happens to invoices already prepared or issued. Review existing amounts separately under the agreement; a change to future billing does not, by itself, tell staff how those amounts should be handled. Your membership pause policy should explain the treatment of already-paid days and upcoming charges.

Ending a membership also needs an effective date and a review of any remaining balance. Give the payer separate confirmation of the membership decision and the billing outcome. An access restriction, a cancellation request, and an approved cancellation should be distinguishable in the record.

Use these cases to test your agreement, staff instructions, and software together. The next steps are review decisions, not a claim that every system produces the same access outcome.

These cases expose gaps that a rule such as "seven days, then suspend" leaves unanswered. In particular, decide which debt affects membership access. A shared account may also contain retail or separately purchased activities; its total unpaid amount need not be the balance your membership restriction uses.

Assign an owner and review date when a payer questions the amount, says they have withdrawn payment permission, or reports that an attempted repair did not resolve access. Also review accounts with repeated unsuccessful recovery and payments whose outcome remains uncertain. A provider retry schedule cannot resolve a disagreement about the invoice or permission to charge.

Use the provider's instructions for the actual failure. Stripe's decline codes distinguish cases that need a new card, payer verification, or another action. They also limit what should be disclosed: suspected fraud and cards reported lost or stolen should be presented as a general decline.

Sources:[4]

A payer asking why a bill is wrong is different from a dispute opened with their card issuer. For an issuer dispute, follow the provider's dispute process. For future charges to a saved card, check the permission the payer gave; Stripe's setup guidance requires permission for future off-session payments. Keep that authorization question separate from the membership agreement and its cancellation terms.

Sources:[5][1]

At the front desk, give staff an access answer and a private handoff when billing review is needed. Record the reviewer, what needs checking, and when the payer should expect a response. Before the next visit, check whether the agreed repair changed the bill, access, or both.

Use a worksheet built from invoice, payment, and follow-up records. Agree the definitions before comparing reports or changing the policy. Counting retries as failures, or counting card updates as recovered payments, will answer a different question from how much overdue membership money you collected.

Start with unique membership invoices whose first confirmed failed card collection fell in the same week. Track the amount overdue at that first failure and give every invoice the same elapsed observation window. The illustrative method below uses 14 days per invoice; it is a review choice, not a recommended grace period or an industry target. Wait until every invoice has had the full window before comparing groups.

Report weekly staff workload separately from the fixed invoice groups, so one contact is not added to several recovery groups. Keep credits and write-offs separate from confirmed payments; they can change the amount owed without collecting money. Exclude new invoices and extra fees from the starting balances in this worksheet, and measure dues before provider fees. Bank payouts are a separate figure. If you rerun the review, retain the same observation window instead of adding later recoveries to earlier results.

Suppose 10 unique invoices enter the review, each with $100 overdue. During each invoice's 14-day window, four are paid in full, two receive $50 each, and four receive nothing. Assume no refunds, chargebacks, credits, or write-offs in this example.

Full invoice recovery is 4 of 10, or 40%. Amount recovered is $500 of $1,000, or 50%. Six invoices still need attention, including the two partly paid. The two measures give the owner different work to review even though they describe the same payments.

Each week, review the latest group whose observation windows have finished. Keep a separate current list of unresolved accounts for follow-up. Several people on one family membership are not several failed payers; keep person, billing-account, and invoice counts distinct. Use your own history to set review triggers, and avoid presenting a change in recovery as proof that one reminder or grace setting caused it.

Complete the worksheet before changing settings or publishing new terms. Check that the agreement, staff instructions, and supported software behavior agree.

Record payer, guardian, and pickup roles separately in your family membership records. Pickup permission alone does not authorize access to billing details. Direct the payer to a secure payment form, and limit staff access to the details needed for their work. The Federal Trade Commission's business privacy guidance recommends minimizing retained information and restricting access. Do not collect card numbers or security codes by email.

Sources:[6]

Adapt this example to your actual agreement, software, and chosen policy. The fields make the invoice, attendance deadline, and next billing decision explicit.

We couldn't collect [amount] for [service period]. Invoice [reference] remains unpaid.

Please open [secure billing account URL] and follow the payment steps. Saving a new card does not, by itself, pay this invoice.

Under your membership's grace policy, access continues until [date, time, time zone], provided the other membership requirements are met. If the membership balance covered by that policy remains overdue then, [describe the affected access].

Your next billing period is [date]. While this is unresolved, [state what the agreement provides for future billing and any agreed review]. For help or to question the amount, contact [billing contact].