← All articles

Martial arts school software with autopay (and failed card retry)

What autopay should do when a card is declined: retry, notify, stop after a limit and never charge twice. How BlackBeltCRM handles each step.

Autopay is on every buying checklist. What separates one system from another is the day a card fails. A declined card either becomes a quiet, recoverable event or a month of unpaid tuition that nobody noticed until the member stopped coming.

This article lists what a martial arts business should expect autopay to do on a bad day, and what BlackBeltCRM does at each step.

The normal day

Autopay runs early each morning in the business’s time zone. It collects every open item that is due on or before that day and marked to be paid automatically, from the card or bank account saved for the household’s primary billing contact. All of a household’s items go out as one charge, so a parent with three children sees one payment, not three.

You set autopay up once per payer: save the card or bank account on the primary billing contact, switch autopay on, and it takes over. A contact is charged from one account only, card or bank, never both.

It is also decided per billing line. A tuition line can be on autopay while a testing fee is paid at the front desk. That detail is covered on the billing and payments page.

When a card is declined

Here is the sequence in BlackBeltCRM:

  1. The charges stay unpaid. Nothing is marked paid and nothing disappears.
  2. The decline is written to the member’s history, and with BlackBeltCRM card processing it includes the reason the processor gave.
  3. The payer is emailed that the payment did not go through, and the email goes into the history too.
  4. The next morning’s run tries again.
  5. A convenience fee is not kept for a failed attempt. If the business adds a card fee to autopay, the fee for a declined attempt is removed, so a family never pays a fee on a payment that failed.

A daily retry needs a stopping rule.

When it stops

Every business sets how many card declines are allowed before autopay locks. The setting runs from 1 to 10 and the default is 3. When the count reaches the limit, autopay locks for that household and the history records it, so a card that keeps failing is not presented every morning.

With BlackBeltCRM card processing, some declines are final. A card reported expired, lost or stolen, or a cardholder who has asked to stop recurring charges, cannot be charged again. For those, autopay pauses for the household straight away without waiting for the count, and the history says a new card is needed.

When the processor does not answer

With BlackBeltCRM card processing, a technical failure on our side or the processor’s is treated differently from a decline. Nothing is charged, nothing is counted against the member, no email goes out, the history notes it, and the next run tries again.

The hard case is a charge with no clear answer, where nobody can say whether the card was charged. Autopay pauses for that household and the history says why. Staff check the payment with the card processor before the household is charged again. This is the rule that protects members from being charged twice.

Getting autopay back

The lock clears and the count starts over when a card payment is approved or a new card is saved. If the old card is the reason it keeps failing, update the card first. In the 3.0 release, the Collect payments page lists households that autopay is paused for and lets a manager charge one anyway, one household at a time.

A checklist for any software you are comparing

Ask each vendor to show you these on a live account, not a slide:

  • What does the member’s history say after a decline, and does it say why?
  • Is the payer emailed automatically, and is that email in the history?
  • How many tries before it stops, and can you change the number?
  • Does a final decline, such as a lost card, stop autopay at once?
  • What happens when the processor does not answer? If the answer is “it retries”, ask how a double charge is prevented.
  • Is a fee kept when the payment failed?
  • Where do you see everyone whose autopay is paused?

What we do not claim: a published recovery rate for failed cards. We have not measured one across our customers, and figures quoted elsewhere describe other businesses. For what the industry data says and where the limits are, see the members you are losing to expired cards.

If you want to see the full billing side, martial arts billing software shows the member and household views, and how to calculate churn rate shows how to separate payment failures from members who chose to leave.

Questions people ask

What happens when an autopay card is declined?

In BlackBeltCRM the charges stay unpaid, the decline is written to the member's history, the payer is emailed, and the next morning's run tries again. Any convenience fee for the failed attempt is removed.

How many times is a declined card tried?

Each business sets a limit for card declines, from 1 to 10, with 3 as the default. When the count reaches the limit, autopay locks for that account so a dead card is not charged every morning.

Can a member be charged twice if the card processor does not answer?

The system is built to prevent it. When the processor gives no clear answer, autopay pauses for that account and the history says so, so staff can check the payment before anyone charges again.

How does autopay start again after it locks?

The lock clears and the count starts over when a card payment is approved or a new card is saved. Update the card first if the old one is why it keeps failing.

Can one autopay card pay for several children?

Yes. Everything due on a household account is combined into one charge to the primary billing contact's saved card or bank account.