← Decline Codes
Soft Decline

Stripe Decline Code · Glossary

new_account_information_available

new_account_information_available is a lifecycle notification decline — the card network or issuing bank is signaling that the stored card details you have on file are outdated and a newer version of the same account exists.

Recoverable·55–75%·Updated May 2026

What It Means

What new_account_information_available actually means.

new_account_information_available is a lifecycle notification decline — the card network or issuing bank is signaling that the stored card details you have on file are outdated and a newer version of the same account exists. Unlike most decline codes that signal a problem with the transaction itself, this one is a data freshness signal: the customer likely has a reissued card, a new account number, or updated card details — and the network is telling your billing system to go get the new information before attempting further charges. It is a soft, recoverable decline with a well-defined resolution path.

Not sure if this code is recoverable for your specific situation? Use the Stripe Failure Lookup →

Why It Happens

The root causes.

  • 1Card reissued with new number after expiry or replacement — The most common cause: the issuing bank has issued a new card with a new PAN (Primary Account Number) to the same customer — the old stored card on Stripe points to a dead account number, and the network flags it with this code to indicate fresher details exist
  • 2Account number changed after fraud or compromise — The bank replaced the customer's card after detecting fraud or compromise on the old number — the new card is active and funded, but your stored card details still point to the cancelled number
  • 3Card upgrade or product change — The bank upgraded the customer from one card product to another (e.g., standard to premium) and issued a new card number in the process — the old number is deactivated but the account and customer relationship is entirely intact
  • 4Stored credential not updated via Account Updater — Stripe's Account Updater service (which automatically refreshes stored card details with Visa and Mastercard networks) either missed the update or the issuing bank isn't enrolled in the updater program — leaving your stored card stale while the network has the fresh details
  • 5Bank-initiated account restructuring — The issuing bank merged accounts, changed account structures, or reassigned card numbers during a system migration — the old card number no longer routes correctly but a valid replacement account exists

What NOT to Do

Common mistakes that make it worse.

✕ Don't treat it like a hard decline and route to a payment method switch email immediately

new_account_information_available is a data update signal, not a rejection — the customer's account is healthy and the bank is actively pointing you toward fresh card information. Sending a "your card failed, please add a new payment method" email before attempting Account Updater or asking for updated details is unnecessary friction that drives payment abandonment on an otherwise recoverable account.

✕ Don't retry with the same stale card details

Retrying with the exact same stored card information that triggered this code will produce the same decline every time — the old card number is dead and the network will keep telling you to update it. Any retry must be preceded by an Account Updater check or a customer card update.

✕ Don't ignore the Account Updater signal and jump straight to customer outreach

If your Stripe account has Card Account Updater enabled, Stripe may already have the refreshed card details available — check first before contacting the customer. For a meaningful percentage of new_account_information_available occurrences, an automatic card detail refresh followed by an immediate retry resolves the payment with zero customer interaction required.

Retry Timing

Optimal retry schedule.

new_account_information_available follows an Account Updater-first, customer-outreach-second recovery path.

Recovery Benchmark

What good looks like.

MetricResult
Overall recovery rate55–75%
Recovery via Account Updater (silent, no customer action)30–40% of all occurrences
Recovery via customer card update email50–65% of those who engage
Recovery with blind retry (same stale details)~0%
Recovery with Account Updater + targeted email65–75% combined
Prevention via Account Updater enrollmentEliminates 30–40% of occurrences entirely

A 65–70% overall recovery rate is the benchmark for teams with Account Updater enabled and a fast card-update email sequence. This is one of the most recoverable decline codes in the taxonomy — the customer has not churned, their bank has not rejected them, and the card network is actively helping you find the fix. The only variable is how quickly and smoothly you capture the updated payment details.

At Scale

How to handle it at scale.

Automated

  • ✓Webhook trigger: invoice.payment_failed → check failure_code === 'new_account_information_available' → immediately query Stripe Account Updater before any customer-facing action
  • ✓Account Updater auto-retry: If updated card details are returned → automatically update the stored payment method on the Stripe Customer object → immediately retry the failed invoice → if successful, close event silently with zero customer notification
  • ✓Email Day 0 — card replacement framing: If Account Updater returns no update or the retry on updated details fails → fire email within 60 minutes with warm, low-friction copy: Subject: "Your new card needs to be added — quick action needed" — body acknowledges the card was likely replaced and provides a direct one-click link to update payment details; frame as routine card replacement, not a payment failure
  • ✓Card update page optimization: Your payment update page should pre-fill everything it can from the existing card on file (card type, last 4 digits) to reduce friction — the customer just needs to enter their new card number and CVV; pre-filled context increases completion rates by 20–30%
  • ✓Alternate method offer — Day 3: If no update within 48–72 hours, add bank transfer, PayPal, or UPI as parallel options — some customers whose card was replaced may not have received the new physical card yet; alternate methods bridge this gap
  • ✓Account Updater enrollment check: Log a flag whenever this code fires for a card from an issuer not enrolled in Account Updater (bank_does_not_participate signal) — these cards will never be auto-updated and require faster customer outreach as a permanent workflow pattern

Manual Escalation

  • →High-ACV accounts: Personal outreach from a CSM within 2–4 hours — "Hi [name], it looks like your card was recently replaced — a common thing when banks issue new cards. Can you add your new card details? It takes 30 seconds and we'll process your payment immediately." — warm, human framing that contextualizes what happened and makes the next step feel easy
  • →Annual plan customers: For annual plan customers who haven't updated their card within 5 days, direct phone or video outreach — losing an annual plan customer to a card replacement non-update is one of the most avoidable involuntary churn scenarios; one personal touchpoint resolves it in the vast majority of cases
  • →Issuer not enrolled in Account Updater: For cards from issuers that don't participate in the Account Updater program, build a proactive expiry-based outreach sequence — 30 days before the known card expiry, email customers to update their card; this eliminates new_account_information_available failures from expiry-triggered replacements before they occur
  • →Recurring pattern — same cohort: If a cluster of new_account_information_available failures arrives simultaneously from customers who signed up in the same period, it likely indicates a bank-level mass card reissue event (data breach replacement, product migration) — run a batch Account Updater refresh and a targeted email campaign to the full affected cohort immediately

FAQs

Frequently asked questions.

What does the Stripe new_account_information_available decline code mean?

new_account_information_available means the card network is signaling that the stored card details on file are outdated and a newer version of the same account exists. The customer's account is healthy — the decline is a data freshness signal, not a rejection. The bank has issued a new card number to the same customer and the network is directing your billing system to retrieve the updated information before retrying.

What are the most common causes of a new_account_information_available error in Stripe?

Common causes include the bank issuing a new card number after card expiry or routine replacement, a card being replaced after fraud or compromise, a card product upgrade resulting in a new card number, stored credentials not being refreshed via Stripe's Account Updater service, and bank-side account restructuring or system migrations that reassigned card numbers.

How does Stripe Account Updater help with new_account_information_available?

Stripe's Account Updater service automatically refreshes stored Visa and Mastercard card details when the issuing bank reports a card number change. For new_account_information_available, enabling Account Updater resolves 30–40% of occurrences silently — Stripe fetches the new card details and retries the charge without any customer interaction. It is the highest-ROI single action for this specific decline code.

Should I retry a payment after a new_account_information_available decline?

Not with the same stale card details — that will fail identically every time. First run an Account Updater check to see if Stripe has refreshed card information available. If yes, update the stored payment method and retry immediately. If no update is available, send a card update email and retry only after the customer provides new card details.

What is the recovery rate for Stripe new_account_information_available failures?

Overall recovery rates are 55–75%, making it one of the highest-recovery decline codes. Account Updater resolves 30–40% silently with no customer action. Customer card update emails convert 50–65% of those who engage. Teams with Account Updater enabled and a fast card-update email sequence achieve 65–75% combined recovery.

What to do next

You are here

new_account_information_available

Decline code reference

↓

Check recoverability

Stripe Failure Lookup

See what's recoverable — and what isn't →

↓

Then

Sign up for Recurflux

Automate recovery for every decline code →

Before you retry

Most new_account_information_available failures are retried on the wrong schedule — which recovers the payment about 30% of the time. The other 70% leaves permanently. See what this code is actually costing at your MRR before deciding how to handle it.

See what new_account_information_available costs me →

Stop leaving revenue on the table

new_account_information_available is recoverable. Most teams don't have the retry logic to prove it.

Recurflux handles code-specific retry scheduling, adaptive dunning, and dispute intelligence across all 30 Stripe decline codes. Connect in under 5 minutes.

See what's leaking →All 30 decline codes →