What causes an unable to route transaction decline?

The card network could not deliver the authorization to a bank, usually because routing tables somewhere are stale or the card's network is not reachable through your processor's connections. No bank ever saw or judged the transaction.

Is code 92 my processor's fault or the card's?

Either. If one card range fails everywhere, the issuer's routing registration is the problem. If assorted cards fail only through one processor or MID, that route's connectivity or tables are to blame and your processor should investigate.

Decline code · Soft decline

Decline code 92: Unable to Route Transaction

The network could not find a path to deliver the authorization to a financial institution. The destination implied by the card number or the transaction's routing details does not resolve to a reachable endpoint. It is a delivery failure at the routing layer rather than a decision by any bank.

Should you retry?

Retries succeed when the routing problem heals or when the retry travels a path with correct tables, so a delayed retry and an alternate-route retry are both rational. If a specific BIN consistently cannot route, stop resubmitting it on that path and escalate; repetition without a path change is noise.

Why code 92 happens

The BIN routes to a destination the network cannot currently reach, sometimes during issuer migrations between processors.
Debit network routing selected a network the card does not actually participate in.
Acquirer routing tables are stale or misconfigured for the card range.
The card belongs to a regional network unavailable through your acquiring connections.
A newly issued BIN range has not fully propagated through routing tables.

What to do about it

Determine whether the failures follow a card range or your route: one BIN failing everywhere is an issuer-side routing gap, many BINs failing on one MID is your acquirer's tables.
Report persistent BIN-specific failures to your processor, who can chase the routing gap with the network.
For debit-heavy traffic, review your routing configuration and preferred-network ordering with your processor.
Retry the transaction later or through an alternate route while the routing issue is chased.

Frequently asked questions

What causes an unable to route transaction decline?: The card network could not deliver the authorization to a bank, usually because routing tables somewhere are stale or the card's network is not reachable through your processor's connections. No bank ever saw or judged the transaction.
Is code 92 my processor's fault or the card's?: Either. If one card range fails everywhere, the issuer's routing registration is the problem. If assorted cards fail only through one processor or MID, that route's connectivity or tables are to blame and your processor should investigate.

Related decline codes