Retry the charge on a fixed schedule that stays inside card network limits, text the member a secure payment link on day 1, and create a task for staff if the payment is still unpaid after the last retry. GoHighLevel retries subscription payments by default three times at one day intervals and exposes the status in the Subscription trigger, so the follow up text can start from the status. The bottom line: most failed payments are an expired card or a bank block, not a decision to quit, so the first message should make paying easy and say nothing about cancellation.

What HighLevel does when a subscription payment fails

A Growthable guide to HighLevel billing says a failed subscription payment generates an invoice, notifies the customer, and starts retries. The default is three retries one day apart, and you can set 1, 2, or 3 retries with intervals of 1, 3, 5, or 7 days. If the customer pays the invoice before a retry, the remaining retries stop. If every retry fails, the subscription stays unpaid, and you can choose to cancel it automatically in Payments settings. That guide does not say how long the automatic cancellation takes, so confirm it in your account.

HighLevel's Subscription trigger lets a workflow filter by status. The statuses include Incomplete Expired, which means the first payment failed when the subscription was created, Overdue, which means a second or later payment failed, and Unpaid, which means the subscription has pending or missed payments.

What the card networks allow

NetworkSoft declinesHard declines
VisaUp to 20 retries in 30 days, then a fee per excess attemptNever retry the same card; fees apply
Mastercard10 retries in 24 hours and 35 in 30 days before feesNo further attempts for the same card

PayPal's merchant guidance lists these limits, and fees such as $0.10 for a domestic Visa excess attempt, and notes that fees can change. A soft decline is a temporary problem such as insufficient funds. A hard decline, such as a closed account or a stolen card report, should never be retried. Keep your retry schedule well under these limits.

The message sequence

  1. Day 0, same hour as the failure: send a text that says the payment did not go through, names the amount, and links to a secure page to update the card. Do not include the card details in the text.
  2. Day 3: send a second text that says the payment is still open and gives the front desk phone number.
  3. Day 7: create a task for staff to call, and send a final note that states what happens to access if the balance stays open, quoting your contract terms.
  4. At any point, a Payment Received trigger ends the workflow and sends a one line thank you.

Rules to respect

Sample messages

Notice what the texts leave out: no card numbers, no threats, and no mention of cancellation. A member with an expired card is still a member.

Match the message to the cause

Likely causeWhat helps
Card expiredA link to update the card, since the new number is all that is needed
Insufficient fundsA second attempt a few days later, around a common payday
Bank blocked the chargeA short note asking the member to approve it with the bank, then a retry
Closed account or lost cardStop retrying, since a hard decline must not be retried, and ask for a new card

What to measure

Common mistakes

Questions people ask

How many times does HighLevel retry a failed subscription payment?

By default three times, one day apart. You can set 1 to 3 retries with gaps of 1, 3, 5, or 7 days.

Can a gym keep retrying a card that was declined for a closed account?

No. Visa and Mastercard treat those as hard declines and require merchants to stop.

What should the first message to the member say?

That the payment did not go through, the amount, and a secure link to update the card. Leave out any mention of cancelling.

To build the failed payment recovery sequence, start a GoHighLevel account here. The workflows are shown in our capabilities demo.