What decline re-routing is
Decline re-routing retries a card payment through a different payment processor after the first processor returns a decline. The second processor sends a new authorization request, which the card issuer evaluates. The issuer can still decline it, so rerouting does not guarantee approval.
This differs from intelligent payment routing, which selects where to send a payment before the first authorization attempt. Decline re-routing is the follow-up action after a failed attempt. The term does not describe a single network rule or a standard network fee.
A second authorization can recover a sale, but every retry needs a reason and a cost check.
Which declines to retry
Use the response code to separate temporary or technical failures from firm rejections. An issuer or connection outage can make a second attempt through another processor worthwhile. The second processor may receive a different outcome because it has a separate connection or processing path.
Do not reroute hard declines such as an expired card, a lost or stolen card, or an issuer security rejection. Repeating an authorization after a clear rejection does not fix the underlying problem. Request a new payment method when the card or issuer response requires it.
What retries mean for your costs
A retry is another authorization attempt. Your pricing may include a separate authorization or transaction charge for that attempt, so recovered sales must be weighed against the added processing cost. There is no universal decline re-routing fee or standard amount in the information available here.
Repeated retries on hard declines add costs without a sound recovery path and can attract scrutiny from payment providers or card networks. Compare approvals recovered through the second processor with the extra attempts and charges. A higher approval rate alone does not prove the routing change improved your net results.
What you can actually change
Your rules determine which response codes trigger a retry, which processor receives it and when the customer sees a final decline. Set clear limits and judge the results by recovered sales after added processing costs.
- Retry only response codes classified as retriable by your processor.
- Exclude hard declines and set a maximum of one secondary-processor attempt.
- Track approval outcomes and added authorization charges by retry reason.
- Compare recovered revenue after fees, not approval rate alone.
- Map response codes. Record which codes trigger a retry, which stop the flow and which require the customer to provide another payment method.
- Set a retry limit. Configure one attempt through a second processor and prevent repeat submissions for hard declines.
- Measure net recovery. Compare the value of sales recovered through rerouting with the additional authorization and processing charges.
Frequently asked questions
Is decline re-routing the same as intelligent payment routing?
No. Intelligent payment routing selects a processor before the first authorization attempt. Decline re-routing sends an eligible failed payment to a different processor for another attempt.
Does decline re-routing guarantee an approval?
No. The card issuer evaluates the second authorization request and can decline it too. A different processor changes the processing path, not the issuer's decision or the cardholder's account status.
Does decline re-routing add a fee?
There is no single standard fee for decline re-routing. Each retry is another authorization attempt, and your processor pricing may charge for that attempt. Compare the additional charges with the sales recovered through retries.