Recover revenuebefore it disappears.

MRRdue reads your billing data, finds the payments that failed, and ranks them by how much revenue is at risk. For each one it tells you who the customer is, why the payment failed, whether they are worth chasing, and what to send. You decide what actually goes out.

Stripe and Dodo Payments. Connect Stripe with a read-only restricted key, or Dodo Payments with a read-only API key, and MRRdue works the same way whichever you pick. One provider per workspace, and more are on the way.

You connect a Stripe restricted key scoped to read access on customers, subscriptions, invoices, prices, and products. MRRdue refuses full secret keys outright, and at connection time it tests whether the key can write to those resources and tells you what it found. The Security page lists the exact permissions and what that test does and does not prove.

No. MRRdue can read billing records and nothing else. It cannot charge your customers, change or cancel subscriptions, issue refunds, or move funds anywhere. That is enforced by your billing provider, not by a promise in our code.

Not unless you turn it on. By default MRRdue writes the recovery email and payment link and leaves it in the dashboard for you. You can send it yourself, hand the case to Slack, a signed webhook, n8n, Zapier, or Make so your own system sends it, or opt in to having MRRdue send it for you. Automatic sending is a separate second opt-in, and both are off by default.

The failure reaches MRRdue through your provider's events, backed up by a scheduled check that catches anything delayed or missed. The case is ranked against everything else that is open, a message is drafted for that failure reason, and you get an alert by email or Slack.

You can open the demo dashboard right now with sample data, no account needed. Connecting Stripe or Dodo Payments takes a few minutes, and your first ranked cases appear once the initial read finishes.

The 14-day trial starts when you first connect Stripe or Dodo Payments, not at signup, so the window only runs once MRRdue can read your real billing data. No card is required.

Yes. MRRdue ships a native MCP server, so your assistant can answer questions about your metrics, at-risk customers, and open cases in plain language. It connects over OAuth 2.1. An assistant can read your data and draft a batch of recovery emails, but it cannot approve one: approving a batch requires a human signed into the dashboard, and no assistant can approve its own. Nothing an assistant does can touch your billing account. Included in the paid plan.

No. MRRdue sits on top of Stripe or Dodo Payments, which stays your billing system. MRRdue is the layer that turns its data into recovery decisions.

Webhook Doctor flags it on its next scheduled check, about every 30 minutes. Because your Stripe webhooks arrive at MRRdue directly, it can see a signing secret that broke after a redeploy, events that stopped arriving, or events received but never processed — the silent failures that quietly make your revenue numbers wrong. You get an alert with the likely cause and the fix.

Your dashboard pauses until you upgrade. Your synced data is kept for a limited period so you can pick up where you left off.