Short answer: A practical dunning process treats a failed charge as an event to investigate, not proof of churn: use processor-supported retries, neutral notices, a secure payment-method update path, and locally reviewed pause or cancellation rules. Stripe documents configurable retry policies, but its settings are not a universal timetable for every studio.
Source and method note (checked 2026-09-01): This guide uses Stripe’s Smart Retries documentation for retry and subscription-status capabilities and the PCI Security Standards Council FAQ on card verification codes for payment-data handling. The source registry contains no independent yoga-studio failure-rate or recovery-rate dataset, so this page does not repeat the prior 5–8% or 60–70% claims. Recommendations below are operational patterns to test, not performance guarantees.
Start with an event record, then separate collection work from member judgment. Store the invoice or subscription identifier, amount, currency, payment method type, processor response, attempt number, next scheduled attempt, and the eventual outcome. That record lets a studio distinguish a transient failure, a hard decline, a missing payment method, a member-requested cancellation, and an unresolved account without guessing why someone left.
| Stage | Studio action | Record to review | Boundary |
|---|---|---|---|
| Failure | Capture the event and response code. | Invoice, amount, method, attempt count. | A failed charge is not proof of intentional churn. |
| Retry | Apply a documented processor schedule. | Attempt date, result, next attempt. | Hard declines may require a new payment method. |
| Notice | Explain the issue and offer a secure update route. | Channel, timestamp, delivery status. | Do not promise recovery or threaten access. |
| Account status | Apply the written membership and processor rule. | Past-due, unpaid, paused, or canceled status. | Contract and local-law review may be required. |
Stripe’s Smart Retries documentation says the recommended default is eight tries within two weeks, while allowing a one-week to two-month policy window and custom schedules. It also says a processor cannot automatically retry certain hard declines without a new payment method. Those are Stripe settings, not a universal yoga-studio timetable. If another processor is used, document its actual retry controls and test them against your own events.
Choose a schedule by asking what the studio can support: how quickly a member needs notice, when access status changes, how refunds or credits are reconciled, and who handles exceptions. Keep the schedule stable long enough to compare cohorts, but do not treat a single recovery percentage as proof that the schedule caused the result.
Use a neutral, specific message: “We could not complete this month’s membership payment. We will retry according to our billing settings. You can update your payment method through the secure link, or contact the studio if you need help.” Identify the invoice or billing period when appropriate, explain the next event, and provide a human contact. Do not imply that a member intended to cancel, and do not make urgency or access consequences more definite than the signed terms and actual account status.
Define the status transition before a failure occurs. Stripe documents options such as canceled, unpaid, and past-due states after a retry schedule ends, but a studio’s membership agreement, consumer-protection obligations, processor settings, and accessibility practices still matter. There is no universal 14-day, 21-day, or 60-day rule that this page can safely prescribe. State the notice, access, billing, reinstatement, and cancellation steps in plain language, then have the responsible operator review them locally.
The PCI Security Standards Council explains that card verification codes cannot be retained after authorization and are not needed for card-on-file or recurring transactions. Staff should therefore use the payment provider’s approved hosted or tokenized update flow and should not write down or retain CVV or other sensitive authentication data. Whether a phone workflow is permitted depends on the implementation and compliance scope; consult the acquirer, payment brand, or qualified assessor rather than treating this article as a legal conclusion.
Use definitions that another staff member can reproduce. Failure rate is failed billing attempts divided by billing attempts during a named period. Recovery rate is eligible failed attempts paid within a stated window divided by eligible failed attempts. Net recovered billings should subtract refunds, credits, and processor fees where those costs are in scope. Break results down by payment method, decline reason, retry stage, notice channel, and member cohort. The result is a local operating measure, not a benchmark for every yoga studio.
Mako disclosure: Mako publishes this guide and offers studio-management software. The page makes no claim that Mako or any other system will recover a given share of failed payments, prevent cancellations, or satisfy every local compliance requirement. Verify the workflow against the processor and the studio’s own records.
There is no universal number. Stripe documents a recommended default of eight tries within two weeks, plus configurable policies, but another processor may differ. Start with the settings you can document, then compare recovery, complaints, cancellations, and unresolved balances by cohort.
Do not record CVV or other sensitive authentication data. Use a provider-approved hosted or tokenized update process whenever possible, and confirm the remaining compliance obligations with the acquirer or qualified assessor. The safe workflow depends on implementation, not on a generic script.
Follow the written membership terms and the processor’s documented status rules, with local legal review where required. Tell the member what happens next, preserve account history, and record the effective date. Avoid presenting a single day count as a universal legal answer.
Next step: If you want to inspect a studio workflow that keeps billing, member records, and staff review in one place, open the Mako demo and validate the fit against your own process.
Related reading: Yoga Studio Late Cancel and No-Show Policy: Designing Rules That Work; How to Set Up Automated Dunning for Your Fitness Studio.
