Failed Payment Best Practice Guide

Created by Customer Support, Modified on Thu, 12 Feb at 2:21 PM by Customer Support

A Practical Framework for First Class users

Failed direct debit payments are a normal part of running a recurring class-based business. The key is not eliminating them entirely — but managing them consistently and professionally.


This guide outlines a simple, structured approach to reduce admin time, improve recovery rates, and protect customer retention.


1. Understand What a Failed Payment Signals

A failed payment is not just a finance issue. It can indicate:

  • Insufficient funds

  • Expired card

  • Bank change

  • Disengagement from lessons

  • Financial stress

Repeated failed payments may signal an increased cancellation risk.

Best Practice:
If a customer has two failed payments within 30 days, consider proactive outreach.


2. Use a Clear 3-Step Recovery Process

To avoid reactive decision-making, implement a standard process:

Step 1 – Automatic Retry

  • Allow the system to automatically retry failed payments (typically after 3 days).

  • Enable SMS notifications to inform the customer.

Step 2 – Personal Follow-Up

If the retry fails:

  • Contact the customer via SMS or phone.

  • Confirm funds are available.

  • Confirm card details are up to date.

Step 3 – Escalation

If payment remains outstanding after 7–10 days:

  • Decide whether to pause enrolment.

  • Consider adjusting future debit amounts to recover the balance.

Consistency reduces confusion for both staff and customers.


3. Limit Automatic Retries

Repeated automatic retries can:

  • Increase payment gateway fees

  • Frustrate customers

  • Create unnecessary admin work

Recommended:
Limit to 1–2 automatic retries before human follow-up.


4. Prevent Expired Card Failures

A significant portion of failed payments are due to expired cards.

Prevention Strategy:

  • Review expiring cards monthly.

  • Send reminders 30 days before expiry (if supported by your gateway).

  • Encourage customers to update details early.

Proactive prevention reduces dishonour rates significantly.


5. Set a Weekly Failed Payment Review

Assign one team member to review failed payments weekly.

Suggested process:

  • Run the failed payment report.

  • Contact outstanding payers.

  • Confirm retry dates.

  • Monitor repeated dishonours.

A structured weekly review prevents balances from quietly accumulating.


6. Avoid Large Accumulated Balances

If failed payments are not addressed quickly, balances can grow across multiple billing cycles.

This can:

  • Overwhelm customers

  • Increase cancellation risk

  • Make recovery more difficult

Best Practice:
Do not allow unpaid balances to exceed two billing cycles without contact.


7. Communicate Clearly and Professionally

Use neutral, non-confrontational language.

Example SMS:

Hi Sarah, just letting you know yesterday’s payment did not go through. It is scheduled to retry on Friday. If your card details have changed, you can update them here.

Clear, calm communication improves recovery rates.


8. Track Failed Payment Metrics

Monitoring trends can provide early warning signals.

Track monthly:

  • Failed payment rate (% of total debits)

  • Recovery rate

  • Average recovery time

  • Common failure reasons (expired card, insufficient funds)

For most swim schools and academies, a healthy failed payment rate is typically between 2–5% of total debits.

Consistently higher rates may indicate process or communication gaps.


Summary

An effective failed payment process should:

  • Automate the first retry

  • Automate SMS notifications

  • Limit repeated retries

  • Include structured follow-up

  • Review weekly

  • Treat dishonours as a retention signal, not just a debt issue

A consistent process reduces admin load and protects long-term revenue.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article