# MRRdue — failed-payment recovery for subscription SaaS Canonical page: https://www.mrrdue.com/ Content last revised: 2026-10-22 Support: support@mrrdue.com --- ## What MRRdue is MRRdue connects to a Stripe or Dodo Payments account with a read-only key, imports the subscription and invoice history, and turns failed payments into a ranked list of customers who need a human today. For each case it explains what failed, what the provider will do on its own, and what the operator should do now — with a drafted recovery email ready to send. What it does not do: it never charges a card, retries a payment, changes a subscription, or cancels anything in the connected billing account. At connection time it sends a write-shaped request to three record IDs that cannot exist (one customer, one invoice, one subscription) and reports whether the key was able to write. That establishes the key cannot write those three resources; it is not a survey of every resource in the account, and MRRdue says so. MRRdue can email an end customer on the workspace's behalf. That is off by default and gated twice: the workspace must enable managed sending, and automatic sending is a separate opt-in on top of it. --- ## The problem: involuntary churn Not every customer who leaves a subscription meant to. Cards expire, banks decline renewals, and a payment fails quietly. The billing provider records the failure and retries on its own schedule, but it does not tell the business which of those customers to chase first or what to say to them. If nobody acts, the subscription is cancelled when the retries run out. That is involuntary churn: revenue lost to a payment problem rather than a decision to leave. MRRdue is built for founders and small teams running one billing account who do not have a revenue-operations person and want to know which failed payments need a human today. --- ## How it works 1. Connect read-only. Paste a Stripe restricted key or a Dodo Payments API key. Full Stripe secret keys are rejected outright, and the write-access probe described above runs at connection time. 2. MRRdue imports subscription and invoice history and turns every failed payment into a case, ranked by the revenue at risk, with the failure reason and what the provider will do on its own. New failures arrive through the provider's events, backed up by a scheduled check that catches anything delayed or missed. Alerts go out by email or Slack. 3. Each case comes with a recovery email written for that failure reason and a payment link. Templates: https://www.mrrdue.com/templates/recovery-emails 4. A person decides what goes out: send it yourself, hand the case to Slack, a signed webhook, n8n, Zapier or Make, or switch on MRRdue's managed sender. Sending is off by default. Webhook Doctor watches Stripe webhook delivery and alerts when a signing secret broke after a redeploy, an endpoint is returning errors, or events were received but never processed — failures that otherwise silently make revenue numbers wrong. It is included on every plan. Try the full flow on sample data, with no signup: https://www.mrrdue.com/demo --- ## Pricing One plan, Pro: $29 per month or $290 per year (about two months free). Every feature is included; there is no per-seat charge and no percentage of recovered revenue. Everything MRRdue ships today for one provider account. Best for: founders and operators monitoring one billing account. Included: - Failed-payment recovery queue with risk scoring - Ready-to-send recovery emails & payment links - MRR, churn & retention-risk signals - Webhook Doctor broken-webhook alerts - Email, Slack alerts & daily summaries - Automatic outreach handoff to your systems - Outbound event webhooks & live read-only REST API - CSV/JSON recovery exports - Up to $100K tracked MRR · 24-month history - 14-day trial, no card required. The trial starts when a billing provider is first connected, not at signup. - Cancelling keeps access until the end of the paid period, and a scheduled cancellation can be resumed from Settings → Billing. - After a trial or subscription ends, synced data is kept for 30 days so you can pick up where you left off. - MRRdue's own subscription is billed through Dodo Payments; the provider account you connect for monitoring stays separate and read-only. Pricing page: https://www.mrrdue.com/pricing --- ## Principles - Read-only by design: no card charges, payment retries, refunds, subscription changes or cancellations in the connected billing account. - No card or bank data: MRRdue does not ask for or store card numbers, CVCs or full bank account numbers. Provider keys are encrypted at rest and used only on the server. - You decide what gets sent: customer email is off by default, automatic sending is a second, separate opt-in, and AI assistants can draft a campaign but only a signed-in person can approve it. - No invented numbers: every figure comes from the workspace's own billing data. --- ## Company MRRdue is operated by Akash Yadav, a sole proprietor registered in Balrampur, Uttar Pradesh, India. Bootstrapped, no outside investment. Founder: Akash Yadav — X @akashyadav_dev (https://x.com/akashyadav_dev) Support and all enquiries: support@mrrdue.com - About: https://www.mrrdue.com/about - Contact: https://www.mrrdue.com/contact - Security and data access: https://www.mrrdue.com/security - Privacy policy: https://www.mrrdue.com/privacy - Terms of service: https://www.mrrdue.com/terms --- ## Machine-readable versions - https://www.mrrdue.com/llms.txt — site map for language models - https://www.mrrdue.com/llms-full.txt — the full site content as one plain-text file - https://www.mrrdue.com/index.md · https://www.mrrdue.com/pricing.md · https://www.mrrdue.com/about.md · https://www.mrrdue.com/faq.md · https://www.mrrdue.com/mcp.md — markdown versions of the key pages - https://www.mrrdue.com/agents.txt — how AI agents connect over MCP - https://www.mrrdue.com/sitemap.xml — every public URL