Changelog | RecoverFlow

Changelog

What has changed

Grouped by the day the work actually landed. Bug fixes that affected numbers shown to customers are listed as prominently as features, because those are the ones you would want to know about.

2026-07-28

Correctness pass on decline handling

  • Fixed six Stripe decline codes being treated as retryable when Stripe will not execute a retry for them without a new payment method: incorrect_number, transaction_not_allowed, revocation_of_authorization, revocation_of_all_authorizations, authentication_required and highest_risk_level. This also inflated the connect-time backtest estimate for accounts holding those failures.
  • Lost, stolen and retained cards now route to the card-update flow instead of being written off. A reissue is the most recoverable failure there is, because the customer usually already has the new card.
  • card_velocity_exceeded is now retried. It is a limit that resets, and Stripe retries it.
  • Dunning step 3 no longer tells customers their subscription will be cancelled. Whether that happens is the merchant's own Stripe setting, which RecoverFlow does not see or control.
  • Published twelve guides at /blog, plus /about, /contact and this documentation.

2026-07-27

Comparison and tooling

  • Four competitor comparison pages with pricing read from each vendor's own page and dated on-page, plus a comparisons hub.
  • Free recovery estimator and a searchable reference for all 48 Stripe decline codes.
  • Retry schedule builder and dunning email generator, completing the free tool set.
  • Pricing page, including a section on the volume at which 25% becomes the wrong deal for the customer.
  • Privacy policy, terms of service and security pages, with governing law in Massachusetts.

2026-07-13

Backtest and analytics

  • Instant 90-day backtest scan on Stripe Connect, so a new merchant sees what already failed before committing to anything.
  • DataProtection keys persisted across redeploys, so sessions survive a deployment.
  • Analytics on the marketing site.

2026-07-12

Billing, auth and deliverability

  • Usage-based billing: 25% of recovered revenue with a $29 monthly floor.
  • Magic-link authentication and the customer dashboard.
  • Self-serve signup funnel.
  • Dunning email deliverability fixes, including rejecting a placeholder SendGrid key at startup rather than silently sending nothing.
  • Open and click tracking disabled on dunning emails at the SendGrid level.

2026-07-10

First working system

  • Clean Architecture scaffold on .NET 8, with PostgreSQL and EF Core.
  • Stripe Connect OAuth, with the access token encrypted at rest.
  • Multi-tenant isolation via EF Core global query filters, so a query that forgets its tenant filter returns nothing rather than another merchant's rows.
  • Decline classification, retry scheduling and the retry execution worker.
  • Dunning email sending through SendGrid.
  • Read-only merchant dashboard API.
  • Deployment to Render.

RecoverFlow started on 10 July 2026. Anything older than that does not exist.