Merchant attrition warning signs in your residual data

Attrition is the quiet tax on a residual portfolio. Every merchant that leaves takes its residual with it, for good, and in most ISOs nobody notices until the line reads zero. By then the merchant has already signed with someone else.

The frustrating part is that the warning was usually in the data for months. A residual report is a monthly record of each merchant's volume, transactions, fees and profit. Read across months instead of one month at a time, it tells you who is fading. This guide covers the signals, a simple rule for flagging them, and what to do with the month or two of notice they give you.

Why it matters more than new sales

Industry figures for merchant attrition vary widely and depend on who is counting, but rates of 10% to 20% a year are commonly cited, and higher for small merchants. Whatever your number is, it compounds against everything else you do. An office adding 10 merchants a month while losing 8 is growing at 2, and paying full acquisition cost for the 10.

Retention is also cheaper. Winning a merchant back after they have signed elsewhere means beating a contract and an early termination fee. Keeping one who is unhappy usually means a phone call.

The six signals

The first four are warnings. The last two are news. The aim is to act on the warnings before the news arrives.

A rule you can apply every month

A rule does not need to be clever to be useful. It needs to run every month without anyone remembering to do it. This is the one we use, and it catches most of what matters:

1. For each merchant, take profit in the current month and the two months before it.
2. Flag the merchant if profit fell 30% or more from the first month to the second, and again 30% or more from the second to the third, or fell to zero.
3. Ignore merchants with fewer than three months of history, so a new account's ramp-up does not trigger it.
4. Sort the flagged list by dollars at stake, the difference between the earlier peak and the current month, and start at the top.

A list of ten merchants sorted by money is something an owner will act on. A list of two hundred merchants sorted alphabetically is something they will close.

Volume and transaction counts make the rule sharper, and are worth adding once the profit version is running. The point is to start.

Separate attrition from seasonality

A merchant that always drops in January is not leaving in January. Before calling anyone, compare the current month with the same month last year, not just with last month. If your reports go back that far, this one comparison removes most false alarms. If they do not, start keeping them: twelve months of residual reports is the most valuable file in the office.

Also look at the whole processor. If every merchant on one processor fell in the same month, the cause is a rate change or a reporting change, not attrition.

What to do with the notice

The signals buy you a month, sometimes two. Use it:

• Call, do not email. Ask how the business is doing. Most merchants will say why volume dropped, and often it has nothing to do with you.
• Check the statement they see. A fee increase from the processor, a new monthly charge, or an annual fee landing is the most common trigger for shopping around. You may not have noticed it either.
• Check the equipment. A terminal that has started failing sends volume to a competitor's terminal sitting beside it.
• Involve the agent. The agent who sold the account usually has the relationship. Send them the flagged list, not just the owner.
• Know your number. If a merchant producing $150 a month is worth a $50 rate concession to keep, decide that before the call.

Sizing the problem honestly

Before you can measure attrition you need to know how many merchants you actually have, and the processor's file will not tell you directly. In one processor report we work with, nearly half the rows were closed or pending accounts, still listed with zeros, looking exactly like live merchants until you check the status column. Anyone counting rows would have overstated the book by almost double, and every average built on that count was wrong. Count active merchants, then track how many of them go inactive each month. That is your attrition rate, and it is the number to watch.

A monthly routine

1. When the reports arrive, count active merchants and compare with last month.
2. Run the two-drop rule and produce the flagged list, sorted by dollars.
3. Check each flagged merchant against the same month last year.
4. Send the list to the agents who own the accounts, with a deadline.
5. Record the outcome: saved, lost, or false alarm. After six months you will know which signals matter in your book.

Frequently asked questions

What are the warning signs a merchant is about to leave a payment processor? Falling volume over two or three months, transaction counts dropping faster than volume, rising chargebacks, and profit down 30% or more two months in a row. A closed status or close date on the report means the merchant has already gone.

What is a normal merchant attrition rate for an ISO? Published figures vary, and annual rates of 10% to 20% are commonly cited, with small merchants at the higher end. The more useful number is your own: active merchants that went inactive this month, divided by active merchants last month, tracked over time.

How do I find at-risk merchants in a residual report? Compare each merchant's profit across the last three months. Flag any merchant whose profit fell 30% or more in each of the last two months, or dropped to zero, and sort the flagged list by the dollars at stake.

Why did my residual drop when I did not lose any merchants? Usually a change in the mix rather than the count: a large merchant's volume fell, interchange shifted with the card mix, or a processor changed a rate or a fee. Look at the largest merchants first; a small number of them usually explain most of any monthly change.

Can residual software flag merchants at risk automatically? Yes. SplitRun applies the two-consecutive-drops rule described above to every merchant each month and lists the ten with the most dollars at stake, with the agent who owns each one, on the dashboard and in the agent's own report. The rule is the same one described here. See the sample agent report.

How does merchant attrition affect the value of a residual portfolio? Directly. Portfolio buyers price residual streams on their expected life, and a book with rising attrition is worth fewer months of income. Keeping attrition low is the single largest lever on what the portfolio is worth, whether or not you ever sell it. See Merchant portfolio concentration for the other risk buyers look at.