Skip to content

Decline code 06: Error

Jordan MederichBy Jordan Mederich · Co-Founder & CEOReviewed by Sean WeasUpdated 3 min read
Summarize with AI

Quick answer

Decline code 06 — “Error” — is a generic processing fault returned somewhere in the authorization chain: the acquirer, network, or issuer hit a system or formatting error rather than refusing the charge. Under the ISO 8583 standard it’s a transient, soft condition, so a retry after a short delay usually clears it. It’s the same condition Stripe reports as processing_error and that Authorize.net returns as response code 3 (“Error”). Recover it with a spaced retry, escalating to outreach only if it persists.

What code 06 means

Soft declineRetryable

A 06 is a transient processing fault, not an issuer refusal — a retry after a short delay (a few minutes to a few hours) usually clears it once the system glitch passes. Don't hammer it back-to-back; space the attempts.

Cross-processor equivalents

The same issuer decision surfaces under a different code on every processor. Here is how code 06 maps across the stacks Revatto recovers on.

ISO 8583
Code06
CalledError
Stripe
Codeprocessing_error
CalledProcessing error
Braintree
Code3000
CalledProcessor Network Unavailable
Authorize.net
Code3
CalledProcessing errortop-level responseCode 3 (Error)
NMI
Code260
CalledProcessor error
Chargebee
Codepayment_processing_failed
CalledPayment processing failed
Recurly
Codeprocessing_error
CalledProcessing error
IxoPay
Code1000
CalledProcessor error1000-series + 3000/4000/8000-series
Shopify
CodePROCESSING_ERROR
CalledProcessing error
Whop
Codeprocessor_error
CalledProcessor errornormalized — no processor-specific code (free-text categorized)

Why it happens

  • A transient system or timeout error in the acquirer, network, or issuer host while processing the authorization.
  • Malformed or incomplete message data — a missing or invalid field in the authorization request triggering a format error.
  • Network connectivity or routing problems between the processor and the issuing bank that interrupt the round trip.
  • Issuer-side maintenance or an overloaded host returning a generic error instead of an approve/decline decision.
  • A gateway or integration fault — a misconfigured request that the processor rejects as an error rather than a decline.

How to recover it

  1. 1Wait out the transient fault — retry after a short delay (a few minutes to a few hours) rather than re-firing the same request instantly.
  2. 2Confirm the request itself is well-formed: a 06 that repeats on identical data often points at a malformed field or integration bug, not the issuer.
  3. 3If retries keep erroring, stop treating it as transient — reach the customer on email and SMS, and confirm the card and details are current before the next attempt.
  4. 4
    When a 06 won’t clear on its own, a real person works the payment to completion. That AI-plus-human handoff is exactly what Revatto does for you: we recover the payment end to end, and you only pay if it works (20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime).See how Revatto recovers 06declines →

See what Revatto would recover for you

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

See Your Recovery Potential

Frequently asked questions