> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/handling-failed-payments/coordinating-messaging-with-recovery.md).

# Coordinating Messaging with Recovery

How FlyCode coordinates recovery emails with retries: templates and models for failed-payment outreach, how this compares with Stripe's default emails, and whether to show customers the raw decline co

The way you communicate about a failed payment decides whether an involuntary churn event stays recoverable or turns into a real cancellation. FlyCode treats messaging as part of the recovery engine rather than a separate email drip. This page covers what is provided, how it differs from Stripe's defaults, and what to show the customer.

## Do you provide email templates for failed-payment outreach?

Yes. FlyCode includes ready-to-use transactional templates for failed-payment outreach, and its communication models decide when each one is sent so that emails coordinate with the retry schedule rather than firing after every attempt. Templates are short, transactional and specific to the failure type (a request for a new card reads differently from a note that a retry is scheduled), and they can be customized with your brand, tone and sender domain. They are sent from high-reputation sending infrastructure to keep deliverability high, and SMS is available alongside email. See [Failed Payment Outreach](https://help.flycode.com/failed-payment-outreach) for customization and delivery details.

## How does FlyCode handle customer emails compared with Stripe's defaults?

Stripe's default dunning can send an email at every failed attempt, up to eight emails over a retry cycle, each one alerting a customer who may not have known anything was wrong. That is the mechanism by which involuntary churn becomes voluntary: the customer sees repeated payment failures, decides the subscription is a hassle, and cancels.

FlyCode coordinates emails with its retries. No email is sent after a soft decline while silent recovery still has a good chance. When outreach is needed, it goes out on a purpose-built cadence for the failure type, in the customer's local time, from your own domain, with a single clear action. At go-live you turn off Stripe's default failed-payment emails so the two systems do not both message the customer. The [Stripe integration guide](https://docs.flycode.com/docs/integrations/stripe-integration-guide-for-flycode) covers the exact settings.

## Should I expose the raw decline code to customers?

It is your choice, and the usual recommendation is no. Raw codes such as `do_not_honor` or `generic_decline` mean nothing to most customers and can sound alarming. FlyCode's email product lets you show a friendly, action-oriented message ("your bank declined the renewal; update your card or contact your bank") while logging the exact decline code internally for support agents and for automated retry logic. The exception is when the code carries a clear customer action, such as a bank requiring authorization for recurring charges, where naming the reason helps the customer resolve it.

## Related

* [Failed Payment Outreach: Delivery Strategy](https://help.flycode.com/failed-payment-outreach/delivery-strategy)
* [Email Behavior & Deliverability](https://help.flycode.com/ai-payment-recovery/email-behavior-and-deliverability)
* [Dunning management 2026 guide](https://docs.flycode.com/docs/dunning-management-2026-guide)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.flycode.com/handling-failed-payments/coordinating-messaging-with-recovery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.