Stripe subscription recovery — beyond Smart Retry.

Stripe Smart Retry uses ML to time up to 4 retry attempts after a payment fails. It recovers roughly 15–25% of failed charges. What it doesn't include: a recovery email sequence, subscription pause or cancellation interception, card health monitoring, or any configurable retry rules by decline type. Recurflux adds all of those on top of Smart Retry.

Stripe retries within a window it doesn't fully disclose — typically within the first 30 days after the failure. The timing is determined by Stripe's ML model, which you have no control over. Recurflux runs its retry logic and recovery email sequence during that same window.

Stripe sends one default "payment failed" email. The content and branding are minimal and not configurable without significant custom development. Recurflux replaces this with a fully branded recovery email sequence: up to 6 emails with subject line testing, custom timing, and per-failure-type messaging.

No. Recurflux connects via Stripe OAuth with read-only access to subscriptions and charges. It does not modify your billing configuration, pricing, or subscription data in Stripe.

No. Stripe Smart Retry fires immediately after the failure and uses Stripe's ML-determined timing. Recurflux operates on top of that — handling the email sequence, decline-code-specific retry logic, and retention flows. They don't interfere with each other.

Smart Retry is a black box: up to 4 attempts, Stripe-determined timing, no configurability. Recurflux maps all 30+ Stripe decline codes to specific retry windows — insufficient funds retries at a different cadence than expired card or card not supported. You see exactly what's being retried, why, and what the outcome was.

Recurflux currently supports standard Stripe accounts. Connect platform support — recovery emails across connected accounts in a marketplace setup — is on the roadmap.