When retries pollute a merchant account

A cascade is extra attempts on the same unique order after attempt 1 failed. CRMs call this recycle. Gateways call it a retry or a hop. The job is the same. You are asking whether those hops recovered orders or only multiplied auths and chargebacks.

Pair: Cascade pollution calculator on Payment orchestration. The three rates (first-try, net, unique billing) are a different job: run first-try, net, and unique billing. CRM Recycle columns vs those hops is a different job: recycle ladder vs cascade. Dunning after a rebill fail is a different job: dunning by decline family.

What to count

First-try declines are unique orders that failed attempt 1. That is the pool hops could save.

Recovered orders are unique orders from that pool that billed on a later hop. One order, one recovery. Do not count the hop as a new order.

Extra auths are every attempt after attempt 1, successes and fails. Auths per recovered order is extra auths divided by recovered orders.

Extra chargebacks are primary disputes that landed on those hops. Blank is zero. A recovered order that later disputes still counts against the merchant account that took the hop.

If extra auths sit below recovered orders, you under-counted retries. If recovered orders sit above first-try declines, you mixed a unique-order file with a hop file.

What is pollution

Hops that burn auths and do not recover, hops that recover at a cost of auths you will not pay, and hops that stack chargebacks. Net approval can still look fine. Unique billing already keeps retries in the attempt count. This page asks whether the hops themselves were worth it.

Do not invent a lucky hop cap. If you have a line you will not cross, type it. Networks also cap retries. Ask this acquirer what they watch. We do not paste a program percent here.

Hard fails do not hop

Pick-up-card, lost, stolen, invalid account, and issuer fraud die on this merchant account. Kill the token. Do not send that PAN onto a “healthier” account. That second account inherits the same card and a worse story.

Soft declines (NSF, some do-not-honor) can retry on the same account. Opening a new merchant account for a do-not-honor is routing theatre. It is how you dump a spare.

3DS dollars versus conversion tax is a different job: Place 3DS only when the tax pays. Do not treat a 3DS fail as a reason to hop the same shopper around every enrolled MID.

After the readout

If auths per recovered order sit above the line you typed, cut hops. If extra chargebacks showed up on the retry account, cut those hops even when recovery looks cheap. If hard fails left this account, cut those codes off the second path today.

If the readout is calm, keep the hops that recovered clean sales. Still do not add a merchant account to chase one more point.

Related: Soft vs hard decline: next action (which families may retry), failover auth count, MIDs (every hop lands on one account), Chargebacks (the ratio on the account that took the retry), Subscriptions (rebill retries are a calendar, not a live-auth hop).