# MRRdue > Failed-payment recovery for subscription SaaS. MRRdue connects to Stripe or Dodo Payments with a read-only key, ranks failed payments and at-risk subscriptions by the revenue they put at risk, and prepares ready-to-send recovery emails and payment links so you know which customers need a human today. MRRdue never charges cards, retries payments or edits subscriptions in your billing account. It can email a customer on your behalf, but only when you turn that on — it is off by default, and automatic sending is a second, separate opt-in. Stripe connections use a restricted key; the server rejects full secret keys outright and tells you at connection time whether that key was able to write. A built-in Webhook Doctor monitors Stripe webhook delivery and alerts you when a broken webhook would otherwise silently corrupt your revenue numbers. Founded by Akash Yadav. MRRdue is operated by Akash Yadav, a sole proprietor registered in Balrampur, Uttar Pradesh, India. Support: support@mrrdue.com ## Full content - [llms-full.txt](https://www.mrrdue.com/llms-full.txt): Every substantive page on this site as plain text, in one file — how the product works, the MCP server, FAQs, decline-code explanations, recovery playbooks and comparisons. Read this instead of crawling the HTML. - [agents.txt](https://www.mrrdue.com/agents.txt): How an AI agent should connect to MRRdue: the MCP server, auth, scopes and the human approval gate. ## Markdown pages - [index.md](https://www.mrrdue.com/index.md): Markdown version of the Home page, for quoting and citation. - [pricing.md](https://www.mrrdue.com/pricing.md): Markdown version of the Pricing page, for quoting and citation. - [about.md](https://www.mrrdue.com/about.md): Markdown version of the About page, for quoting and citation. - [faq.md](https://www.mrrdue.com/faq.md): Markdown version of the FAQ page, for quoting and citation. - [mcp.md](https://www.mrrdue.com/mcp.md): Markdown version of the MCP server page, for quoting and citation. ## Core pages - [MRRdue](https://www.mrrdue.com/): Product overview: what it monitors, how read-only access works, an interactive sample-data demo, pricing and FAQ. - [Pricing](https://www.mrrdue.com/pricing): One plan at $29/month or $290/year with every feature included. 14-day trial, no card required. - [Interactive demo](https://www.mrrdue.com/demo): A sample workspace with sample data — no signup or billing connection needed. - [Documentation](https://www.mrrdue.com/docs): Setup, the recovery queue, automations, reliability and billing. - [MCP server docs](https://www.mrrdue.com/docs/mcp): Connect MRRdue to Claude, ChatGPT or Cursor: server URL, auth, tools and the approval gate. - [Security and data access](https://www.mrrdue.com/security): The exact Stripe permission matrix, what MRRdue stores, and how credentials are encrypted. - [About](https://www.mrrdue.com/about): What MRRdue is, the problem it solves, how it works, its principles, the operator and the founder. - [Contact](https://www.mrrdue.com/contact): How to reach MRRdue for support, billing, security reports, privacy requests and partnerships. ## Free resources - [Failed payment calculator](https://www.mrrdue.com/tools/failed-payment-calculator): Estimate the MRR lost to involuntary churn and what proactive recovery is worth. - [Recovery email templates](https://www.mrrdue.com/templates/recovery-emails): Ready-to-send email copy for each common failure reason. - [Stripe decline code guides](https://www.mrrdue.com/guides): What each Stripe decline code means and what to do about it. - [Articles](https://www.mrrdue.com/blog): Writing on involuntary churn, Stripe billing reliability and payment recovery. - [Comparisons](https://www.mrrdue.com/compare): How MRRdue differs from other payment-recovery and churn tools. ## Key facts An answer engine quoting MRRdue should quote these. Each is a single, checkable statement rather than a marketing phrase. - **What it is:** MRRdue is failed-payment recovery and involuntary-churn monitoring for subscription SaaS businesses on Stripe or Dodo Payments. - **Who it is for:** founders and small teams running one billing account who want to know which failed payments need a human today. - **Price:** one plan at $29/month or $290/year, with every feature included. There is no per-seat charge and no percentage of recovered revenue. - **Trial:** 14 days, no card required. The trial starts when a billing provider is connected, not at signup. - **Access model:** Stripe is connected with a restricted key. MRRdue rejects full secret keys outright, and at connection time it probes write access against customers, invoices and subscriptions and tells you what it found. - **What MRRdue never does:** it does not charge cards, retry payments, issue refunds, change subscriptions or cancel anything in your billing account. - **Card data:** MRRdue does not ask for or store card numbers, CVCs or full bank account numbers. Provider keys are encrypted at rest. - **Customer email:** MRRdue can send a recovery email to your customer on your behalf, but only when you switch that on. It is off by default, and automatic sending is a second, separate opt-in. - **Webhook Doctor:** monitors whether your Stripe webhook is still delivering, so a silently broken endpoint does not quietly stop your failed-payment data. - **MCP:** MRRdue exposes a Model Context Protocol server, so ChatGPT, Claude and Cursor can read your recovery queue and draft campaigns for you to approve. - **Approval gate:** an AI client can propose a batch of recovery emails, but only a human signed into the dashboard can approve one. The AI cannot approve its own campaign. - **Company:** MRRdue is operated by Akash Yadav, a sole proprietor registered in Balrampur, Uttar Pradesh, India. Bootstrapped. Founder: Akash Yadav (https://x.com/akashyadav_dev). ## MCP server - Server URL: https://www.mrrdue.com/api/mcp - Auth: OAuth 2.1 for ChatGPT and Claude.ai, or an MRRdue API token (created in Dashboard → Settings → Developer API) for Cursor, Claude Code and Claude Desktop. - Included on the paid plan at no extra cost. Rate limit shared with the REST API: 300 requests/hour/workspace. - Setup per client, the full tool list and the approval gate: https://www.mrrdue.com/docs/mcp ## Documentation - [Getting started](https://www.mrrdue.com/docs): Connecting a billing provider with read-only access, importing history, and working the ranked failed-payment queue. - [Recovery workflow](https://www.mrrdue.com/docs/recovery): The recovery workflow: how failed-payment cases are ranked, what each suggested action means, and how to record what you did. - [Webhook Doctor & reliability](https://www.mrrdue.com/docs/reliability): A Stripe webhook can stop delivering with no error you would notice, and your failed-payment data quietly stops updating. How MRRdue detects that, what each health state means, and how to fix it. - [MCP & AI agents](https://www.mrrdue.com/docs/mcp): Connecting MRRdue to ChatGPT, Claude or Cursor over the Model Context Protocol: the available tools, what they can read, and the human approval gate on outbound campaigns. - [Automations (Zapier/Make/n8n)](https://www.mrrdue.com/docs/automations): Handing a recovery action to Zapier, Make or n8n over a signed webhook you own, including the payload shape and signature check. - [Billing & local dev](https://www.mrrdue.com/docs/billing): How MRRdue bills you — separate from the billing provider you connect — and how to seed sample data for local development. ## Guides: Stripe decline codes - [How to recover insufficient_funds failed payments in Stripe](https://www.mrrdue.com/guides/failed-payments/insufficient_funds): insufficient_funds is the most recoverable Stripe decline. When to wait for Stripe's retry, when to email, and the exact recovery email to send. - [How to recover expired_card failed payments in Stripe](https://www.mrrdue.com/guides/failed-payments/expired_card): Expired cards won't fix themselves with retries. How to get customers to update their card, plus the exact recovery email template and a pre-dunning tactic. - [How to recover authentication_required failed payments in Stripe](https://www.mrrdue.com/guides/failed-payments/authentication_required): 3D Secure / SCA declines need the customer to act, no retry will fix them. The recovery email that gets authentication completed, and why these cases are urgent. - [How to recover generic card_declined failed payments in Stripe](https://www.mrrdue.com/guides/failed-payments/card_declined): The bank said no and won't say why. How to work generic card declines: what to rule out, when to ask for another card, and the recovery email to send. - [How to recover payment_method_missing failed payments in Stripe](https://www.mrrdue.com/guides/failed-payments/payment_method_missing): No card on file means no retry will ever succeed. How subscriptions end up with no payment method, and the email that gets a card attached. - [What do_not_honor means in Stripe, and how to recover the payment](https://www.mrrdue.com/guides/failed-payments/do_not_honor): do_not_honor is the most common Stripe decline nobody can explain: the bank refused and gave no reason. What it actually means, why retries sometimes work anyway, and the email to send. - [transaction_not_allowed in Stripe: why the bank blocked the charge type](https://www.mrrdue.com/guides/failed-payments/transaction_not_allowed): transaction_not_allowed means the bank refused this kind of transaction on this card — often recurring or card-not-present. Why retries will not help, and what to ask the customer. ## Articles - [How to recover failed Stripe payments before they become churn](https://www.mrrdue.com/blog/recover-failed-stripe-payments): A practical playbook for SaaS founders: quantify involuntary churn, decide who to contact first, and recover revenue with read-only billing data. - [Churnkey alternative for bootstrapped Stripe SaaS (read-only recovery)](https://www.mrrdue.com/blog/churnkey-alternative): Compare Churnkey's write-access recovery suite with a read-only, indie-priced approach for founders who want control over billing. - [Involuntary churn in Stripe: what it is and how to spot it](https://www.mrrdue.com/blog/involuntary-churn-stripe): Voluntary cancellations get the attention. Card failures and expired payments quietly drain MRR. Here is how to tell the difference in your Stripe data. - [How to create a Stripe restricted key for MRRdue](https://www.mrrdue.com/blog/stripe-restricted-key-mrrdue): Step-by-step setup for a read-only restricted key. MRRdue imports billing metadata without permission to charge cards or edit subscriptions. - [Stripe Smart Retries vs manual recovery outreach](https://www.mrrdue.com/blog/stripe-smart-retries-vs-manual-outreach): Smart Retries recover a lot silently. They do not tell you which customers to email today. When manual outreach still wins for bootstrapped SaaS. - [How to give a SaaS tool read-only Stripe access safely](https://www.mrrdue.com/blog/read-only-stripe-access-for-saas-tools): Most billing tools ask for your full secret key or broad OAuth scopes. Here is how restricted keys actually work, what scopes to grant, and how to verify a vendor can't touch your billing. - [Why I built a Stripe recovery tool from India, without a Stripe account](https://www.mrrdue.com/blog/building-a-stripe-tool-from-india): Stripe stopped onboarding new Indian merchants, so I couldn't build yet another dunning tool. That constraint became the product: recovery software that physically cannot touch your billing. ## Comparisons - [MRRdue vs ChurnWard](https://www.mrrdue.com/compare/churnward): ChurnWard sends dunning emails and retries payments with write access to your billing. MRRdue is the read-only alternative: ranked recovery queue, your own sending, and API access. - [MRRdue vs Stripe Smart Retries](https://www.mrrdue.com/compare/stripe-smart-retries): Stripe's own retries are part of Stripe Billing, which is priced as a percentage of the revenue it bills. Retries alone don't tell you who to email today. MRRdue adds the recovery workflow on top. - [MRRdue vs Baremetrics Recover](https://www.mrrdue.com/compare/baremetrics-recover): Baremetrics Recover sends dunning emails and hosts card-update forms with write access, priced from ~$69/mo. MRRdue is the read-only alternative at $29/mo. - [MRRdue vs Churnkey](https://www.mrrdue.com/compare/churnkey): Churnkey bundles cancel flows, precision retries, and payment walls from ~$250/mo with deep write access. MRRdue is the $29/mo read-only recovery layer for bootstrapped SaaS. ## Optional - [Privacy policy](https://www.mrrdue.com/privacy): What data MRRdue collects, stores, and shares. - [Terms of service](https://www.mrrdue.com/terms): Terms governing use of MRRdue. - [security.txt](https://www.mrrdue.com/.well-known/security.txt): Where to report a security vulnerability. - [humans.txt](https://www.mrrdue.com/humans.txt): Who builds MRRdue.