Skip to content

Foxhound menu

Recovery sequences

Managing payments

Reading the payments list

The list at /recovery/payments holds every failed payment Foxhound has detected, newest first. A row carries the customer name and email, the amount, the decline category, the current status, and when the failure was detected. Open any row for that payment's own page.

Filtering and search

  • Search. Matches on customer name, email, or plan name.
  • Status tabs. All, Active, Recovered, Canceled and Failed.
  • Decline category. Narrows to one of the six categories.
  • Date range. Filters on when the failure was detected.
  • Amount range. A slider bounded by the smallest and largest amounts you actually have.
  • Sort. Newest first, oldest first, or by amount.

Every filter is a URL parameter, so a filtered view can be bookmarked or sent to somebody else and it opens the same way for them.

Rows per page

The selector above the table shows 10, 25, 50, 100, or all of them. It starts at 25.

Understanding payment statuses

A payment is in one of five states: Stripe retrying, active, recovered, canceled, or failed unrecovered, which every page labels Failed.

  • Stripe retrying. Stripe is still attempting the payment on its own schedule. Foxhound is watching and has planned no steps yet.
  • Active. The sequence is running and at least one step is still ahead of it.
  • Recovered. The invoice was paid, and every remaining step was canceled.
  • Canceled. You stopped the recovery, or the subscription behind it ended.
  • Failed. Every step ran and the payment did not come back. Nothing further happens on its own.
  • ActiveSequence running
  • RecoveredInvoice paid
  • FailedAll steps ran, no recovery
  • CanceledStopped by you, or the subscription ended
  • Stripe retryingStripe is still retrying

Reading a payment detail page

A payment's own page carries its whole timeline, from detection to the most recent step. Each step shows what kind it is, when it was scheduled, when it ran, and what came back: an email step shows the subject and the body that was sent, and a retry step shows what Stripe answered.

Example: a soft declineSoft
  1. Retry (early)

    4 hrRetry Failed
  2. Email (day 1)

    5 hrPending
  3. Retry (day 2)

    Day 2Pending
  4. Email (day 3)

    Day 3Pending
  5. Email (day 7)

    Day 7Pending
  6. Email (day 14)

    Day 14Pending
  7. Retry (day 21)

    Day 21Pending
  8. Email (day 30)

    Day 30Pending

Opens and clicks are recorded per email step, so you can see whether a message was read and whether the card-update link was followed. The click is the one that matters for billing.

Manual actions on a payment

  • Trigger next step now. Runs the next pending step immediately instead of waiting for its scheduled time.
  • Mark as recovered. Closes the payment and cancels the rest of the sequence. Use it when the customer paid some other way, which Foxhound has no way to see. A payment you mark recovered is never billed.
  • Stop recovery. Stops every future step for that payment. It does not touch the customer's subscription.
  • Resend last email. Sends the last email again and records it as its own step.
  • Note. A field for your own reference. It is never sent to the customer.

Note. Foxhound has no rewrite-the-pending-email control. Each email is written at send time from the customer, the decline and your brand voice, so there is no draft sitting there to edit.

Bulk actions

Select rows with the checkboxes and a bar appears at the bottom of the screen. Trigger the next step, mark recovered, or stop recovery for every selected payment at once. Above 25 payments Foxhound asks you to confirm, and one submission carries at most 100. Each payment is reported on its own, and any that did not go through stay selected.

Note. There is no undo. Stop recovery ends the remaining steps for every selected payment.

Exporting to CSV

Export CSV in the list header downloads the payments on screen: this page, with the filters, sort and rows per page you have on. Choose All in rows per page to export every payment that matches your filters.

Recovery sequences

How sequences are built by decline type

Declines are sorted into six categories: soft, network, expired, fraud, revoked, and unknown. Each gets its own schedule, spread across up to thirty days, chosen by what is actually wrong with the payment. When a retryable payment fails, Foxhound attempts a quiet retry before any customer sees an email, and only after that does the first email go out, with a hosted card-update link.

  • SoftSoft decline. The card is good, the charge was refused for now: insufficient_funds, do_not_honor, generic_decline
  • NetworkNetwork error. A processor or bank problem, usually passing: processing_error, issuer_not_available, try_again_later
  • ExpiredExpired card. The card has passed its expiry date: expired_card
  • FraudSuspected fraud. The issuer blocked the card: stolen_card, lost_card, fraudulent
  • RevokedRevoked authorization. The customer withdrew the mandate: revocation_of_authorization
  • UnclassifiedUnclassified decline. A decline code none of the five above lists, or none at all

Each category's steps in order, from the engine's own schedule table:

Soft decline: 8 steps
  1. Retry4 hr
  2. Email5 hr
  3. RetryDay 2
  4. EmailDay 3
  5. EmailDay 7
  6. EmailDay 14
  7. RetryDay 21
  8. EmailDay 30
Network error: 7 steps
  1. Retry4 hr
  2. RetryDay 1
  3. EmailDay 2
  4. EmailDay 7
  5. EmailDay 14
  6. RetryDay 21
  7. EmailDay 30
Expired card: 6 steps
  1. Email1 hr
  2. EmailDay 3
  3. EmailDay 7
  4. EmailDay 14
  5. RetryDay 21
  6. EmailDay 30
Suspected fraud: 5 steps
  1. Email2 hr
  2. EmailDay 3
  3. EmailDay 7
  4. EmailDay 14
  5. EmailDay 30
Revoked authorization: 1 step
  1. Email2 hr
Unclassified decline: 5 steps
  1. Email1 hr
  2. EmailDay 3
  3. EmailDay 7
  4. EmailDay 14
  5. EmailDay 30

Why so few retries for expired cards, and none for fraud? A retry on an expired card fails every time until the card is updated, and the card networks do not allow retrying the same card number and expiry. So an expired card gets one retry, on day 21, and it charges only if the card has changed since the decline: Stripe's card updater gave it a new expiry, or the customer added a card on the card-update page. Otherwise the step is skipped. Retrying a blocked card can draw further flags with the issuer, so fraud gets no retry. In both cases the main path to recovery is the customer acting, which is what the emails are for, and a revoked mandate gets a single email for the same reason. An unknown decline gets no retry at all. Emails only, failing closed: no silent retry against a code that has not been classified.

Why does network get an early retry at 4 hours? Network errors are usually passing: a processor hiccup or a bank briefly unavailable. Most clear within a few hours on their own, and the early retry catches those before any email is needed.

Reading the sequence performance page

The page at /recovery/sequence reads across your whole recovery history by category. For each step it shows how many went out, the open rate, the click rate and the most recent subject line used. A retry step shows how often the retry worked instead.

How recovery emails are written

Every email is written at send time. The AI is given the customer's first name, the plan, the amount, how long they have been a customer, the decline category, where the message sits in the sequence, your brand voice, and your merchant context when you have set it.

What comes back is checked before it goes anywhere: an email carrying hollow phrasing, hedging, or anything that reads like a billing system wrote it is rejected and the template goes instead. Delivery is never held up by the AI layer.

Tip. Send test email under Settings and Email delivers a real one to your own address through the same sending path, so you can read what a customer would get before anything fails.

Understanding your dashboard

Stat cards

Nine stat cards sit on the recovery dashboard: three across the top and six further down, under the recovery queue. They read the last 30 days whatever range is selected.

Dashboard stat cards
CardWhat it shows
Recovered (30d)What came back in the last 30 days.
Currently at riskThe total across every payment still in an active sequence, with its share of your MRR when Foxhound has an MRR figure.
Recovery rateThe share of failed payments that came back, colored by band: below target at 20% or less, near target from 21% to 35%, above target from 36%.
Active sequencesHow many payments are being worked right now.
Win-backs activeHow many canceled customers are in a win-back sequence.
Cards expiringCards inside the alert window.
Avg days to recoveryHow long a recovery takes, on average.
Best categoryWhich decline category is recovering best for you.
Emails sentRecovery emails sent in the last 30 days, with their open and click rates.

Date range filter

The 7d, 30d, 90d, and all buttons in the dashboard header change the window the trend charts, the decline breakdown, the win-back panel and the payments preview read from. The recovery timing chart stays on the last 30 days, as the stat cards do. The range starts at 30 days.

The recovery queue always shows the steps due in the next 48 hours, whatever the range.

The email deliverability panel, under the stat cards, follows the range: the share of the emails Foxhound sent that bounced or were reported as spam. Foxhound records each bounce and spam report against the account that sent the email, and when there are none in the range the panel says so. It shows no delivered rate, because Foxhound does not record delivery.

ROI widget

The Foxhound-attributed revenue panel shows what Foxhound recovered this month and over all time, counting only recoveries where a Foxhound action provably preceded payment, with the 20% fee on each and what you keep. This month counts every such recovery since the 1st, with the fee it will carry once it has held for 30 days; all time counts the ones that have held for 30 days, which are the ones Foxhound bills.

A recovery is billable only when a Foxhound action provably preceded payment: a scheduled retry succeeded, a dunning email was clicked or otherwise engaged (not just opened), or a card was updated through a Foxhound page. Everything else is Stripe's own baseline recovery, recorded and shown to you, never billed.

A click only counts if it came within 14 days before the payment came back. A customer who clicks and then pays two months later was not brought back by that email, so the recovery records as Stripe's own baseline and is free.

Note. Some clicks are not people. A click that arrives within 60 seconds of the email being sent, or on a link no human can see, is marked suspect: corporate mail scanners follow every link in a message before it reaches the inbox. A suspect click is shown on the ledger with its reason and is never billed.

Recovery rate benchmark

The dashboard shows no outside benchmark beside your rate. Its color comes from the bands above, not from a figure published by Stripe or anyone else.

Webhook health indicator

A badge in the dashboard header shows whether Stripe is still reaching Foxhound. A webhook inside the last day reads as receiving normally, nothing for a day reads as quiet, and nothing for more than three days is flagged as a problem worth checking. A brand new connection that has not seen one yet says so rather than reading as a failure.

Troubleshooting

A payment is not being detected

  • Is the Stripe account still connected? Settings and Stripe connections lists every live connection on this account.
  • Has Stripe finished its own retries? The payment appears as soon as it fails, marked as Stripe's to retry. Foxhound's sequence starts when Stripe stops.
  • Is the payment on the account you are looking at? If you hold more than one, check the account switcher in the header.
  • Is Stripe still reaching Foxhound? The webhook health badge on the dashboard says so.

Emails are not sending

  • Is the address suppressed? A customer who unsubscribed, hard bounced, or reported an email as spam is suppressed, and Foxhound will not send to them again.
  • Is the step actually due? The timeline on the payment page shows when each step is scheduled.

Note. Suppression is per address and it holds. It exists so a customer who asked to stop hearing from you is not mailed again by a later sequence.

Recovery rate seems low

  • How many closed payments are behind it? A rate over a handful of payments moves on every one of them. Give it a billing cycle.
  • What is the decline mix? Fraud and revoked recover less by nature. The decline breakdown on the dashboard shows yours.
  • Are the emails being opened? Low open rates on the sequence page point at deliverability rather than at the copy.
  • Is the brand voice set? Copy written without one is more generic than copy written with one.

A customer says they did not receive an email

  • Check the timeline on the payment page and confirm the step ran rather than sitting pending.
  • Check whether the address is suppressed.
  • Ask them to look in spam.
  • Use Resend last email on the payment page to send it again.

Contact support

If none of this explains it, email support@foxhoundapp.com from the address you sign in with, and include the Stripe invoice ID (in_) or payment ID (pi_) of the payment in question, so it can be found without a second round of email.