Decline code 264: Retry In a Few Days
By Jay Stevens · Principal EngineerReviewed by Jordan MederichUpdated 2 min readQuick answer
NMI response code 264 — “Declined: Retry In a Few Days” — is a soft decline where the issuer is signalling a temporary problem with the card or account and explicitly inviting a later retry. Per NMI’s documentation the right action is to wait and re-attempt in a few days, not to re-run the charge immediately. It’s one of the most recoverable declines because the issuer itself is telling you a retry will likely succeed.
What code 264 means
Explicitly retryable — NMI response code 264 is the issuer telling you to try again in a few days. Schedule a retry 3–5 days out rather than re-attempting immediately.
Cross-processor equivalents
The same issuer decision surfaces under a different code on every processor. Here is how code 264 maps across the stacks Revatto recovers on.
Why it happens
- A temporary issuer-side hold or processing condition on the account.
- A transient limit or velocity flag the bank expects to clear shortly.
- Short-lived account maintenance on the issuer’s side.
How to recover it
- 1Don’t retry immediately — the issuer explicitly asked you to wait a few days.
- 2Schedule a single retry 3–5 days out, when the temporary condition has likely cleared.
- 3If that retry also fails, send a light customer nudge — the condition may not be transient after all.
- 4Track repeat 264s on the same card; a persistent “retry later” is worth a human follow-up. Revatto does all of this for you — AI schedules the timed retry, and a real team steps in over email and SMS if it doesn’t clear — and you only pay if the payment is recovered.See how Revatto recovers 264declines →
See what Revatto would recover for you
Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.