Stripe decline code
reenter_transaction
The issuer asked for the transaction to be submitted again — a temporary, retryable condition rather than a hard decline.
Primary source: Stripe’s official decline codes reference
Why it happens
- A transient error on the issuer side.
- A momentary processing problem during authorization.
- Temporary network or issuer load.
Should you retry it?
Yes — retrying usually recovers it
The issuer itself asked to resubmit, so retrying the same card promptly is the right move.
How to recover it
Retry on a short schedule. Customer outreach is usually unnecessary unless it keeps failing.
Stripe's own retries usually clear temporary errors like this. Recoverly watches what's left: if the invoice is still unpaid after Stripe's retry schedule ends, it opens a case and — with your approval — emails the customer a Stripe-hosted payment page to finish the payment.
See how much failed-payment revenue you can recover
Connect Stripe (we only read) and Recoverly shows your recoverable revenue in 30 seconds.
Related decline codes
Written by the Recoverly team · Published June 25, 2026 · Last reviewed July 17, 2026
Recoverly finds invoices Stripe’s retries left unpaid and — with your approval — sends payment-update emails, then verifies what actually came back. This page is informational and not affiliated with Stripe.