Skip to content

Failed payment recovery for IxoPay

Calum EwingBy Calum Ewing · Head of FulfillmentReviewed by Jay StevensUpdated 3 min read
Summarize with AI

Quick answer

IxoPay is a payment orchestration platform that routes transactions across multiple acquirers and PSPs, normalizes their decline codes, and can re-route or retry through cascading rules. What it doesn't do is run the customer-facing recovery — reaching the cardholder to get a new card. Revatto detects the failed payment from IxoPay, reads the normalized decline code, and runs an AI-timed email + SMS + human outreach sequence under your brand that drives the customer to update their card. It's done for you — 20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime.

The gap IxoPay leaves open

What IxoPay recovers on its own

  • IxoPay is a payment orchestration platform — it routes transactions across multiple acquirers and PSPs from a single integration.
  • Cascading and transaction-routing rules can re-route or re-attempt a failed charge through a different provider to improve authorization rates.
  • IxoPay normalizes each underlying processor's raw decline into a consistent code so the failure reason is readable across providers.
  • Its recovery is provider-side — orchestration and retry logic, not a customer dunning sequence that emails, texts, or calls the cardholder.
  • IxoPay stops at: IxoPay's cascading and retry rules address routing and provider-side failures, not a card the customer needs to update.Revatto adds: Email + SMS + a human recovery specialist that reach the cardholder under your brand to fix the card.
  • IxoPay stops at: IxoPay has no built-in customer dunning sequence — no failed-payment emails, SMS, or human follow-up.Revatto adds: A managed, AI-timed outreach cadence done for you, in place of a recovery flow IxoPay doesn't run.
  • IxoPay stops at: IxoPay normalizes the decline code but does nothing with it on the customer side.Revatto adds: Revatto reads that normalized code to time outreach — soft declines get a paced retry-prompt, hard declines go straight to the customer.
  • IxoPay stops at: IxoPay's API is built to orchestrate charges, not to run a win-back, so it can't re-attempt the payment for you as a recovery step.Revatto adds: Revatto runs the multi-channel outreach and drives the customer back to update their card, then stops the moment the payment clears.

How Revatto recovers failed IxoPay payments

  1. 1
    Detect the failureRevatto ingests IxoPay's failed-transaction webhook the moment a charge fails — no polling, no delay.
  2. 2
    Read the normalized declineIxoPay normalizes the underlying provider's raw decline into a consistent code, so Revatto can tell a soft retry-now from a hard needs-the-customer.
  3. 3
    Reach the customerEmail + SMS + a human recovery specialist contact the cardholder under your brand — the customer-facing sequence IxoPay's orchestration layer doesn't run.
  4. 4
    Drive the card updateRevatto guides the customer to update their card so the next charge clears — because recovery here runs through outreach, not a programmatic re-attempt on IxoPay.
  5. 5
    Stop on successWhen IxoPay reports the payment succeeded, Revatto ends the sequence automatically — no double-charge, no stray outreach.

How a IxoPay decline maps across stacks

A do-not-honor decline on IxoPay. Recovery looks the same across every stack Revatto runs on — here is how the same issuer decision is named on each.

ISO 8583
Code05
CalledDo Not Honor
Stripe
Codedo_not_honor
CalledDo not honor
Braintree
Code2000
CalledDo Not Honorgeneric issuer decline
Authorize.net
Code5
CalledDo not honorresponseReasonCode 5
NMI
Code201
CalledDo not honor
Chargebee
Codedo_not_honor
CalledDo not honor
Recurly
Codecall_issuer
CalledCall issuer
IxoPay
Code05
CalledDo not honorISO 8583 adapterCode 05 (refer to issuer)
Shopify
CodeDO_NOT_HONOR
CalledDo not honor
Whop
Codedo_not_honor
CalledDo not honornormalized — no processor-specific code (free-text categorized)
Fanbasis
Codedo_not_honor
CalledDo not honornormalized — matched by substring rule, no processor-specific code

See what Revatto would recover from IxoPay

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential

Frequently asked questions

Recovery, done for you

The same managed recovery layer runs on every stack — including IxoPay. Here is what it has recovered for our clients.

$55M+ ARR

Recovered for our clients

65,000+

Payments recovered

54%

Average recovery rate