Failed-payment recovery

Every week a recovery agent pulls failed charges and expiring cards from your billing provider, segments customers by failure cause, and drafts matched recovery emails — you approve every send before it goes out.

Join the waitlist

What it installs

Agents 1

  • Payment Recovery Agent

    Owns the weekly failed-payment run: pulls failures and expiring cards, drafts cause-matched outreach for approval, and logs outcomes.

Workflows 1

  • Failed-payment recovery

    Pull failures and expiring cards, segment by cause, draft matched outreach, approve the batch, and log outcomes.

Documents 1

  • Recovery tracker

    The living record of every failed payment: recovered MRR, outstanding balances, and write-offs.

Goals 1

  • Failed payments recovered before they become churn

    Keep involuntary churn low by catching every failed charge and expiring card within a week.

Skills 2

  • failed-payment-segmentation

    Segment failed charges by decline type and run the dunning stack — pre-dunning expiry alerts, decline-aware retries, a timed four-email sequence, grace period, hard cancel — against recovery benchmarks. Adapted from coreyhaines31/marketingskills/churn-prevention.

  • recovery-outreach-writing

    Write the four-email dunning sequence — day 0 friendly alert, day 3 reminder, day 7 urgency, day 10 final warning — with a no-login payment link, concrete loss framing, and blameless plain-text copy. Adapted from coreyhaines31/marketingskills/churn-prevention.

Schedules 1

  • Weekly recovery run

    Runs the failed-payment recovery cycle weekly: pull failures, segment, draft, approve, log.

Connected services pick at least 1 of 4

  • Stripe

    Connects to Stripe so the recovery agent can read failed charges, card expiry dates, and subscription status for the customers it drafts outreach to.

  • Paddle

    Connects to Paddle so the recovery agent can read failed transactions, card expiry dates, and subscription status for the customers it drafts outreach to.

  • Polar

    Connects to Polar so the recovery agent can read failed orders, payment-method state, and subscription status for the customers it drafts outreach to.

  • PayPal

    Connects to PayPal so the recovery agent can read failed transactions, billing-agreement state, and subscription status for the customers it drafts outreach to.

Folders 1

  • Payment recovery

Requirements

What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.

  • Billing data in your payment provider — The agent reads failed charges, card expiry dates, subscription status, and customer records from the billing provider you pick during setup (Stripe, Paddle, Polar, or PayPal). Until that access is authorized, it works from failure exports you attach to the run.

Setup guide

How to Automate Failed Payment Recovery

A practical guide to recovering failed subscription payments with an agent: segmentation, retry logic, drafted emails, and approvals.

Read the setup guide

Install Failed-payment recovery and run it with approvals.

Join the waitlist and we will send early access when the first private beta spots open.

Private beta. We invite teams in batches and never share your email.