Failed Payments & Recovery

Why cards decline, what Rotor does about it automatically, and the manual steps to update a payment method and re-run the charge — plus what to do when a recurring service plan keeps failing.

Written By Support Team

Last updated About 1 hour ago

A failed payment is not a lost payment. Most declines are boring and fixable: an expired card, a card that got reissued after a fraud alert, a balance that was $12 short on the wrong day. The businesses that collect well are simply the ones that look at the failed list every day and act on it while the customer still remembers the service.

The recovery work happens in Financials → Payments. See Financials: Invoices, Payments, and Payouts for the wider tour of that screen.

Why cards fail

The failure reason is shown on the payment when you open it. Broadly they fall into four buckets:

Expired card. The most common one on quarterly and annual plans, where months pass between charges.
Insufficient funds. Common on debit cards billed on a fixed day of the month. Often succeeds a few days later.
Issuer decline. The bank blocked the charge — fraud rules, a card reported lost, a card the customer closed, or a spending limit. You can't fix this from your side; the customer has to.
Bad or stale details. A wrong number, a wrong postal code, or a bank account that was closed.

What Rotor does automatically

Three things happen without you doing anything.

The failed payment is recorded and stays visible. Failed payments remain in the list until they are marked as reviewed, so they cannot quietly disappear behind newer activity. Use the Failed filter to isolate them.
Your team can be notified. There is a Failed payment event under Admin Notifications, deliverable by push, SMS, email, or in-app. Turn it on — a failed charge you learn about the same day is worth far more than one you find at month end. See Notifications.
The customer can be reminded about the unpaid invoice. Under Settings → Messaging, Invoice Payment Reminders lets you set multiple reminders at different intervals with custom text for each. See Client Messaging Settings.

What is not confirmed: [VERIFY: does Rotor automatically retry a failed charge on a schedule (smart retries), and if so, how many attempts over how many days?] [VERIFY: is the customer notified directly and immediately when their card declines, separately from the invoice payment reminder sequence?] Until those are confirmed, treat every failed payment as something a human has to pick up.

The manual recovery routine

Make this a daily five-minute habit for whoever owns collections.

Go to Financials → Payments and apply the Failed filter.
Open each failed payment and read the failure reason. It tells you which conversation to have.
Take the matching action from the table below — usually requesting a new payment method.
Update the payment method. The safest route is to send the client portal link from the customer's Paymentstab so the customer enters the new card themselves. See Payment methods on file and the client portal link.
Retry the charge in Rotor once the new method is saved. Don't wait for the next billing cycle — on a quarterly plan that's three months of float.
Mark the payment as reviewed so it drops off the list. Only do this once it's genuinely resolved or consciously written off.

When you call the customer, lead with the service, not the money: "Hey, we treated the perimeter on Tuesday and the card on file bounced — do you have a newer one?" That call succeeds far more often than an invoice reminder email.

Failure reasons and what to do

Failure reason	What it means	What to do
Expired card	The card's expiration date has passed	Send the client portal link for a new card, then retry. Retrying the same card will never work
Insufficient funds	Not enough money or credit available at that moment	Wait a few days and retry, or text the customer to ask when to run it. Often clears after payday
Card declined / do not honor	A generic issuer decline with no reason given	Ask the customer to call their bank or provide a different card. Repeated retries usually fail the same way
Lost, stolen, or closed card	The card number is dead	New payment method required. Do not retry
Incorrect number, CVC, or postal code	A detail was mistyped, usually on manual entry	Re-enter carefully, or better, have the customer enter it through the portal link
Bank account closed or details invalid (ACH)	The linked bank account no longer works	Collect new bank details, or switch the customer to a card
No payment method on file	The plan tried to bill and there was nothing saved	Send the portal link and confirm the plan's billing mode is what you intended

[VERIFY: confirm the exact wording of the failure reasons Rotor displays so this table matches the UI.]

When a recurring service plan keeps failing

One decline is noise. Three declines on a quarterly pest plan is a customer decision you haven't been told about yet.

Work it in this order:

Confirm it's a payment problem, not a service problem. Check the Conversations tab on the customer profile. A customer who wanted to cancel and never got a call back will simply stop paying.
Get a working method on file. Nothing else matters until this is done. On monthly and start-of-month billing, a card on file is required for the plan's billing to work at all.
Decide whether to keep servicing. Rotor will happily keep generating plan jobs while the balance grows. Set a house rule — for example, no further visits once two invoices are unpaid — and enforce it, because unpaid recurring service is the fastest way to turn a customer into a bad debt.
Pause or deactivate the plan. On the customer's service plan you can edit plan details or deactivate the plan, which stops future jobs from being generated. See Service Plans. [VERIFY: does deactivating a service plan cancel already-scheduled visits and pending jobs, or do those need to be cancelled individually?]
Deal with the outstanding balance separately. Deactivating the plan does not collect the money already owed. Those invoices stay in Financials → Invoices.

Before you cancel anything on an agreement-backed plan, check the cancellation terms in the signed agreement. That document sets what you're owed and what notice is required. For how each billing mode charges in the first place, see Recurring billing rules: when plans bill and what happens on failure.

Automating the follow-up

Beyond the built-in reminders, you can build a dunning sequence with workflows. Under Engagement → Workflows, an Invoice sent trigger plus Wait actions and a Conditional split on invoice status lets you text a customer three days later only if the invoice is still unpaid, then create a task for the office on day seven. Add a Send Notification action so a specific person owns the follow-up. See Workflows & Automations.

Turn on Respect Business Hours for those messages. Nobody updates a card because of a 2 a.m. text.

Habits that prevent failures

Check the Failed filter daily, not weekly.
Also check Jobs filtered to Completed plus Unpaid — that catches work that was never charged at all, which the failed list won't show you.
Before your busy season, sweep your active recurring customers for missing or expiring payment methods.
Set expectations at signup about when the card will be charged. Surprised customers dispute charges; informed customers update their card.
Mark payments reviewed only after they're truly resolved, so the list stays trustworthy.

Congratulations! You now have a repeatable routine for turning declined charges back into collected cash, and a clear point at which to stop servicing an account that won't pay.

Have additional questions? Our team is ready to help you succeed. Contact us through the chat or drop us an email at support@getrotor.com.

Still need help? Ask the team