Stripe decline code
try_again_laterA temporary issue at the issuer side. The charge should succeed if retried soon.
Type
Recoverable
Frequency
Commontry_again_later indicates the issuer is temporarily unable to process the charge: internal system issue, network congestion, or a brief outage. Like processing_error, recovery is high on short retries.
Retry in 2-4 hours. If it fails again, retry after 24 hours. If it still fails, something more permanent is going on; stop and escalate.
No outreach needed initially. Retry quietly.
Temporary issue. The card is still valid. High recovery rate with proper retry timing.
Stripe suggests 2-4 hours. Retrying within minutes may hit the same issuer issue. After the first retry fails, space additional attempts at least 12-24 hours apart.
How Rebounce handles try_again_later
Rebounce classifies every failed payment by its Stripe decline code and applies the optimal recovery strategy automatically. For try_again_later, that means intelligent retries at the right times. Multi-channel follow-up through email, SMS, WhatsApp, and in-app banners ensures the customer actually sees the message.
processing_errorSoft declineA temporary error occurred at Stripe or the card network while processing the charge.
issuer_not_availableSoft declineThe card issuer could not be reached by the card network. A temporary issue.
reenter_transactionSoft declineThe issuer returned a generic "try again" response, indicating a transient problem.