Free during beta · no recovery cut

Recover failed payments. Keep the customer.

Dunlo reads the Stripe failure, chooses the right recovery path, and gives sensitive accounts back to a human before the message goes out.

Stripe OAuthNo card storageFounder review
Dunlo dashboard showing failed payments, recovery status, and revenue at risk

Product capture · example workspace

Failure-aware recovery

The decline decides the next move.

A failed payment is not one problem. Dunlo translates Stripe's signal into the right timing, message, or human handoff.

The card expired

expired_card
What Dunlo says
Send a secure Stripe-hosted payment update link.
Next action
Request a card update

The customer may need time

insufficient_funds
What Dunlo says
Use a calm message and retry at a more useful moment.
Next action
Delay and retry

The bank needs customer approval

authentication_required
What Dunlo says
Guide the customer through Stripe's SCA confirmation path.
Next action
Request authentication

No useful reason, or a sensitive account

generic_decline

No useful reason · sensitive/high-value account

What Dunlo says
Pause automation and surface the Stripe context to a person.
Next action
Manual founder review

One event in Stripe. One clear recovery path.

Dunlo turns payment failures into a visible sequence your team can understand, edit, and trust.

Start free in beta
Dunlo recovery sequence for a failed Stripe card payment
  1. 01

    Connect Stripe

    OAuth connects the payment context without exposing your Stripe credentials.

  2. 02

    Let the failure speak

    Each decline code selects a timing, message, and secure customer action.

  3. 03

    Recover or review

    Routine paths run. Sensitive accounts wait for your decision.

Founder review

Automation knows when to stop.

High-value or ambiguous failures land in a focused review queue. Dunlo prepares the Stripe context and a draft. You decide what the customer receives.

Failure context
At a glance
Before send
Founder decides
Start with founder control
Dunlo founder escalation queue with Stripe payment context and a prepared recovery email

Product capture · example workspace

Recovery estimate

Find the revenue already hiding in Stripe.

Move your MRR. Dunlo exposes every assumption behind the estimate, because recovery should feel measurable—not magical.

$1,000$20,000

$6,000

Failed MRR at risk

$300

Annualized estimate

$2,232

Estimated recoverable this month

$186

Illustrative estimate using an assumed 5% failed-payment rate and 62% recoverability. It is not a benchmark result or a guarantee. Model updated July 2026.

Beta transparency

What can be verified today.

Dunlo publishes assumptions, recovery mechanics, and its proof policy before it publishes customer outcomes.

During beta, customer outcomes are published only with approval and enough context to be useful.

Visible assumptions

The public benchmark exposes the illustrative failed-payment bands and 62% recoverability assumption used in its model. Updated July 2026.

Inspect the public model

Visible mechanics

Failure reasons, recovery timing, customer update links, and founder review are documented before signup.

See the mechanics

Visible proof policy

Customer metrics and stories remain private until the sample is useful and the customer approves publication.

Read the proof policy
Mathieu Chambaud, founder of Dunlo

Built and supported by Mathieu Chambaud

A founder-led beta with a public standard for proof.

I built Dunlo to make failed-payment recovery more specific and less awkward for customers. Beta feedback goes directly to me.

Follow @mathchambaud

Beta pricing

Free during beta. No recovery cut.

Dunlo will communicate any pricing change before billing starts.

Beta plan

$0

until beta ends

Start free in beta
  • Stripe failure-reason detection
  • Recovery emails matched to the failure
  • Stripe-hosted payment update links
  • Founder review for sensitive accounts
  • Recovered-payment tracking

Straight answers before you connect Stripe.

Is this just Stripe Smart Retries with nicer emails?

No. Stripe can retry cards. Dunlo handles the customer-facing recovery layer around Stripe: message, timing, founder review, and recovered-payment reporting.

Will customers know an automation sent the email?

The copy is plain, specific, and tied to the payment reason. High-value or sensitive accounts can pause for founder review before anything is sent.

How does Dunlo connect to Stripe?

Dunlo uses Stripe OAuth. You authorize access in Stripe and can revoke that connection from Stripe or Dunlo.

Does Dunlo store card numbers?

No. Card updates happen through Stripe-hosted flows. Dunlo uses payment and subscription context, not full card numbers or CVC data.

Do I pay during beta?

No. Dunlo is free during beta and does not take a percentage of recovered revenue during that period. Pricing changes will be communicated before billing starts.

Can sensitive accounts require founder review?

Yes. Important accounts can pause before a message is sent so a founder can review the Stripe context and prepared draft.

Free during beta

Recover the payment. Keep the customer.

Start free in beta