Skip to content

Decline code 55: Incorrect PIN

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

Quick answer

Decline code 55 — “Incorrect PIN” — comes from the cardholder’s issuing bank: the PIN entered with the transaction did not match the one on file. Under the ISO 8583 standard it’s a hard decline tied to a customer action, so an immediate retry won’t clear it. Stripe normalizes the broader family as an incorrect_number / invalid card error, and Authorize.net returns reason code 37 (card number invalid). Recovering it takes customer action or a card update, not blind re-attempts.

What code 55 means

Hard declineDo not retry

Don't blind-retry a 55 — the same charge will keep declining until the cardholder re-enters the right PIN, and on a card-not-present recurring charge there is no PIN to fix at all. Recover it with customer outreach or a card update, not back-to-back re-attempts.

Cross-processor equivalents

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

ISO 8583
Code55
CalledIncorrect PIN
Stripe
Codeincorrect_number
CalledIncorrect numberalso invalid_cvc, invalid_expiry_*
Braintree
Code2005
CalledInvalid Card Number
Authorize.net
Code37
CalledCard number invalidresponseReasonCode 37
NMI
Code220
CalledInvalid card data
Chargebee
Codeinvalid_card
CalledInvalid card
Recurly
Codeinvalid_card
CalledInvalid card
IxoPay
Code2007
CalledInvalid card
Shopify
CodeINVALID_PAYMENT_METHOD
CalledInvalid payment methodalso PAYMENT_METHOD_NOT_FOUND
Whop
Codeinvalid_card
CalledInvalid cardnormalized — no processor-specific code (free-text categorized)

Why it happens

  • The cardholder simply entered the wrong PIN at the terminal or checkout — a typo or a forgotten PIN.
  • The PIN on file with the issuer was recently changed and the cardholder used the old one.
  • A reissued or replaced card whose new PIN has not propagated, or whose old PIN no longer applies.
  • A card-not-present recurring charge attempted against a card record that expects PIN verification it can’t supply — the stored card details no longer match.
  • Issuer-side PIN verification failure or a temporary block after repeated incorrect PIN attempts.

How to recover it

  1. 1Don’t re-run the same charge right away — a 55 won’t clear on a blind retry, and repeated incorrect-PIN attempts can trip an issuer block on the card.
  2. 2Reach the customer on a channel they actually answer — email and SMS — let them know the payment didn’t go through, and ask them to re-enter the correct PIN or confirm an up-to-date card.
  3. 3When the card itself is the problem, get a current card on file — an updated number or a freshly added payment method clears the mismatch that drove the PIN failure.
  4. 4
    When it persists, a real person — not another automated email — works the card update directly. 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 55declines →

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